A new version of the package node-vscp-class (1.0.5) was published at 2020-02-19T17:06:43.505Z from 188.8.131.52. The shasum of this package was 3a7ac8a3c9c4e16a5bc8b05e7b4c5261332ef5a2.
A new version of the package node-vscp-type (1.0.5) was published at 2020-02-19T17:01:49.884Z from 184.108.40.206. The shasum of this package was 9936b45a6f5fd66f552b774da682e48749eee55e.
A new version of the package node-vscp-tcp (1.0.7) was published at 2020-02-18T11:08:17.527Z from 220.127.116.11. The shasum of this package was c7442d3916af3c9528dd13e7f8e825cb754ca153.
A new version of the package node-vscp (1.0.19) was published at 2020-02-18T11:06:11.869Z from 18.104.22.168. The shasum of this package was f3f76e558bf9728aacda46a97784265f4009b558.
On some Raspberry Pi’s of mine I had problems running node-js as a service as described here. The only hint of a problem I got was a cryptic “run nvm use latest/*” in the setup. I also remembered a post saying that node-red does not like nvm.
So how to get rid of nvm you have it installed?
sudo npm uninstall nvm
to remove it.
Then remove the lines nvm add to your .bashrc file. They are located at the end of the file and look like this
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion" # This loads nvm bash_completion
Now remove the nvm config folder
rm -rf ~/.nvm
Now run the node-red setup/update script again and after that services will work again.
I had problems installing node.js using the official install script. The problem
is that the update step fails. There is no clue in the install log file as far as I can see.
To solve the problem I installed node/nmp following the excellent guide here
After you gone throw the steps in the guide just run the install script again and everything will be alright. At least it was for me on a machine running Debian Stretch and some other boxes.