Error in 3.0 upgrade notes. BIG problem with latest Node.JS (v16.6)

[knolleary]

@Colin

could you comment on this please? The docs for upgrading nodejs (Supported Node versions : Node-RED) says that npm rebuild should be also be run in the node-red install directory. Is that still the case? I have never done that as far as I can remember.

It is still true that Node-RED has a binary module dependency (bcrypt) that will fall back to the less efficient bcryptjs if it fails to load.

When you change Node.js version you should run npm rebuild on any node_modules folders you have installed with the old version - just in case there's something in there that needs rebuilding.

[Colin]

@knolleary

fall back to the less efficient bcryptjs if it fails to load.

OK, thanks. Does it fail silently or is there a message in the startup log?

[bwims]

Hi,

Sadly this is nowhere near as usable. The function-npm would load modules dynamically, not require them to be specified and loaded in settings.js

Is that possible in V3 ?

[Steve-Mcl]

Node red version 2 and version 3 do not require you to put anything in settings.js. just enter the module name in the settings tab and deploy.

[bwims]

@UnborN
Thanks, I just found this live twitch thingy with @knolleary then I found it in the 2.0 release notes!

Looks like Writing Functions : Node-RED (nodered.org) needs an update

Isn't life grand?

Moral: try not to upgrade 2 versions at once...