Install NPM & Node.js: Your Flawless 5-Step Guide

---

1 Overview

Node.js is a JavaScript runtime built on Chrome’s V8 engine that lets you run JavaScript outside the browser — on servers, in CLIs, and in build tooling. npm (Node Package Manager) is the default package manager for Node.js and the world’s largest software registry, with over 2.1 million published packages.

Because npm is bundled with every official Node.js installer, the practical task is really install Node.js. Once Node.js is installed, npm is available immediately — no separate install required. This guide walks through every supported platform, covers the trade-offs of each method, and ends with verification steps and troubleshooting for the most common issues.

---

2 Prerequisites

Before you install Node.js and npm, make sure your environment meets the following minimum requirements. None of these are strict blockers — a recent OS and a terminal are enough to get started — but matching these baselines avoids the most common install-time failures.

Requirement	Minimum	Recommended	Notes
Operating System	Windows 10, macOS 11, Ubuntu 20.04	Latest LTS of your OS	64-bit required for official binaries
RAM	2 GB	8 GB+	Build-from-source needs more
Disk Space	500 MB	2 GB	Includes global packages cache
Terminal Access	Required	—	PowerShell, Terminal.app, or bash/zsh
Internet Connection	Required for install	Broadband	Needed to fetch the installer and packages

---

3 Install Node.js

Node.js ships in two release lines: LTS (Long Term Support, even-numbered, production-ready) and Current (latest features, odd or even). For most users and teams, install the LTS line unless you specifically need a feature only available in Current.

---

4 Install npm

Every official Node.js installer and every nvm install ships npm as part of the bundle. Once Node.js is installed, npm is already on your machine — there is no separate npm download step.

What you may want to do separately is update npm to the latest version, switch to a faster package manager like pnpm or Yarn, or configure npm’s global install directory to avoid permission errors.

Action	Command	When to use
Check npm version	npm -v	Confirm what’s installed
Update npm (self-update)	npm install -g npm@latest	Get newest npm features
Install pnpm	npm install -g pnpm	Faster installs, saved disk space
Install Yarn	npm install -g yarn	Alternative registry client
Configure global prefix	npm config set prefix '~/.npm-global'	Avoid EACCES errors
List global packages	npm ls -g --depth=0	Audit what is installed globally

---

5 Verify Installation

After installing, run the three commands below in a fresh terminal window. Each should print a version number with no error. If any command is not found, the install did not complete or your PATH is missing the install directory — see Common Issues below.

For a deeper sanity check, create and run a tiny script that prints the Node.js version and a list of installed global packages:

# Create a working directory
mkdir ~/node-hello && cd ~/node-hello

Print versions
node -e "console.log('Node version:', process.version)"
npm -v

Initialize a project and install a package
npm init -y
npm install lodash
node -e "const _ = require('lodash'); console.log(_.chunk([1,2,3,4,5], 2))"

If the final command prints [ [ 1, 2 ], [ 3, 4 ], [ 5 ] ], your Node.js and npm installation is fully working — the runtime can execute code, npm can resolve and install packages from the registry, and modules load correctly.

---

6 Common Issues

Most install-time problems fall into one of four buckets: command-not-found PATH issues, permission errors on global installs, SSL/TLS errors behind corporate proxies, and version mismatches between Node.js and a project’s lockfile. The table below maps each symptom to its cause and fix.

Symptom	Cause	Fix
command not found: node or 'node' is not recognized	Install directory not on PATH	macOS/Linux: add ~/.nvm/versions/node/... or restart shell. Windows: reinstall with the .msi or add C:\Program Files\nodejs\ to PATH.
EACCES: permission denied on npm install -g	Global prefix owned by root	Set a user-owned prefix: npm config set prefix '~/.npm-global' and add it to PATH. Better: switch to nvm.
UNABLE_TO_VERIFY_LEAF_SIGNATURE	Corporate proxy intercepting HTTPS	Set the proxy env vars (HTTPS_PROXY) and/or npm config set strict-ssl false as a last resort.
npm ERR! code ERESOLVE peer dependency conflict	Conflicting package versions in package.json	Run npm install --legacy-peer-deps or update the offending package to a compatible version.
npm install hangs forever	Slow default registry or firewall	Switch registry: npm config set registry https://registry.npmmirror.com (mirror) or check your DNS.
nvm: command not found after install	Shell rc file not reloaded	Run source ~/.bashrc (or ~/.zshrc) or open a new terminal window.
Node version mismatch between projects	System-wide install is wrong version	Use nvm use <version> per project, or add an .nvmrc file with the target version.

---

7 Next Steps

With Node.js and npm installed and verified, you have the foundation for everything else in the JavaScript ecosystem. The next moves depend on what you want to build:

---

8 Take Action

You now have everything you need: a clear install path for every major operating system, a verification checklist, and a troubleshooting table for the most common failure modes. The only remaining step is to run the commands on your own machine.

That is the entire install story for Node.js and npm. The runtime is free, the registry is free, and the ecosystem is the largest in the JavaScript world. The fastest way to learn what Node.js can do is to run it — so open a terminal and start now.