Running Node-RED update for user pi at /home/pi on raspbian
Nodejs 10 is no longer supported.
You can update to the latest Node-RED 1.x version by adding --nodered-version="1.3.5"
to that install command. If in doubt this is the safer option.
Or you can force an install of node 12 or 14 by using the --node12 or --node14 parameter
However doing so may break some nodes that may need re-installing manually.
Generally it is recommended to upgrade all nodes to their latest versions before upgrading.
Please backup your installation and flows before upgrading.
Exiting now.
Ok, I get it.
But adding --nodered-version="1.3.5" to that install command. can't be done.
I am using this to try and update: bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
pi@CameraPi:~/.node-red $ bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
This script checks the version of node.js installed is 12 or greater. It will try to
install node 14 if none is found. It can optionally install node 12 LTS or 14 LTS for you.
If necessary it will then remove the old core of Node-RED, before then installing the latest
version. You can also optionally specify the version required.
It also tries to run 'npm rebuild' to refresh any extra nodes you have installed
that may have a native binary component. While this normally works ok, you need
to check that it succeeds for your combination of installed nodes.
To do all this it runs commands as root - please satisfy yourself that this will
not damage your Pi, or otherwise compromise your configuration.
If in doubt please backup your SD card first.
See the optional parameters by re-running this command with --help
Are you really sure you want to do this ? [y/N] ? y
Would you like to install the Pi-specific nodes ? [y/N] ? n
Running Node-RED update for user pi at /home/pi on raspbian
Nodejs 10 is no longer supported.
You can update to the latest Node-RED 1.x version by adding --nodered-version="1.3.5"
to that install command. If in doubt this is the safer option.
Or you can force an install of node 12 or 14 by using the --node12 or --node14 parameter
However doing so may break some nodes that may need re-installing manually.
Generally it is recommended to upgrade all nodes to their latest versions before upgrading.
Please backup your installation and flows before upgrading.
Exiting now.
I'm taking a break from it. The two machines have been shut down.
But they are running Jessie, so I think that is part of the problem.
I'll try to remember to get their versions and post them ASAP.
Sorry, though I know I am not alone with this...... Covid 19 stuff, I am really not dealing with things as well as I would like.
So the brain isn't quite as responsive as I would like either.
Yes. Jessie LTS went eol June 20. You should still be able to upgrade to NR1.3.6 using the script with the extra parameter, but it won't work trying to upgrade to 2.x as the nodejs install will fail and mess everything up.