Knowing how to install nodejs sounds trivial — download an installer, click next, done. But that click-next path is exactly what leaves people fighting permission errors and stuck on an old version six months later. In 2026 the right way to install Node.js is through a version manager, so you can switch versions per project and never touch sudo just to install a package. Here is the honest, no-nonsense version.
What changed in 2026
- Version managers are the default recommendation. Even Node's own guidance now nudges you toward nvm, fnm, or Volta instead of the raw installer for day-to-day work.
- Corepack ships with Node. You no longer globally install pnpm or Yarn —
corepack enable wires them up from your project.
- LTS cadence is predictable. A new Long Term Support line lands each October, and the even-numbered line is what you want for anything real.
- Apple Silicon and ARM are first-class. Native arm64 builds mean no Rosetta or emulation workarounds on modern hardware.
Pick your install method
The official installer is fine for a one-off, but it makes running two projects on two Node versions genuinely painful. A version manager solves that.
| Tool |
Platform |
Best for |
Watch out for |
| nvm |
Mac / Linux |
Most people |
Shell-based; not a Windows tool |
| fnm |
Mac / Linux / Windows |
Speed, cross-platform |
Needs a shell hook in your profile |
| nvm-windows |
Windows |
Windows-only setups |
Separate project from nvm — different commands |
| Volta |
All |
Teams pinning versions |
Pins per project, which can surprise you |
| Official installer |
All |
One-off, no version juggling |
Hard to run multiple versions cleanly |
For most readers: nvm on Mac and Linux, fnm or nvm-windows on Windows. Verify the current version numbers on nodejs.org before you install — they move faster than any blog post.
Install with a version manager
On Mac or Linux, install nvm from its official repo, then reopen your terminal so the shell picks it up. From there:
nvm install --lts
nvm use --lts
nvm alias default lts/*
That last line sets the LTS as your default so every new terminal starts on it. To add a second version for an older project, run nvm install 20 and switch with nvm use 20 whenever you cd into it.
On Windows, do not use the Mac nvm — it does not work there. Install fnm or nvm-windows instead. With fnm, add its shell hook to your PowerShell profile, then run fnm install --lts. A per-project .nvmrc or .node-version file lets both nvm and fnm auto-switch versions when you enter a folder.
LTS vs Current — which version
Node ships two tracks and picking the wrong one causes real headaches.
- LTS (even-numbered): production-ready, gets bug and security fixes for roughly three years. This is your default for apps, servers, and client work.
- Current (odd-numbered): the bleeding edge for trying new APIs. Do not run production on it.
As of mid-2026 the active LTS is the Node.js 24 line, but confirm the current LTS number on nodejs.org rather than trusting a fixed figure here — the active line rotates every year.
Verify it works and start a project
After installing, check three things:
node --version
npm --version
corepack enable
corepack enable turns on managed pnpm and Yarn so you match whatever a project's package.json declares in its packageManager field — no global installs, no version drift across a team. If node --version prints the LTS you expect, you are done.
What to skip and watch out for
- Do not install Node with
sudo. If a tutorial tells you to sudo npm install -g anything, that is the classic sign the underlying setup is wrong. A version manager owns files in your home directory, so permissions never bite you.
- Skip the system package manager for Node itself.
apt install nodejs or the older Homebrew formula often lag versions behind and fight your version manager. Let nvm or fnm own Node.
- Do not install pnpm or Yarn globally in 2026. Corepack is the supported path now.
- Avoid third-party all-in-one bundles. Grab Node from nodejs.org or through your version manager, not a random installer that ships extra software you did not ask for. If you previously installed Node from a
.pkg or .msi, uninstall it first so the two do not shadow each other.
FAQ
How do I update Node.js later?
With nvm, run nvm install --lts again to pull the newest LTS, then nvm alias default lts/*. fnm uses fnm install --lts. Version managers make updates a one-liner instead of a reinstall.
Do I still need to install npm separately?
No. npm bundles with every Node release, so installing Node installs npm. Use Corepack only when you want pnpm or Yarn on top.
Can I run two Node versions at once?
Yes — that is the whole point of a version manager. Pin each project with a .nvmrc or .node-version file and let nvm or fnm switch automatically as you move between folders.
Is the official installer ever the right choice?
For a locked-down machine where you will never juggle versions, sure. For real development work, a version manager saves more trouble than it costs.
Where to go next
Once Node is running, the next questions are usually about the stack around it. If you are deciding how to ship your app, read Docker vs Kubernetes in 2026. For the front end you will pair with Node, compare React vs Vue in 2026. And to pick the editor you will live in all day, see VS Code vs Cursor in 2026.