It is interesting that it did not install 12. Can you post the install log please. When you copy/paste it in use the </> button at the top of the forum entry window and paste it where it says.
To be clear - In general we don't upgrade node.js if you are on an LTS - so 10 or 12 or 14. If you are on 10 from apt (10...dfsg) or any odd numbered version (apart from 15) then we do try to upgrade it to node 12 LTS. If you are on 15 then we assume you may be trying something new and or may need it for some other reason so don't touch it.
Last week I did try moving things from 10 to 12 as a minimum - and yeah - that is where Pete had a lot of trouble with nodes with native code not migrating so I backed that change out again pronto.
So result is if you are on an LTS version (10,12,14) having run the script then for any Arm7 based Pi - then your usual apt-get update/upgrade will get any fix releases for you - (script not needed). The script will take care of the Node-RED upgrade part for you.
If you do want to upgrade the version of node (and you are on an LTS version) then yes you need to purge node.js first - then either install the version you want - or let the script install 12 (currently) for you.
But as Pete showed us - upgrading across major versions can break other installed nodes - and although we try to handle it - there are so many nodes that may or may not be supported at different versions it may not be possible. Anyway - we do our best. Personally I don't think we do a bad job vs the amount you pay for all this.
4 Likes
It's big. I will attach.nodered-install.log.txt (48.0 KB)
Yes, everything works fine on 10 and 12 and 14 versions. just the script puts 10 and we remember about the roadmap. It's time to say goodbye to 10 ...
We didn't need the whole log, just the bit relating to the most recent install, but it doesn't matter.
Looking at the log I can't work out why it has installed node 10, can you paste here the exact command you are using to run the install script please.
bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)
That is the wrong script. See https://nodered.org/docs/getting-started/raspberrypi.
Where did you find instructions to tell you to use the command you used?
As per the chart you just posted - 10 isn't going anywhere until April next year... at that point yes - we will drop it - jump base to node14, ship Node-RED 2., etc. See Going beyond Node-RED 1.x : Node-RED
True, but I believe the script now installs 12 if nodejs is not installed.
@Daneev has been running the wrong script. Should that one be removed to avoid such confusion again?
Indeed - and when you run that old script it does give you a link and tell you to run the new one instead...
We left it there while we migrated to the new script, knowing there may well be blogs etc pointing at the old one... but yeah - I'll knobble it so it no longer runs 
The clue is when it says ARCHIVE in the url...
so yes - it has changed...
You should be at https://nodered.org/docs/getting-started/raspberrypi
I am aware that the archive. I was asked where I got it and show what I took from the site. 2019 only. Since then, I have recorded it in One-Note from where it was convenient for me to use it. God, in Windows, I updated with a mouse in 5 minutes)
It would have been the same on the pi (apart from the power of the pi itself) if you had used the recommended script.
I checked, the new script puts the 12th version, everything is fine, but I will leave the 14th
It's my fault that I didn't check the script
Ah yes, but the amount of (wasted according to my wife) time you and Nick have personally cost us over the years!!! 
We like to share the pain
4 Likes
I like your (British?) humour! Is applicable & valid here too...
2 Likes
What makes you think Dave was joking 
1 Like
In fact, even faster in pure time. But cumulatively due to confusion with scripts - half a day.
