Any errors will be logged to /var/log/nodered-install.log
All done.
You can now start Node-RED with the command node-red-start
or using the icon under Menu / Programming / Node-RED
Then point your browser to localhost:1880 or http://{your_pi_ip-address}:1880
Started Wed 19 Sep 11:33:57 BST 2018 - Finished Wed 19 Sep 11:41:47 BST 2018
pi@plinth:~ $ cd .node-red
pi@plinth:~/.node-red $ node-red
bash: node-red: command not found
pi@plinth:~/.node-red $ node-red-start
Node-RED is not yet fully installed
Fetching Node-RED update.
This script will remove versions of Node.js prior to version 6.x, and Node-RED and
if necessary replace them with Node.js 8.x LTS (carbon) and the latest Node-RED from Npm.
It also moves any Node-RED nodes that are globally installed into your user
~/.node-red/node_modules directory, and adds them to your package.json, so that
you can manage them with the palette manager.
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.
Are you really sure you want to do this ? [y/N] ?
Just an idea: would it be an option to bundle each new node-red version with it's own carefully picked versions of node and npm?
Have a look here how Meteor does it.
The only slightly odd thing with your setup is that both node and npm are in /usr/local/... - the update script usually installs them in /usr instead (and wipes from /usr/local...) - If you apt-get purged them as per earlier then not sure why they would still be there.
We would like to think that the LTS versions are fairly stable - but...
