What is nvm

Overview

Node Version Manager (NVM) is a popular open-source tool that simplifies managing multiple Node.js versions on your development machine. Node.js is constantly updated with new features, security patches, and improvements, but different projects may require different versions due to dependency compatibility. NVM eliminates the hassle of manually uninstalling and reinstalling Node.js when switching projects.

Why Use NVM

Different projects often depend on specific Node.js versions. A legacy project might require Node.js 14, while a newer project needs version 20. Without NVM, switching between these versions would require completely uninstalling one version and installing another, a time-consuming and error-prone process. NVM manages this automatically, allowing you to switch versions with a single command.

How NVM Works

NVM installs Node.js versions in a hidden directory in your home folder rather than system directories. When you activate a specific version, NVM modifies your system PATH to point to that version's binaries. This approach is clean, non-invasive, and allows complete isolation between versions. Each installed version includes npm and other tools, ensuring complete compatibility.

Key Features

• Version Management: Download, install, and manage multiple Node.js versions
• Quick Switching: Change versions with a single command (nvm use v14.0.0)
• .nvmrc Support: Automatically use the correct version specified in a project's .nvmrc file
• Version Aliases: Create shortcuts for commonly used versions
• Default Version: Set a default Node.js version for your terminal sessions

Installation and Setup

Installing NVM typically involves downloading an installation script from its GitHub repository and running it in your terminal. The installer modifies your shell configuration files (.bashrc, .zshrc) to load NVM automatically. After installation, you can immediately start downloading and managing Node.js versions.

Common Use Cases

Developers use NVM when contributing to multiple open-source projects, working on legacy systems, testing backward compatibility, or teaching Node.js to students who may use different versions. Teams often document required Node.js versions in project README files, and team members use NVM to match those requirements.