Repository navigation
Rewriting a pnpm 12 lockfile drops the leading packageManagerDependencies document
#1822
Unanswered
mwolson
asked this question in
Troubleshooting and Bugs
Replies: 2 comments
|
Opened a fix: #1842 — rewrites now keep pnpm's leading AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable. |
0 replies
|
Implemented in #1842: fix(lockfile): keep pnpm's leading environment document on rewrite |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
pnpm12-package-manager-document-drop2.8.2 linux-x64 (2026-10-23)When
package.jsonhas"packageManager": "pnpm@12.14.0", pnpm 12 writespnpm-lock.yamlas two YAML documents. The first recordspackageManagerDependenciesfor pnpm itself. aube reads this shape (#116), butaube add is-number@7.0.0writes only the project document. pnpm 12.14.0install --frozen-lockfilethen fails withERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE("Cannot update packageManagerDependencies with "frozen-lockfile" because the lockfile is not up to date"). pnpm's own add keeps the document.Putting the original first document back makes pnpm accept the rest. Found in pingdotgg/t3code.
All reactions