Error map
workspace: protocol npm ERR! code EUNSUPPORTEDPROTOCOL — Unsupported URL Type "workspace:": workspace:*
npm · layer 7, Build & delivery
Centre: this error. First ring: errors it is linked with (7). 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 (7)
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.
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.
yarn: command not found
Yarn isn’t installed (or not enabled through Corepack) on this machine.
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! cb() never called!
An old npm crash during install — usually network/cache corruption.
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.
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…
Two steps away (21)
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! 403 — You cannot publish over the previously published versions: 1.2.3
That version number has already been published (or unpublished) and can’t be reused.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
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.
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.
fatal: not a git repository (or any of the parent directories): .git
You ran a Git command outside a Git working tree.
bash: command not found
The shell can’t find an executable with that name in any directory on your PATH.
Author identity unknown *** Please tell me who you are.
Git doesn’t know your name and email for commits.
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.
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".
Error: ENOSPC: System limit for number of file watchers reached
Linux ran out of inotify watches — dev servers watching large projects hit the limit.
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 ECONNRESET — network aborted / socket hang up
The connection to the registry was reset mid-download.
npm WARN tar TAR_ENTRY_ERROR / npm ERR! tarball data for x seems to be corrupted
A downloaded package tarball is damaged — cache corruption or a network/proxy problem.
npm ERR! code ERESOLVE — unable to resolve dependency tree
npm 7+ found conflicting peer dependency requirements and refuses to install a broken tree.
HTTP 404 Not Found
The server can’t find anything at the requested URL.
[ERROR] Failed to execute goal on project x: Could not resolve dependencies for project
Maven couldn’t download or find one or more dependencies.
Map another error
Popular: 403500400TypeErrorCritical error0xC000007BNullPointerException404