Updating Nodes Through Palette Manager seems Broken

I'm having trouble updating seemingly any node through the palette manager, and it seems, through npm as well. I think this started after updating to the latest version of node and npm.
Here's the log it's generating:

2023-03-26T07:11:29.162Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-dashboard@3.4.0

2023-03-26T07:11:30.379Z [err] npm

2023-03-26T07:11:30.380Z [err]

2023-03-26T07:11:30.380Z [err] WARN config production Use `--omit=dev` instead.

2023-03-26T07:11:32.469Z [err] npm

2023-03-26T07:11:32.469Z [err]

2023-03-26T07:11:32.469Z [err] ERR! code EBADENGINE

2023-03-26T07:11:32.474Z [err] npm

2023-03-26T07:11:32.474Z [err] ERR!

2023-03-26T07:11:32.475Z [err]

2023-03-26T07:11:32.475Z [err] engine Unsupported engine

2023-03-26T07:11:32.475Z [err] npm ERR! engine

2023-03-26T07:11:32.475Z [err] Not compatible with your version of node/npm: node-red-contrib-wstt-stream-fixed@0.0.2

2023-03-26T07:11:32.476Z [err] npm

2023-03-26T07:11:32.476Z [err] ERR! notsup Not compatible with your version of node/npm: node-red-contrib-wstt-stream-fixed@0.0.2

2023-03-26T07:11:32.476Z [err] npm ERR!

2023-03-26T07:11:32.476Z [err] notsup Required: {"node":"6.x"}

2023-03-26T07:11:32.476Z [err] npm ERR!

2023-03-26T07:11:32.476Z [err] notsup Actual: {"npm":"8.19.3","node":"v16.19.0"}

2023-03-26T07:11:32.481Z [err]

2023-03-26T07:11:32.481Z [err] npm

2023-03-26T07:11:32.482Z [err] ERR! A complete log of this run can be found in:

2023-03-26T07:11:32.482Z [err] npm ERR! /home/pi/.npm/_logs/2023-03-26T07_11_30_304Z-debug-0.log

2023-03-26T07:11:32.492Z rc=1

I've tried putting that install command in the terminal after deleting the "engine-strict" part, and it sure acts like it works, but it doesn't seem to have successfully updated, in this case, dashboard.

Thank you for the help!

This node has been locked to requiring node js V6.x - you are running nodejs v16.x

You could request the author updates that node but since it was last published 6y ago, I don't hold much hope.

Do you need this node? Is there a more up to date alternative?

Wow...just wow. I never even noticed it was getting hung up on another node....I certainly didn't need it, deleted it, and it works great now. Thank you very much!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.