Error map
EPUBLISHCONFLICT npm ERR! 403 — You cannot publish over the previously published versions: 1.2.3
npm · layer 7, Build & delivery
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
npm ERR! code E402 — 402 Payment Required - PUT https://registry.npmjs.org/@scope%2fpkg - You must sign up for private packages
You published a scoped package without --access public, so npm tried to publish it as private.
Error: Cannot find matching keyid (Corepack signature verification)
An older Corepack couldn’t verify the signature of a newly published pnpm/yarn release after npm rotated its signing keys.
npm ERR! code E401 — Unable to authenticate, need: Basic realm / Incorrect or missing password
The registry rejected your credentials — missing, expired or wrong auth token.
npm ERR! code ENEEDAUTH — need auth This command requires you to be logged in
npm needs credentials (publishing, private packages) but none are configured for that registry.
npm ERR! code EOTP — This operation requires a one-time password from your authenticator
Your npm account has 2FA for writes and no one-time password was supplied.
npm ERR! cb() never called!
An old npm crash during install — usually network/cache corruption.
Error response from daemon: client version 1.45 is too new. Maximum supported API version is 1.41
Your Docker CLI (or SDK) speaks a newer API version than the Docker daemon it’s talking to.
npm ERR! code E403 — 403 Forbidden - PUT https://registry.npmjs.org/x - You do not have permission to publish
The registry refused the operation — the package name is taken, you lack publish rights, or 2FA/policies block it.
Two steps away (24)
Error: ENOSPC: System limit for number of file watchers reached
Linux ran out of inotify watches — dev servers watching large projects hit the limit.
npm ERR! code EUNSUPPORTEDPROTOCOL — Unsupported URL Type "workspace:": workspace:*
npm met the workspace: protocol used by pnpm/yarn, which npm doesn’t support.
npm ERR! code EEXIST — EEXIST: file already exists, symlink '../lib/node_modules/x/bin/x' -> '/usr/local/bin/x'
A global install can’t create its command link because a file with that name already exists.
Authentication plugin 'caching_sha2_password' cannot be loaded
An old MySQL client/driver can’t use MySQL 8’s default authentication plugin.
npm ERR! could not determine executable to run
npx couldn’t find a binary to run for that package.
npm WARN old lockfile — The package-lock.json file was created with an old version of npm, so supplemental metadata must be fetched
The lockfile is lockfileVersion 1 (npm 6) and npm 7+ is upgrading it.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
npm ERR! code E404 — 404 Not Found: package@version is not in this registry
npm asked the registry for a package (or version) that doesn’t exist there — a typo, a private/scoped package without auth, or th…
npm ERR! code ETARGET — No matching version found for package@^9.9.9
The version range in package.json doesn’t match any published version of the package.
OAuth 2.0 Error: invalid_grant
The authorization code, refresh token or credentials sent to the token endpoint are invalid, expired, already used or were issued…
API Error: Invalid API Key / Incorrect API key provided
The API didn’t recognise the key sent with the request — it’s wrong, revoked, from another environment, or sent in the wrong plac…
{"message":"Missing Authentication Token"} / No authorization token was found
The request reached a protected endpoint without credentials — or, on AWS API Gateway, it hit a path/method that doesn’t exist.
invalid_token: The access token is invalid (JsonWebTokenError: invalid signature / jwt malformed)
A token was sent but the server couldn’t verify it — bad signature, malformed, revoked, or issued for another audience or environ…
denied: Your authorization token has expired. Reauthenticate and try again. (Amazon ECR)
Docker’s login to Amazon ECR has expired — ECR tokens last 12 hours, so pushes and pulls fail until you log in again.
UnrecognizedClientException: The security token included in the request is invalid
The access key or session token isn’t recognised — wrong/deleted key, a session token missing for temporary credentials, or a reg…
npm ERR! code EINTEGRITY — sha512 integrity checksum failed
A downloaded package’s hash doesn’t match the integrity value in package-lock.json — a corrupted cache, a changed tarball, or a l…
npm ERR! Missing script: "start"
The script name you ran isn’t defined in package.json "scripts".
gyp: No Xcode or CLT version detected!
node-gyp on macOS can’t find the Xcode Command Line Tools to compile native modules.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.
invalid mount config for type "bind": bind source path does not exist
A -v/--mount or Compose volume points at a host path that doesn’t exist (from the Docker daemon’s point of view).
dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
npm ERR! code ETIMEDOUT — network request to https://registry.npmjs.org/x failed, reason: connect ETIMEDOUT
npm couldn’t reach the registry in time — network, proxy or firewall issue.
npm ERR! code ECONNRESET — network aborted / socket hang up
The connection to the registry was reset mid-download.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException