Error AtlasError Documentation and Resolutionnpm documented errors
Browse npm error codes and npm troubleshooting pages across package installation, dependency resolution, registry access, authentication, and local environment setup.
This npm error reference is designed for users searching exact npm error messages, error codes, and clear how-to-fix guidance.
npm troubleshooting is often a mix of registry access, package resolution, authentication, filesystem permissions, and local environment issues. Many npm searches start with a short code like `EACCES` or `ERESOLVE`, but the real fix depends heavily on the install context.
This hub keeps npm error codes and install failures in one searchable reference so users can compare package-manager issues without jumping between multiple docs or forum answers.
Authentication
Authentication errors
Configuration
Configuration errors
Installation
Installation errors
cb() never called!npm cb() never called when using shrinkwrapped dependenciesnpm can fail with cb() never called due to a subtle race condition involving shrinkwrapped dependencies, especially on older npm versions.
ENOGIT / not found: gitnpm could not find gitnpm can fail with ENOGIT or not found: git when a package or install path depends on git but git is not installed or not available on PATH.
ENOSPCnpm could not write because the drive is full or not writablenpm could not complete the install because the target drive or temporary directory had no available space or could not be written to.
EACCES permissions errornpm EACCES permissions error during global installnpm reports EACCES during global installs when npm writes into directories owned by the system instead of the current user.
Error: ENOENT, stat C:\Users\<user>\AppData\Roaming\npmnpm ENOENT for AppData Roaming npm directory on Windowsnpm can fail with ENOENT on the AppData Roaming npm directory when the expected npm user directory does not exist or is not writable on Windows.
No spacenpm failed because the system ran out of disk spacenpm ran out of available disk space while writing files, extracting packages, or updating local installation state.
Running a Vagrant box on Windows fails due to path length issuesnpm failed in a Windows Vagrant box due to path length limitsnpm installations inside a Windows-backed Vagrant box can fail because nested dependency paths exceed Windows path length limits.
npm hangs on Windows at addRemoteTarballnpm hangs on Windows at addRemoteTarballnpm can hang on Windows during addRemoteTarball when more than one tmp directory is configured in .npmrc.
Broken npm installationnpm installation is brokennpm is not functioning correctly due to a damaged local installation, often requiring reinstallation of npm or Node.js depending on the platform.
Permissions errorsnpm permissions errors during install or executionnpm encountered filesystem permissions problems while trying to read, write, or install packages, usually because the current user cannot access the configured directories.
ENOENT / ENOTEMPTY errors in outputnpm produced many ENOENT or ENOTEMPTY errorsnpm can emit many ENOENT, ENOTEMPTY, lstat, chmod, or unlink errors during install when concurrent work triggers race conditions, especially on older npm versions.
Random npm errorsnpm random install or command errorsnpm can surface vague or inconsistent errors when local cache or install state is unhealthy, and the official first-line remediation is to clean cache and retry with verbose logging.
No compatible version foundnpm reported no compatible version foundnpm reports that no compatible version could be found when the local npm installation is outdated for the requested operation or package resolution path.
Networking
Networking errors
npm only uses git: and ssh+git: URLs for GitHub repos, breaking proxiesnpm GitHub git and ssh URLs are breaking behind a proxynpm can fail to fetch GitHub-based dependencies behind a proxy because git: and ssh+git: URLs bypass the proxy-friendly HTTPS path.
SSL-intercepting proxynpm is behind an SSL-intercepting proxynpm is encountering TLS and certificate problems because network traffic is being intercepted and re-signed by a proxy between the client and the npm registry.
CERT_UNTRUSTED / UNABLE_TO_VERIFY_LEAF_SIGNATUREnpm SSL certificate is untrusted or leaf signature cannot be verifiednpm could not validate the TLS certificate chain for the registry connection, often because of outdated runtime support, custom CA issues, or an inspecting proxy.
SELF_SIGNED_CERT_IN_CHAINnpm SSL self signed certificate in chainnpm received a self-signed certificate in the SSL chain, often due to outdated npm certificate handling or an intercepting corporate proxy.
SSL23_GET_SERVER_HELLO:unknown protocolnpm SSL unknown protocol errornpm tried to speak SSL to an endpoint that was not actually serving SSL, which usually points to a proxy or registry configuration problem.
Package Managers
Package Managers errors
Registry
Registry errors
Error: Invalid JSON / Unexpected token <npm registry response produced invalid JSONnpm received invalid JSON where it expected package metadata, often because of a temporary registry issue, a corrupted local cache, an invalid package.json, or a corporate proxy returning HTML.
404 Not Found / Server errornpm registry returned 404 or server errornpm can fail with 404 or 500 responses when the registry is temporarily unhealthy, the package tarball path is unavailable, or a published package is corrupt.