pnpm
pnpm Error Codes
Error codes thrown by the pnpm package manager. These appear as the code property on errors and in pnpm's output, prefixed with ERR_PNPM_.
11 codes
· All codes 11 codes
- ERR_PNPM_FETCH_401 Registry Authentication Required The registry returned HTTP 401 Unauthorized. Authenticate by running `pnpm login` for npmjs.com, or set an auth token in `.npmrc` with `//registry.example.com/:_authToken=<token>` for private registries.
- ERR_PNPM_FETCH_403 Registry Access Forbidden The registry returned HTTP 403 Forbidden. The authenticated user lacks permission to access the package or scope. Check that the auth token is correct and that the account has read access. For private scopes, ensure the token has the appropriate read permissions.
- ERR_PNPM_LOCKFILE_BREAKING_CHANGE Lockfile Breaking Change The pnpm-lock.yaml file was written by a newer version of pnpm and uses an incompatible format. Upgrade pnpm to a version that supports the lockfile format, or regenerate the lockfile with `pnpm install --no-frozen-lockfile`.
- ERR_PNPM_MISSING_LOCKFILE Missing Lockfile pnpm was run with `--frozen-lockfile` (the default in CI environments) but no pnpm-lock.yaml exists. Commit a lockfile generated locally by running `pnpm install` and pushing the resulting pnpm-lock.yaml.
- ERR_PNPM_NO_MATCHING_VERSION No Matching Version No version of the requested package satisfies the specified version range. Check the range in package.json, verify the package name is correct, and confirm the version exists on the registry with `pnpm view <pkg> versions`.
- ERR_PNPM_OUTDATED_LOCKFILE Outdated Lockfile The pnpm-lock.yaml is out of sync with package.json. Run `pnpm install` locally to regenerate it, then commit the updated lockfile. In CI use `--frozen-lockfile` to enforce that the lockfile is always committed.
- ERR_PNPM_PEER_DEP_ISSUES Peer Dependency Issues One or more packages have unresolved or conflicting peer dependencies. pnpm enforces peer dependencies strictly by default. Either install the missing peer manually, add a `peerDependencyRules` override in package.json, or run with `--no-strict-peer-dependencies` to downgrade to a warning.
- ERR_PNPM_REGISTRY_NETWORK_ERROR Registry Network Error pnpm could not reach the npm registry or a private registry due to a network error. Check your internet connection, proxy settings, and registry URL in `.npmrc`. Try again or switch registries with `pnpm config set registry <url>`.
- ERR_PNPM_TARBALL_INTEGRITY Tarball Integrity Check Failed The downloaded package tarball does not match the expected checksum stored in the lockfile. This can indicate a network corruption, a registry publishing inconsistency, or a tampered package. Delete the pnpm store (`pnpm store prune`) and retry.
- ERR_PNPM_UNSUPPORTED_ENGINE Unsupported Engine The current Node.js or pnpm version does not satisfy the `engines` field declared in a package's package.json. Upgrade Node.js/pnpm, or override the check with `--ignore-scripts` / `engine-strict=false` in `.npmrc` if you accept the risk.
- ERR_PNPM_WORKSPACE_PKG_NOT_FOUND Workspace Package Not Found A `workspace:` protocol dependency references a package that does not exist in the monorepo workspace. Verify the package name matches the `name` field in the target package's package.json, and that the package is included in the workspace patterns defined in pnpm-workspace.yaml.