Registry unreachable or slow response

- Check if registry.npmjs.org responds: `curl -I https://registry.npmjs.org` - If it times out, try switching to a mirror: `npm config set registry https://registry.npmmirror.com` - To revert back: `npm config set registry https://registry.npmjs.org` - Corporate proxies often block npm traffic — ask your sysadmin for the proxy URL and set it via `npm config set proxy`

npm ci fails in CI pipeline

- Make sure package-lock.json is committed to the repo - Ensure the lockfile version matches your npm version: `npm --version` - `npm ci` requires an exact lockfile — any mismatch between package.json and the lockfile causes it to abort - Use `npm ci --prefer-offline` to speed up repeated builds with cached packages

Back to services

Is npm Down? Live status & outage reports

Operational

Last problem:

npm outage reports00 · 00:00

npm common issues

Having issues with npm?

Tap what’s going wrong — one click helps thousands of others see the outage.

Recent Reports

No reports yet

Service info and troubleshooting

npm install fails with EACCES error: This usually means npm is trying to write to a directory it doesn't own. On Linux/macOS, avoid running npm with sudo — instead, fix the permissions on your global node_modules folder: run `npm config get prefix` to find the path, then `sudo chown -R $(whoami) <path>`. On Windows, run your terminal as Administrator.
Packages install but commands not found: After a global install, the CLI tool is nowhere to be found. The problem is almost always a missing PATH entry. Run `npm bin -g` to get the global bin directory, then add it to your shell config (~/.bashrc, ~/.zshrc, etc.). Restart the terminal after saving.
Registry unreachable or slow response: Check if registry.npmjs.org responds: `curl -I https://registry.npmjs.org`

If it times out, try switching to a mirror: `npm config set registry https://registry.npmmirror.com`

To revert back: `npm config set registry https://registry.npmjs.org`

Corporate proxies often block npm traffic — ask your sysadmin for the proxy URL and set it via `npm config set proxy`
npm publish returns 403 Forbidden: You're either not logged in or the package name is already taken. Run `npm whoami` — if it returns an error, do `npm login` first. If you're authenticated but still getting 403, the package name might be claimed by another user. Scoped packages (`@yourname/package`) solve the naming conflict problem instantly.
Lockfile conflicts after git merge: Package-lock.json conflicts are painful to resolve manually. The safest fix: after resolving package.json conflicts, delete package-lock.json and run `npm install` fresh. This regenerates the lockfile cleanly without leftover merge markers.
npm ci fails in CI pipeline: Make sure package-lock.json is committed to the repo

Ensure the lockfile version matches your npm version: `npm --version`

`npm ci` requires an exact lockfile — any mismatch between package.json and the lockfile causes it to abort

Use `npm ci --prefer-offline` to speed up repeated builds with cached packages
Peer dependency warnings block installation: Starting from npm v7, peer dependencies are installed automatically, which can cause conflicts. If you're getting ERESOLVE errors, run `npm install --legacy-peer-deps` as a short-term fix. Long-term, check which package versions are actually compatible and pin them explicitly in package.json.