How to Install Node.js on Ubuntu 26.04 and 24.04

• Ubuntu 26.04 LTS or 24.04 LTS, internet access and a sudo account.
• Choose one method first. Existing applications may depend on an installed system version.
• For nvm, use a regular user account and a Bash or Zsh shell. Node installed this way belongs to that user.

These checks show which commands your current shell finds and whether APT owns a Node.js package. Missing commands or no installed package are normal on a fresh system.

command -v node
command -v npm
node --version
npm --version
dpkg-query -W nodejs npm 2>/dev/null
apt-cache policy nodejs npm

Paths under your home directory can indicate a user-managed installation; /usr/bin usually indicates a system package. Do not remove a working runtime until you know what depends on it.

Refresh package lists, then install download tools and the library required by recent official Linux binaries:

sudo apt update
sudo apt install curl ca-certificates libatomic1

Stop if APT reports an error. nvm supports multiple shell environments; the commands below assume Bash.

Download the official release script, inspect it, and run it as your normal user. The installer modifies your shell profile and normally installs into ~/.nvm; an existing NVM_DIR or XDG configuration can change the location.

nvm_installer=$(mktemp) && curl -fsSL https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.8/install.sh -o "$nvm_installer" && less "$nvm_installer"

Press q to exit the viewer. In the same terminal, only run the script after a successful download and review:

bash "$nvm_installer"

After the installer finishes successfully, remove the downloaded temporary file in the same terminal, while its path is still stored in the shell variable:

rm -- "$nvm_installer"

Then open a new terminal so the profile changes load. Do not use sudo to install or run nvm.

In the new terminal, confirm nvm is loaded, then install the latest LTS release:

command -v nvm
nvm install --lts
nvm current
node --version
npm --version
command -v node
command -v npm

The first command should print nvm. Node and npm paths should point inside your nvm directory. If nvm is not found, see Troubleshooting. The latest LTS major changes over time; use a project-specific version when required.

If a project contains an .nvmrc file, run these commands from its directory to install and select the specified version:

nvm install
nvm use
node --version

Changing directories alone does not automatically select the version. To install a specific supported major, for example 24 rather than the latest LTS, use nvm install 24 and nvm use 24. Check the project requirements and Node.js release schedule first.

Use this alternative if you need Ubuntu-managed system packages. Node.js and npm are separate packages in Ubuntu. The Universe repository must be enabled. Check the candidate and its source:

sudo apt update
apt-cache policy nodejs npm

If no candidate appears, enable Universe in Software & Updates, refresh the package index and check again. If a third-party source is selected, resolve that before continuing; this section assumes Ubuntu packages.

Review the proposed transaction, especially removals on a system with an existing installation. Stop if it would remove software you need.

sudo apt install --simulate nodejs npm

If the proposal is acceptable, install and verify:

sudo apt install nodejs npm
node --version
npm --version
command -v node
command -v npm

When nvm is active, the shell may still find its user-managed Node.js first. Use nvm use system to check the system version in that shell.

Open a new Bash terminal after installation. Check your installer output and shell startup file. For the usual default location, load nvm for this session:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
command -v nvm

If you use a custom NVM_DIR or XDG location, use that location instead. Check the nvm Linux troubleshooting notes if it still does not load.

Run command -v node, command -v npm and nvm current if nvm is loaded. Select the project version with nvm use, or nvm use system for APT. Avoid using sudo with nvm or changing ownership of system directories. A custom npm prefix can conflict with nvm; inspect npm config get prefix and your user npm configuration before changing it.

If Node reports a missing libatomic.so.1, install libatomic1 with APT and retry. Some npm dependencies compile native code; if an error mentions a compiler or node-gyp, install build-essential and python3, then check that the dependency supports your Node and Python versions. Do not replace Ubuntu system Python.

List installed versions and switch away from the version to remove:

nvm ls
nvm deactivate

Then run nvm uninstall VERSION, replacing VERSION with the exact unwanted version shown by nvm ls. Global npm packages installed under that version are removed with it. To remove nvm itself, first inspect your configured NVM_DIR and shell profile, back up anything needed, and follow the manual uninstall instructions.

If you used Ubuntu APT packages, preview dependent removals first:

sudo apt remove --simulate nodejs npm

Proceed only if the proposed changes are acceptable:

sudo apt remove nodejs npm
sudo apt autoremove --dry-run

Run sudo apt autoremove only after reviewing the dry run. These commands do not remove your project files or an nvm installation.