Node.js on Windows: LTS or Current, MSI or zip
Node.js runs JavaScript outside the browser. Many people install it not to write servers but because a project's README says "run npm install", or because a tool such as a site generator or a linter is built on it. Either way, the setup on Windows is short. The one decision that matters is which release line to take.
Node.js is free and open source under the MIT licence.
LTS or Current?
The download page always shows two lines:
- LTS (long-term support): the stable line. According to the project's release page, critical bugs are typically fixed for 30 months, and production applications should only use LTS releases.
- Current: the newest major version, for its first six months. It is there so library authors can test against it.
Take LTS unless a project explicitly asks for something newer. The file our catalogue hosts is the Windows x64 installer from an LTS line.
The Windows files
For each release Node.js publishes:
- .msi installer for x64 or ARM64. It sets up Node, npm and the PATH entries in one go. This is the simplest choice.
- .zip and .7z archives for x64 or ARM64. Unpack them anywhere and add the folder to PATH yourself. Useful when you cannot run installers.
There is no 32-bit Windows build in the current releases.
Installer or version manager?
The npm documentation strongly recommends a Node version manager instead of the installer, partly to avoid permission problems with globally installed packages. A version manager also lets you switch quickly between the Node versions different projects want. The installer is fine if you only ever need one version. The download page points out that the third-party installation methods it lists are not maintained by the Node.js project itself.
Checking it worked
Open a new terminal window, so it picks up the new PATH, and run:
node -v
npm -vBoth should print a version. Then, in a project folder that has a package.json, npm install fetches its dependencies into node_modules, and npm run lists the scripts the project defines.
A note on PowerShell
If PowerShell refuses to run npm with a message about scripts being disabled, the quickest workaround is to use Command Prompt or call npm.cmd instead of npm. Change PowerShell's execution policy only if you understand what it controls.
Updating
Node does not update itself. To move to a newer release, run the newer MSI over the old one, or switch with your version manager. When an LTS line nears the end of its support, move to the next LTS rather than to Current.
FAQ
Is Node.js free?
Yes. It is open source under the MIT licence and free for any use.
Does the installer include npm?
Yes. The npm documentation confirms that a Node installer sets up both Node.js and npm.
Which download do I need for Windows on Arm?
The ARM64 MSI, or the ARM64 zip if you would rather not install.
Why does my project need a specific Node version?
Dependencies are often tested against particular major versions. Check the project's package.json or README, and use a version manager if your projects disagree.
- Best for
- Web developers, and anyone a project's instructions tell to run npm install.
- Good to know
- No 32-bit Windows build is offered, and production work should stay on an LTS line.
Tools to go with Node.js
You will want an editor such as Visual Studio Code, and Git for Windows to clone projects and track your own changes.