Node.js: the JavaScript runtime that runs your toolchain
What it does
Node.js is a runtime that executes JavaScript outside the browser, built on the V8 engine with an event-driven, non-blocking I/O model. On Windows it installs as a standard MSI package and provides the node interpreter, the npm package manager, and the npx runner used to execute one-off packages. For most desktop developers its real importance is indirect: almost every modern web build pipeline, test runner, linter, bundler and many command-line utilities are distributed through npm and expect a Node runtime to be present. It is equally capable as an application platform in its own right, hosting HTTP services, background workers, socket servers and Electron-based desktop applications.
The workflow
Installation is deliberately plain. Run the MSI, keep the default component set, and let it add Node and npm to the PATH. The installer offers to add the native build tools needed to compile native addons; this pulls a Python installation and Visual Studio build components, so it is worth declining unless you actually need to compile modules from source. After installation, open a fresh terminal and confirm the versions, then create a project with npm init, install dependencies, and use npm scripts in the project manifest as the single entry point for build, test and lint commands so that CI and local development stay identical.
Practical settings and limits
Two release channels matter: Long Term Support versions receive security and stability fixes for years and are the right choice for anything you must maintain, while Current versions carry the newest language features with a shorter support window. The npm global prefix on Windows lives in the user profile, so global installs rarely need administrator rights, which is convenient but also means machine-wide CLI tools are per-user. The runtime has no built-in process manager, so long-running services rely on the Windows service wrapper or a supervisor. Package installation reaches out to a public registry and executes lifecycle scripts, so corporate networks usually want an internal mirror and a lockfile policy.
Who should choose something else
Deno and Bun offer TypeScript-first runtimes with different security and dependency models and are worth evaluating for greenfield services. Python, Go, or .NET are better choices for CPU-bound workloads where a single-threaded event loop is the wrong shape. If you only need to run a packaged web application that bundles its own runtime, installing Node separately adds nothing.
- Best for
- Running npm-based build tooling and hosting lightweight JavaScript services locally.
- Good to know
- Prefer an LTS release for production work; the installer can optionally add native build tools for compiling addons.
Node.js runs JavaScript outside the browser. The Windows installer adds the runtime plus the npm package manager in one step, which is what most front-end build pipelines, linters and CLI tools expect to find on a development machine.
How to get started
- Open the official Node.js download page and pick the Windows Installer for the LTS line.
- Run the MSI and accept the licence agreement.
- Keep the default options, which add Node and npm to the system PATH.
- Skip the native module tools unless you plan to compile addons from source.
- Open a new terminal and check
node -vandnpm -v, then scaffold a project withnpm init -y.
Questions & answers
Should I install LTS or Current?
Install LTS for almost everything. Current ships newer language features but has a short support window, so it suits experimentation rather than machines you depend on.
Do I need administrator rights?
No for the default per-machine install done once by an administrator, and no for global npm packages, which install into your user profile. Machine-wide service installs still need elevation.
Is npm installed as well?
Yes. npm ships with the runtime, along with npx for running packages without a permanent install. You can switch to pnpm or yarn later without reinstalling Node.
