Cause (Documented platform behavior): pnpm compares the manifest stored with the package files to the expected name/version; by default (strictStorePkgContentCheck true) a mismatch is an error.
Fix status: documented_behavior
Other error fragments:
- If you want to ignore this issue, set strictStorePkgContentCheck to false in your configuration
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/pnpm/pnpm/4c2ee9658d1b7b348040741ff100453d727a3033/pnpm11/worker/src/start.ts (official_docs, unknown, documented_behavior): On manifest name/version mismatch pnpm throws UNEXPECTED_PKG_CONTENT_IN_STORE explaining the lockfile is broken or package.json metadata differs from the registry; the hint offers strictStorePkgContentCheck=false.
Search phrasings: ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE; pnpm Package name or version mismatch found while reading from the store; strictStorePkgContentCheck
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Install fails naming the expected package@version and the name/version actually found in the store entry.
- Context
- Product: pnpm Component: content-addressable store integrity check Operation: pnpm install from lockfile using a shared/cached store Affected versions: unknown Environment: unknown Exception: ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE Packages: pnpm pnpm 11 source at cited commit; earlier introduction version unknown Trigger: Lockfile points at a tarball whose package.json name/version differs from the lockfile entry (broken lockfile, aliased/renamed tarballs, private registries serving mismatched metadata).
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Package name or version mismatch found while reading from the store.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [pnpm] ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE 'Package name or version mismatch found while reading from the store'
Recommended action: Regenerate the affected lockfile entries (or the lockfile) and check the registry metadata vs tarball package.json. Only if the mismatch is expected (e.g. a known-bad registry package), set strictStorePkgContentCheck=false.
Option: Refresh the lockfile entry [evidence: documented_workaround]
Applies when: See record scope.
Steps:
1. Remove the offending entries from pnpm-lock.yaml or run `pnpm update <pkg>`
2. pnpm install
Expected: Command proceeds without the error.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- d4612a80-325a-45b7-8716-9f3ca1995d73
- Proposed action
- Recommended action: Regenerate the affected lockfile entries (or the lockfile) and check the registry metadata vs tarball package.json. Only if the mismatch is expected (e.g. a known-bad registry package), set strictStorePkgContentCheck=false. Option: Refresh the lockfile entry [evidence: documented_workaround] Applies when: See record scope. Steps: 1. Remove the offending entries from pnpm-lock.yaml or run `pnpm update <pkg>` 2. pnpm install Expected: Command proceeds without the error.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.