Note: The parameter below is optional $ nvm use Get Available Versions to Install $ nvm list available View Default Node Architecture Being Used $ nvm archĬhange Default Node Architecture $ nvm arch 32 Nvm just switches out which version is referenced in your path variables. Installing Node packages is the same as you are used to. Additionally, some npm modules may not be supported in the version of node you’re using, so be aware of your environment as you work. Reminder! Any global npm modules you may have installed are not shared between the various versions of node.js you have installed. Note that only 1 node version can be activate at a time. Below we are installing 4.4.5 and 5.10.1. Get a the list so you can see what is available $ nvm list available If you originally installed to the default locations, you just need to click “next” on each window until it finishes. Make sure you use the same installation and symlink folder.
It will safely overwrite the files it needs to update without touching your node.js installations. Delete the npm install directory at C:\Users\AppData\Roaming\npm.
NVM’s generated symlink will not overwrite an existing (even empty) installation directory. “C:\Program Files\nodejs”) that might remain.
This means that it will take a bit more disk space but most node packages are fairly small so this should be a none issue. There is no ability to share packages between versions. The one downside to having multiple versions of Node installed is that you have to install the global packages for each version of node that you want them available to. Luckily with nvm you can install multiple versions of Node on the same machine and switch between them with a simple command line call. I am sure that many of you are in the same situation that I am in with needing a different version of node for different projects and you don’t want to have to create a new virtual machine for each project just because of node.