ERR_PNPM_OUTDATED_LOCKFILE 📦 npm

ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json

pnpm’s lockfile doesn’t match package.json, and CI installs with a frozen lockfile.

Seen on: npm

Meaning

The pnpm equivalent of npm ci being out of sync. Update the lockfile locally and commit it.

Common causes

  • package.json changed without updating pnpm-lock.yaml
  • Different pnpm versions locally and in CI

⚡ Quick fix

  1. Run pnpm install locally and commit the lockfile
  2. Pin the pnpm version (packageManager field)

Detailed fix by platform

npm

  1. "packageManager": "pnpm@9.12.0"

How to diagnose

  1. Versions — pnpm -v locally vs CI
  2. Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.