csuermann
commented
8 months ago Hi @jowi1968,
The Node-RED official Docker image's continued use of Node v16, which reached its end of life in 2023, is concerning, to say the least. I highly recommend building your own image utilizing Node 18 or 20 for improved reliability and security.
Please note that this repository does not contain the VSH add-on for Node-RED but its server counterpart.
Duplicate of https://github.com/csuermann/node-red-contrib-virtual-smart-home/issues/241
Installation of VSH 4.1.5 or later returns an error in Node-RED (v3.1.5, official docker) Seems like VSH needs node.js 18.2.0 while the official docker has 16.20.2 (?)
Error in Node-RED v3.1.5 after installing VSH 4.1.6:
2024-02-23T12:43:02.602Z Install : node-red-contrib-virtual-smart-home 4.1.6
2024-02-23T12:43:01.955Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-virtual-smart-home@4.1.6 2024-02-23T12:43:02.434Z [err] npm 2024-02-23T12:43:02.434Z [err] WARN config 2024-02-23T12:43:02.434Z [err] production Use
--omit=devinstead. 2024-02-23T12:43:06.547Z [err] npm ERR! 2024-02-23T12:43:06.547Z [err] code EBADENGINE 2024-02-23T12:43:06.549Z [err] npm ERR! engine Unsupported engine 2024-02-23T12:43:06.549Z [err] npm ERR! engine Not compatible with your version of node/npm: fast-unique-numbers@9.0.0 2024-02-23T12:43:06.549Z [err] npm ERR! notsup Not compatible with your version of node/npm: fast-unique-numbers@9.0.0 2024-02-23T12:43:06.549Z [err] npm 2024-02-23T12:43:06.549Z [err] ERR! notsup Required: {"node":">=18.2.0"} 2024-02-23T12:43:06.549Z [err] npm ERR! 2024-02-23T12:43:06.549Z [err] notsup Actual: {"npm":"8.19.4","node":"v16.20.2"} 2024-02-23T12:43:06.551Z [err] 2024-02-23T12:43:06.551Z [err] npm 2024-02-23T12:43:06.551Z [err] ERR! A complete log of this run can be found in: 2024-02-23T12:43:06.551Z [err] npm ERR! /data/.npm/_logs/2024-02-23T12_43_02_403Z-debug-0.log 2024-02-23T12:43:06.561Z rc=1