Is pnpm status down? User reports show no current problems with pnpm status

Is pnpm Down Right Now?

Short answer: pnpm runs on your machine, so a pnpm outage in practice means an install that fails or hangs for you. Registry trouble is the only part that can fail for everyone at once.

This page tracks the pnpm status through reports from JavaScript developers. It covers local installs, CI pipelines, and the npm registry that pnpm pulls packages from.

Below are the errors that stop installs most often, what each code means, and the fixes. Read the first error line in the output; pnpm prints the real cause before the noise. Plenty of users then check Podman status as well, to see whether the problem reaches beyond one tool.

Is pnpm Down for Me or Everyone?

So is pnpm down for me, or is the registry down for everyone? Try installing one tiny package in an empty folder and watch the result.

If that works, your project, its lockfile, or its cache holds the fault. If it fails the same way, test whether the npm registry answers at all, since pnpm cannot install without it.

CI failures tell a different story. Pipelines use frozen lockfiles by default, so a lockfile that is fine locally can fail CI after any package.json change.

Why Does pnpm Fail With ERR_PNPM_OUTDATED_LOCKFILE?

This error means package.json and pnpm-lock.yaml disagree. Someone changed a dependency and forgot to update the lockfile, or merged code that updated only one of the two files.

CI hits it most because pipelines install with a frozen lockfile. Locally the fix is simple: run pnpm install once to refresh the lockfile, then commit both files together.

If the error appears with no changes at all, check that CI uses the same pnpm version as your team. A newer pnpm can write a lockfile format an older one rejects.

Why Is pnpm Install So Slow or Stuck?

pnpm is normally fast, so a stuck install points to the network, the registry, or the store. A registry that answers slowly makes every fresh install crawl.

A damaged store also slows things down. pnpm links files from a global store, and a store on a nearly full or failing disk turns linking into a grind.

Watch disk space and try pnpm store status. If the store looks broken, prune it or delete it and let pnpm rebuild it on the next install.

Common pnpm Problems and Fixes

ERR_PNPM_OUTDATED_LOCKFILE in CI

Run pnpm install locally so the lockfile matches package.json, then commit both files. In CI, keep frozen installs on, since they catch exactly this drift. Match pnpm versions between local and CI too.

ERR_PNPM_NO_MATCHING_VERSION Found

The version you asked for does not exist in the registry, or your registry mirror lags behind. Check the package page for real versions, fix typos in ranges, and confirm your .npmrc points at the right registry.

ERR_PNPM_FETCH_404 for a Package

A 404 means the registry has no such package or version. The package may be private, removed, or under another name. For private scopes, sign in to the registry and check your token rights.

Code Works With npm but Fails With pnpm

pnpm builds a strict node_modules layout, so packages that rely on undeclared dependencies break. Add the missing package to your own dependencies. This is the famous phantom dependency problem, and the fix belongs in your project.

node_modules Looks Broken After an Install

A half-finished install leaves a mixed tree. Delete node_modules and run a fresh pnpm install. Avoid running npm or yarn in the same project, since mixed managers corrupt each other’s layouts.