Node
nvm
windows
Written by:
As a developer, you'll likely encounter the need to juggle multiple Node.js projects in your local development environment, each requiring different versions of Node.js. To manage these requirements efficiently, we strongly recommend installing Node Version Manager (NVM) instead of directly installing Node.js. NVM allows you to switch between Node versions seamlessly, ensuring that each project has the right environment to run effectively. For those interested in optimizing their development setup further, we have an article detailing the best local development practices to help you avoid common issues in the future.
π This guide is for Windows users only, follow these links if you want to install NVM on MacOS or install NVM on linux.
In order to install Node Version Manager tool in Windows environment can download the latest version zip file from the following list of official version.
π₯ Make sure to download the ZIP file because it contains a very simple installation wizard.
Go to your Downloads folder on Windows, and unzip nvm-setup.zip
file and double click on nvm-setup
.
When the installation wizard opens, hit the next button a bunch of times, and at the end you will see an install button that you will hit too. After that, just wait for the progress bar to finish.
βοΈ ?? Remember not to touch any default configuration. Always keep hitting next!!!
Once it is installed, open Windows Command Prompt. If you have any issues finding the command line, just type CMD in Windows search bar at the bottom-left corner of your desktop.
Type nvm
and hit enter
on your command prompt and you should see a message similar to this one:
If you want to check what are the current node versions available you can type: nvm list available
or you can go to nodejs.org and check all of them.
We would recommend using the latest stable version, for example Node v22 when writing this article. In the command prompt type the command below:
1nvm install 22
Always check your installed node versions. Sometimes our applications do not run because we are using outdated versions. This command will show all the installed node versions you have in Windows.
1$ nvm list
You can always use different node versions and this command line let us jump between all our installed versions.
1# for node 8 2nvm use 8.15.0 3# for node 10 4nvm use 10.15.1
Here's a list of common problems you might encounter while installing NVM (Node Version Manager) on Windows, along with solutions for each:
Problem: π± After successfully installing NVM, you might encounter an issue where running nvm
commands results in a command not found
error.
Solution: π This usually occurs because the NVM path has not been correctly added to the system's environment variables. You can manually add the NVM directory to your PATH by:
C:\Users\<Your-Username>\AppData\Roaming\nvm
.Problem: π± Sometimes, even if the installation completes successfully, NVM might not work because the installer fails to set the necessary environment variables.
Solution: π Verify that the environment variables have been set correctly. If not, manually add NVM_HOME
and NVM_SYMLINK
to your system's environment variables:
NVM_HOME
should point to the directory where NVM is installed.NVM_SYMLINK
should point to the directory where Node installations will be placed.Problem: π± Installation fails with an 'Access Denied' error message. Solution: π This can occur if you do not have administrative privileges on your computer. Try running the installer as an administrator by right-clicking on the installer and selecting 'Run as administrator'.
Problem: π± After NVM is installed, attempting to install certain Node versions fails. Solution: π This can happen due to network issues or if the Node version specified is incorrect. Ensure you have a stable internet connection and verify the version number. Also, try installing another version to check if the problem is specific to one version. Sometimes, running the command prompt as an administrator helps.
Problem: π± This error typically appears if the command prompt was open during the installation and hasnβt been restarted, or the PATH hasn't been updated properly. Solution: π Close and reopen your command prompt or restart your computer to ensure all environmental changes take effect. Double-check the PATH settings as described in the solutions for 'Command Not Found Error After Installation'.
Problem: π± NVM installs and lists Node versions correctly, but switching between them doesnβt seem to work. Solution: π Make sure that when you install Node versions via NVM, youβre running the command prompt as an administrator. Sometimes, permissions issues can prevent NVM from modifying the symlinks properly.
Problem: π± NVM can sometimes be noticeably slower on Windows compared to Unix systems. Solution: π This is a known issue due to how environment variables and paths are managed on Windows. Minimizing the number of Node versions installed and rebooting the system after making significant changes can sometimes help.
These solutions address the most common issues faced when installing NVM on Windows, helping you ensure a smoother setup and management of different Node.js versions.