Juggle Node Versions Without Breaking Projects (nvm, volta)

Why this matters

Node's release cadence is fast: even-numbered majors (18, 20, 22) are LTS for ~3 years, odd-numbered are not. You'll have multiple Node versions on one machine. nvm is the venerable choice (shell-only); volta is the rust-written newer option (faster, project-pinned auto-switching); corepack is Node-builtin and manages package managers (pnpm, yarn) without global installs. Pick one and stick with it.

Demo

Node version managers solve a real problem: different projects require different Node.js versions, and switching them manually invites version drift and subtle incompatibilities. nvm (Node Version Manager) is the original and most widely used — it manages versions per shell session via .nvmrc files — while volta pins versions per-project in package.json and automatically switches without any shell configuration. Knowing which tool your team uses and why version pinning matters is the difference between a reproducible development environment and a 'works on my machine' nightmare.

Try it yourself

1. Install nvm or volta. Run node --version, then install a different major version, and switch with nvm use or auto-switching.
2. In a fresh project, add a .nvmrc (or volta block in package.json) pinning Node 22. cd in and verify the right version is active.
3. Enable corepack with corepack enable. Now pnpm and yarn are available without global installs.
4. Try volta install pnpm to pin pnpm at the user level. Run pnpm --version from anywhere.

References

• nvm
• volta
• corepack
• Node.js release schedule