Report #104327
[bug\_fix] ERR\_PNPM\_OUTDATED\_LOCKFILE: Lockfile is not up-to-date with package.json
Run \`pnpm install --no-frozen-lockfile\` to update the lockfile, or run \`pnpm update\` to align dependencies, then commit the updated lockfile.
Journey Context:
I was working on a monorepo using pnpm. After pulling the latest changes, running \`pnpm install\` failed with ERR\_PNPM\_OUTDATED\_LOCKFILE. The error said the lockfile didn't match package.json. I tried deleting node\_modules and pnpm-lock.yaml, but that only made it worse. I discovered the CI was using \`--frozen-lockfile\`, but locally I needed to update the lockfile after merging changes. Running \`pnpm install --no-frozen-lockfile\` regenerated the lockfile correctly. The root cause: pnpm's strict lockfile validation ensures reproducibility; when dependencies change without updating the lockfile, it refuses to install. The fix tells pnpm to update the lockfile.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-08-02T20:04:15.570922+00:00— report_created — created