Working with Node.js Versions Using NVM

Different Node.js projects often need different Node.js versions: an older app may only run on the version it was built for, while a new one wants the latest LTS release. nvm (Node Version Manager) installs several versions side by side in your home folder and lets you switch between them with one command. This guide shows how to install nvm, choose the right version, switch per project, and upgrade or downgrade safely.

1. Understand Node.js versions

Node.js uses semantic versioning: major.minor.patch, for example 24.5.1. A new major version can break existing code; minor and patch releases should not.

Each major version goes through three stages:

• Current: the newest release with the latest features. Short-lived for odd numbers.
• Active LTS (long-term support): an even-numbered release that is recommended for production and receives fixes and security updates.
• Maintenance LTS: only critical fixes and security updates, until it reaches end of life.

The schedule changes every year, so check the release page on nodejs.org before you choose.

2. Install nvm

nvm works on macOS and Linux (including WSL on Windows). Install it with the one-line command in the README at github.com/nvm-sh/nvm. The README always shows the current release; copy the command from there rather than from an old tutorial, and read the script first if you prefer.

The installer adds a few lines to your shell profile (~/.bashrc, ~/.zshrc or ~/.profile). Open a new terminal, then check:

command -v nvm    # prints "nvm" if it loaded
nvm --version

If nvm is "not found", make sure the lines the installer added are in the profile file your shell actually reads, then open a new terminal.

3. Check what you have

node -v            # the active Node.js version
npm -v             # the npm bundled with it
nvm ls             # versions installed with nvm, and your default
nvm ls-remote --lts   # LTS versions available to install
nvm current        # the version this terminal is using

4. Install and use the LTS version

nvm install --lts          # install the latest LTS release
nvm use --lts              # use it in this terminal
nvm alias default lts/*    # use the latest LTS in every new terminal

You can also install a specific major version by number, which installs its latest patch release:

nvm install 24
nvm use 24

npm comes with each Node.js version. To update npm on its own, run npm install -g npm@latest, though it is usually simpler to let npm update with Node.js.

5. Pin a version per project with .nvmrc

Put a .nvmrc file in the root of each project so everyone on the team, and your deployment, uses the same version:

echo "24" > .nvmrc
nvm install   # installs the version in .nvmrc if needed
nvm use       # switches to it

Commit .nvmrc to your repository. You can also declare the requirement in package.json, which many tools and hosts read:

{
  "engines": { "node": ">=24" }
}

6. Upgrade to a newer version

When you move a project to a new major version:

7. Downgrade for an older project

Sometimes an old project only works on an older release. Install that version and use it for that project only:

nvm install 18
nvm use 18

Keep your default on the current LTS, and switch only inside that project. Treat this as temporary: Node.js 18 and older are end of life and receive no security fixes, so plan to upgrade the project rather than running it in production on an old version.

8. Build and run your app

With the right version active, use the scripts defined in package.json:

npm ci           # install exactly what package-lock.json says
npm run build    # run the project's build script
npm start        # start the app

Run commands through npm run rather than calling a system path such as /usr/bin/node. A fixed path points at the system Node.js, not the version nvm selected.

9. Running Node.js on Domain India

• cPanel and DirectAdmin shared hosting: you don't need nvm. Node.js apps run through the control panel's Node.js tool, which offers several versions. When we checked on 23 September 2026, cPanel offered Node.js 20, 22 and 24, and DirectAdmin 14 to 24. Choose the same major version as your .nvmrc. See how to deploy a Node.js app on shared hosting. Jailed SSH is available on request (key login only); tools available inside the jail vary, so ask support before relying on one.
• App Platform: Node.js apps are detected and built automatically from package.json; you deploy with Deploy Now or a deploy token. See getting started with the App Platform.
• VPS: self-managed with root access. nvm works for your own user; for a service that starts at boot, a system-wide install from NodeSource is often simpler.

The price on the card is a Domain India list price and excludes 18% GST.

Frequently asked questions

Ready to deploy? Put your Node.js app on the App Platform, compare cPanel hosting and VPS plans, or open a ticket if you need help choosing.