nvm

nvm is a free command-line tool for installing and managing Node.js versions within an individual user account. It is best suited to developers moving among projects with different Node.js requirements. Its focused version controls and project pinning are compelling, provided your shell and Windows setup are compatible.

Overview

Installed per user and invoked per shell, nvm lets you install specific Node.js versions, switch between them, and set aliases such as a default. That scope keeps runtime choices close to a developer’s work, but nvm is for Node.js alone, not a multi-language version manager.

An .nvmrc file can record the Node.js version a project expects. Documented shell snippets support automatic switching, which can reduce manual version changes between projects, though it requires shell configuration. nvm can also reinstall global npm packages from another installed version during installation—a useful way to carry those packages forward when changing runtimes.

Key features

• Version selection and aliases: Install particular releases, switch as needed, and choose a default. This suits developers who need different Node.js versions without changing their project workflow around one runtime.
• LTS management: Commands and aliases support installing, using, and listing long-term support releases. That gives users who prefer LTS versions a direct way to select them.
• Project pinning and automatic switching: An .nvmrc names a project’s intended version, while documented shell snippets can automate switching. The file provides a project-level cue; automatic behavior depends on configuring the shell.
• Offline installation: The --offline flag can install a previously downloaded or cached Node.js version without network access. It helps when connectivity is unavailable, but only for versions already cached.
• Docker and CI: The project README documents Docker use, including an example for CI/CD jobs, making nvm relevant beyond interactive development shells.

Pricing

nvm is open-source software under the MIT license, with one free plan: free. The plan is the Node.js version manager itself; there is no paid tier or free-trial decision to weigh. It is a focused, single-language option for individuals who need Node.js version management rather than broader runtime coverage.

Platforms

nvm supports POSIX-compliant shells, including sh, dash, ksh, zsh, and bash, on Linux and macOS. Its per-shell design makes compatibility central: the project does not support Fish, though it points users to community alternatives. Windows use is possible through WSL; Git Bash or Cygwin may work depending on the environment, so Windows users outside WSL should not assume a consistent fit.

Who it's for

nvm is a strong fit for Node.js developers who work across projects with different runtime requirements, want to pin a project version, or prefer LTS releases. Cached-version installation and documented Docker and CI examples also suit workflows that need to reuse Node.js versions offline or in build jobs. It is less suitable for people who need one manager for several languages, use Fish, or need straightforward Windows support outside WSL.

Pros and cons

• Pro — project-level version pinning: .nvmrc gives projects a way to state their expected Node.js version, with shell snippets documented for automatic switching.
• Pro — useful runtime controls: Specific versions, default aliases, and LTS commands cover common choices without broadening the tool beyond Node.js.
• Pro — offline and CI options: Cached versions can be installed offline, and Docker use is documented with a CI/CD example.
• Con — narrow language scope: nvm manages Node.js, so developers seeking one tool for multiple language runtimes need another approach.
• Con — shell and Windows caveats: Fish is unsupported, and Windows compatibility beyond WSL depends on the environment.
• Con — support follows the current release: Only the latest nvm version is supported, which matters to users who need support for older releases.

Alternatives

For other runtime-management choices, see Runtime Version Managers and Development Environment Managers. nvm’s own scope is specifically Node.js version management, so readers comparing tools should consider whether they need that focus or broader coverage.

The listed alternatives are disk diagnostic tools rather than Node.js version managers, so they do not serve the same purpose as nvm. GSmartControl is a free drive-health inspection option for Linux, macOS, and Windows; smartmontools is a free Linux, macOS, and Windows option built around the smartctl and smartd utilities. DiskMaster is a free disk tool for Linux, macOS, and Windows. Hard Disk Sentinel offers a limited trial and Linux and Windows versions, while Active@ Hard Disk Monitor has personal-use freeware for Windows and a custom-priced Professional plan for business use. Ariolic Disk Scanner is a free Windows disk-scanning utility. CrystalDiskMark offers a free Windows desktop edition and a Microsoft Store edition priced at $9.99, paid once. DRevitalize has an older free DOS version for Windows.

Verdict

Choose nvm if you work primarily with Node.js and want per-user version switching, project pinning, and LTS controls without a license cost. Its main reason to look elsewhere is compatibility or scope: Fish is unsupported, Windows outside WSL is uncertain, and the tool does not manage other languages.