Thank you again sir for the support.
rock@rockpie:~$ which node
/usr/bin/node
rock@rockpie:~$ apt policy nodejs
nodejs:
Installed: 10.24.0~dfsg-1~deb10u3
Candidate: 10.24.0~dfsg-1~deb10u3
Version table:
*** 10.24.0~dfsg-1~deb10u3 500
500 http://security.debian.org buster/updates/main arm64 Packages
100 /var/lib/dpkg/status
10.24.0~dfsg-1~deb10u1 500
500 Index of /debian buster/main arm64 Packages
I read that the script leaves node.js untouched if it detects node.js > 10. So i tried to update npm manualy with
sudo npm cache clean -f
sudo npm install -g n
sudo n stable
and confirmed it with:
rock@rockpie:~$ npm -v
9.5.1
rock@rockpie:~$ node -v
v18.16.1
when i run the script i get;
Stop Node-RED \u2714
Remove old version of Node-RED \u2714
Node option not specified : --node14, --node16, or --node18
Leave existing Node.js : v10.24.0 Npm 5.8.0
Clean npm cache -
Install Node-RED core \u2714 3.0.2
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.pdate systemd script
npm WARN npm You can find the latest version at https://nodejs.org/
Move global nodes to local -
Leave existing nodes -/nodered-install.log
Install extra Pi nodes \u2714
Add shortcut commands \u2714
Update systemd script \u2714
after that when i enter the version number i get
rock@rockpie:~$ node -v
-bash: /usr/local/bin/node: No such file or directory
rock@rockpie:~$ npm -v
-bash: /usr/local/bin/npm: No such file or directory
rock@rockpie:~$
after a reboot:
rock@rockpie:~$ node -v
v10.24.0
rock@rockpie:~$ npm -v
5.8.0
rock@rockpie:~$
to be honest i am now at maximum confusion-level..
seems that the script downgrades my npm and node.js versions
