

We recommend using the installer, but if you have a more advanced understanding of your needs, you may want to consider the manual installation.
HOW TO INSTALL NPM GLOBALLY ON WINDOWS HOW TO
For help with removing previous installations, see How to completely remove node.js from Windows.)įollow the install instructions on the windows-nvm repository. NVM's generated symlink will not overwrite an existing (even empty) installation directory.

This includes deleting any existing nodejs installation directories (e.g., "C:\Program Files\nodejs") that might remain. It is always recommended to remove any existing installations of Node.js or npm from your operating system before installing a version manager as the different types of installation can lead to strange and confusing conflicts. There are alternative version managers to consider as well covered in the next section. Instead, we recommend installing nvm-windows and then using it to install Node.js and Node Package Manager (npm). Node Version Manager, more commonly called nvm, is the most popular way to install multiple versions of Node.js, but is only available for Mac/Linux and not supported on Windows. You will likely need to switch between multiple Node.js versions based on the needs of different projects you're working on. We recommend using a version manager as versions change very quickly. Install nvm-windows, node.js, and npmīesides choosing whether to install on Windows or WSL, there are additional choices to make when installing Node.js. If you are using Node.js professionally, find performance speed and system call compatibility important, want to run Docker containers that leverage Linux workspaces and avoid having to maintain both Linux and Windows build scripts, or just prefer using a Bash command line, then install Node.js on Windows Subsystem for Linux (more specifically, WSL 2).
