In win10 environment, nvm switches to node version, indicating that it is successful, but in fact it is still the original version. How to deal with it?

The

nvm version is 1.1.7.
can install other versions of node, view all installed node, use the nvm use command to switch, and prompt that the switch was successful, but in fact node is the same as the previous version.
I would like to ask you how to deal with it?

Jun.08,2022

to be honest. This situation is more difficult to deal with.
the reason is that your global node was previously installed.

different installation solutions are not the same.
and after switching, the global package is not the same and not universal. (nonsense, npm versions are different, and some of them are not backward compatible.)
it is recommended not to switch. It doesn't mean anything.
like a computer system, do you always switch between xp,win7,win10?
it's OK to have some fun. For the sake of stability, let's fix a version.

Menu