bbindreiter / node-red-contrib-alexa-remote2-applestrudel

Node-Red Nodes for interacting with Alexa
https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel
MIT License
74 stars 20 forks source link

Problemi Upgrade 5.0.27 > 5.0.41 #144

Closed saviothecnic closed 8 months ago

saviothecnic commented 9 months ago

My Node-Red 3.1.0

Errore Log

`2023-09-13T10:22:44.794Z Install : node-red-contrib-alexa-remote2-applestrudel 5.0.41

2023-09-13T10:22:45.049Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-alexa-remote2-applestrudel@5.0.41 2023-09-13T10:23:01.390Z [err] npm 2023-09-13T10:23:01.391Z [err] ERR! code ENOTSUP 2023-09-13T10:23:01.510Z [err] npm ERR! 2023-09-13T10:23:01.511Z [err] notsup Unsupported engine for node-red-contrib-alexa-remote2-applestrudel@5.0.41: wanted: {"node":">=16.0.0"} (current: {"node":"14.21.3","npm":"6.14.18"}) 2023-09-13T10:23:01.511Z [err] npm ERR! notsup 2023-09-13T10:23:01.511Z [err] Not compatible with your version of node/npm: node-red-contrib-alexa-remote2-applestrudel@5.0.41 2023-09-13T10:23:01.511Z [err] npm ERR! 2023-09-13T10:23:01.512Z [err] notsup Not compatible with your version of node/npm: node-red-contrib-alexa-remote2-applestrudel@5.0.41 2023-09-13T10:23:01.512Z [err] npm ERR! 2023-09-13T10:23:01.512Z [err] notsup Required: {"node":">=16.0.0"} 2023-09-13T10:23:01.512Z [err] npm ERR! 2023-09-13T10:23:01.512Z [err] notsup Actual: {"npm":"6.14.18","node":"14.21.3"} 2023-09-13T10:23:01.534Z [err] 2023-09-13T10:23:01.534Z [err] npm ERR! A complete log of this run can be found in: 2023-09-13T10:23:01.534Z [err] npm ERR! 2023-09-13T10:23:01.535Z [err] /home/pi/.npm/_logs/2023-09-13T10_23_01_517Z-debug.log 2023-09-13T10:23:01.571Z rc=1


2023-09-13T10:29:39.562Z Install : node-red-contrib-alexa-remote2-applestrudel 5.0.41

2023-09-13T10:29:39.859Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-alexa-remote2-applestrudel@5.0.41 2023-09-13T10:29:55.447Z [err] npm 2023-09-13T10:29:55.448Z [err] ERR! code ENOTSUP 2023-09-13T10:29:55.580Z [err] npm 2023-09-13T10:29:55.581Z [err] ERR! notsup Unsupported engine for node-red-contrib-alexa-remote2-applestrudel@5.0.41: wanted: {"node":">=16.0.0"} (current: {"node":"14.21.3","npm":"6.14.18"}) 2023-09-13T10:29:55.581Z [err] npm ERR! notsup 2023-09-13T10:29:55.582Z [err] Not compatible with your version of node/npm: node-red-contrib-alexa-remote2-applestrudel@5.0.41 2023-09-13T10:29:55.582Z [err] npm ERR! 2023-09-13T10:29:55.582Z [err] notsup Not compatible with your version of node/npm: node-red-contrib-alexa-remote2-applestrudel@5.0.41 2023-09-13T10:29:55.582Z [err] npm ERR! 2023-09-13T10:29:55.582Z [err] notsup Required: {"node":">=16.0.0"} 2023-09-13T10:29:55.582Z [err] npm ERR! notsup Actual: {"npm":"6.14.18","node":"14.21.3"}`

elgerg commented 9 months ago

You need node 16+ image

saviothecnic commented 9 months ago

Ok friend can you help me with what commands to launch to upgrade to the necessary node I have on raspberry PI4

elgerg commented 9 months ago

You want something like this bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node18

That will update to node 18. You can pick which version you want.

I believe that if you did the normal upgrade to Node-red 3.1.0 it will update node to 16.

elgerg commented 9 months ago

Also, check the changelog here https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/blob/master/CHANGELOG.md

It does specify that you need a new node version.

saviothecnic commented 9 months ago

bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node18

Ok Thanks friend with this command I solved it

github-actions[bot] commented 8 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 8 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.