Node.js & NVM Installation Guide: Managing Multiple Node Versions Seamlessly

The Problem with Global Node.js Installers

Installing Node.js via standard standalone MSI or PKG installers binds your entire system to a single runtime version. In reality, modern developers maintain legacy projects requiring Node 18, active projects running Node 20 LTS, and experimental apps on Node 22. Attempting to manage this with a single global installation leads to broken dependencies and version mismatch errors.

Node Version Manager (NVM) solves this by enabling instant runtime switching on a per-project basis.

1. Installing NVM on Windows

1. Download nvm-setup.exe from the official coreybutler/nvm-windows repository.
2. Run the installer and complete the setup.
3. Open a new terminal to verify:

nvm version

2. Installing and Switching Node Versions

# Install the latest Long Term Support (LTS) release
nvm install lts

# Install a specific Node version
nvm install 20.12.0
nvm install 18.20.0

# List installed versions
nvm list

# Switch your active version immediately
nvm use 20.12.0

3. Automatic Version Switching with .nvmrc

Add a .nvmrc file to the root of your project repository specifying the target version:

v20.12.0

Whenever your team clones the repository, running nvm use automatically selects the matching Node release.

4. Optimizing Global NPM Storage

Ensure your global npm modules are stored cleanly in user space without requiring administrator permissions:

npm config set prefix "~/.npm-global"
npm install -g yarn pnpm tsx