Cannot install any node with palette error

General
1

Hello. i cannot install any node with the palette manager.

here's the error.
Hope you can help me.

2025-03-14T17:55:20.946Z Installer : node-red-contrib-google-calendar 0.1.5

2025-03-14T17:55:20.637Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-google-calendar@0.1.5

2025-03-14T17:55:38.662Z [err] (node:18109) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.

2025-03-14T17:55:50.827Z [err] npm

2025-03-14T17:55:50.827Z [err] WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@3. I'll try to do my best with it!

2025-03-14T17:55:56.763Z [err] npm

2025-03-14T17:55:56.763Z [err] WARN deprecated sinon@8.0.4: 16.1.1

2025-03-14T17:56:30.774Z [err] npm

2025-03-14T17:56:30.775Z [err] WARN deprecated superagent@3.8.3: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net

2025-03-14T17:56:36.492Z [err] npm

2025-03-14T17:56:36.493Z [err] ERR! code ENOTSUP

2025-03-14T17:56:36.515Z [err] npm ERR! notsup Unsupported engine for mime@4.0.6: wanted: {"node":">=16"} (current: {"node":"12.22.12","npm":"6.14.16"})

2025-03-14T17:56:36.515Z [err] npm

2025-03-14T17:56:36.516Z [err] ERR! notsup Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T17:56:36.516Z [err] npm ERR! notsup Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T17:56:36.516Z [err] npm ERR!

2025-03-14T17:56:36.517Z [err] notsup Required: {"node":">=16"}

2025-03-14T17:56:36.517Z [err] npm ERR! notsup Actual: {"npm":"6.14.16","node":"12.22.12"}

2025-03-14T17:56:36.948Z [err]

2025-03-14T17:56:36.949Z [err] npm ERR! A complete log of this run can be found in:

2025-03-14T17:56:36.949Z [err] npm ERR! /home/pi/.npm/_logs/2025-03-14T17_56_36_534Z-debug.log

2025-03-14T17:56:37.020Z rc=1

-----------------------------------------------------------

2025-03-14T18:01:43.976Z Installer : node-red-contrib-google-calendar 0.1.5

2025-03-14T18:01:43.669Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-google-calendar@0.1.5

2025-03-14T18:01:57.597Z [err] (node:18185) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.

2025-03-14T18:02:08.200Z [err] npm

2025-03-14T18:02:08.200Z [err] WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@3. I'll try to do my best with it!

2025-03-14T18:02:13.743Z [err] npm

2025-03-14T18:02:13.743Z [err] WARN deprecated sinon@8.0.4: 16.1.1

2025-03-14T18:02:46.807Z [err] npm

2025-03-14T18:02:46.807Z [err] WARN deprecated superagent@3.8.3: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net

2025-03-14T18:02:52.825Z [err] npm

2025-03-14T18:02:52.826Z [err] ERR! code ENOTSUP

2025-03-14T18:02:52.847Z [err] npm ERR!

2025-03-14T18:02:52.847Z [err] notsup Unsupported engine for mime@4.0.6: wanted: {"node":">=16"} (current: {"node":"12.22.12","npm":"6.14.16"})

2025-03-14T18:02:52.847Z [err] npm ERR! notsup Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T18:02:52.848Z [err] npm ERR! notsup

2025-03-14T18:02:52.848Z [err] Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T18:02:52.848Z [err] npm

2025-03-14T18:02:52.848Z [err] ERR! notsup Required: {"node":">=16"}

2025-03-14T18:02:52.848Z [err] npm ERR!

2025-03-14T18:02:52.848Z [err] notsup Actual: {"npm":"6.14.16","node":"12.22.12"}

2025-03-14T18:02:52.892Z [err]

2025-03-14T18:02:52.893Z [err] npm ERR! A complete log of this run can be found in:

2025-03-14T18:02:52.893Z [err] npm ERR!

2025-03-14T18:02:52.893Z [err] /home/pi/.npm/_logs/2025-03-14T18_02_52_865Z-debug.log

2025-03-14T18:02:52.929Z rc=1

Thanks!
Marc.

2

Hi @MPELectronique

Some of the clue(s) are in the error message(s)

wanted: {"node":">=16"}
current: {"node":"12.22.12"}

You really should look at updating Node RED & importantly your Node version.
if you use the latest Node RED Install script, it can all be updated.

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

It uninstall node-red completly.
Can i get it back?

thank you.
Marc.

4

Really - first we have heard, how did you install Node RED originally?
I cant imagine that it removed Node RED, unless you installed Node RED using non traditional methods

5

using the bash script

6

What did?

This node has not been updated in nearly 5 years, the Google API's have changed greatly in that time I think.

Also, that node's readme refers to a completely different package quite early on and it isn't clear as to why.

So I would say that you probably shouldn't be using that node. Especially since it (or something else) is disabling certificate checking which is a really bad idea.

7

I managed to reinstall Node-Red using this command:

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

and i write in the adress bar: http://10.0.0.160:1880/

and it load and stops.
what can i do?

Marc.

[Moderator edit to fix url and code formatting]

8

Without more information, we can't help.

Please share the node-red log, at least the startup and the part that stops.

Also, try stopping node-red then rename the ~/.node-red folder to something different and restart node-red, it should recreate that folder with a clean config. You can rename back later if that works.

9

Once upon a time Node-red stored flows in a file flows_hostname.json. In more modern releases the flows live in flows.json.

This might be the cause of a blank editor page with no flows.
Either find your old flows and credentials files and rename them flows.json and flows_cred.json or else edit settings.js to make Node-red point to the old style filename.

ps The current stable version of node.js is 22. Node-red works reliably with v20 or, on eg an old Raspberry Pi, v18.
Why did you specify v16?

1 Like
10

can close the issue i got node-red back with node 20

1 Like