install/upgrade scripts updated to detect and use NVM

[sdetweil]

I am seeing more cases where users have used nvm to change their node version.
which conflicts with the tool the scripts use (n, which is a nodejs version of nvm)

but the two tools store the node versions in different places, which causes failures on update and install

I have updated the tools to detect if nvm is installed and use it
otherwise use n

keep an eye out for any install or upgrade issues related to nodejs version

thanks for any feedback

[schlomm]

@sdetweil Thanks for your effort! For my Magic Mirror Instances I try to use/install the node version installed by MagicMirror, but yeah -“nvm” ist a great tool in the node ecosystem.

Thanks for your work and the updates script ♥️

[sdetweil]

@schlomm said in install/upgrade scripts updated to detect and use NVM:

For my Magic Mirror Instances I try to use/install the node version installed by MagicMirror,

that is what the script does… reads package.json engines, and uses that.
on some systems, you might get 22.20.0 instead of 22.18.0

you don’t have to do it manually , as the script will handle it.

BUT if you used nvm for some reason, then it puts code in the users home folder/.nvm
and first in the PATH…
n puts code in /usr/local/bin , but if nvm is first… oops…
so , n did its thing, but no change…

use the tool the user picked, quite a pain to get nvm to run FROM a script…