Repository navigation
pnpm install --frozen-lockfile now fails when some workspace packages are missing #16453
Description
Last pnpm version that worked
12.5.1 (maybe some later versions too)
pnpm version
12.8.2
Code to reproduce the issue
pnpm-workspace.yaml:
packages:
- server
- tests
...Dockerfile:
COPY --exclude=tests . ./
RUN pnpm install -r --offline --frozen-lockfileExpected behavior
#30 0.518 Scope: all 5 workspace projects
#30 0.646 ✓ Lockfile passes supply-chain policies (verified 18h ago)
#30 0.646 Lockfile is up to date, resolution step is skipped
#30 0.815 Already up to date
#30 0.979 Done in 470ms using pnpm v12.5.1
Previously we were able to exclude unrelated workspace packages from the image (smaller image, faster CI build). pnpm install --frozen-lockfile just accepted it.
Actual behavior
#26 0.474 Scope: all 4 workspace projects
#26 0.526 Error: ERR_PNPM_OUTDATED_LOCKFILE
#26 0.527
#26 0.527 × installing dependencies
#26 0.527 ╰─▶ Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up
#26 0.527 to date with package.json.
#26 0.527
#26 0.527 Failure reason:
#26 0.527 the lockfile records `importers["tests"]`, but that project's
#26 0.527 directory or package.json is missing
#26 0.527 help: Regenerate the lockfile with `pnpm install --lockfile-only` so that
#26 0.527 pnpm-lock.yaml reflects the current package.json, then re-run `pnpm
#26 0.527 install --frozen-lockfile`.
Additional information
No response
Node.js version
v24.13.0
Operating System
Linux
Contributing a fix
- I am working on a fix
Activity
[-]`pnpm install -r --offline --frozen-lockfile` now fails when some workspace packages are missing[/-][+]`pnpm install --frozen-lockfile` now fails when some workspace packages are missing[/+]runspired commentedon Sep 30, 2026
potentially a duplicate of #16428 which had a fix PR committed earlier today
KazimirPodolski commentedon Sep 30, 2026
I'll check when it ships!
tunglambk commentedon Oct 1, 2026
I reproduced this on pnpm 12.8.1 with a minimal workspace: generate a lockfile with
serverandtestsimporters, removetests/, then runpnpm install --frozen-lockfile; it fails withERR_PNPM_OUTDATED_LOCKFILEfor the missing importer.The failure comes from the missing-importer check added in #15427, which intentionally made an unfiltered frozen install fail when a lockfile-listed project's directory or manifest is missing. A Docker context that excludes one project is indistinguishable to that check from a deleted project. This is a different check from #16428's injected optional-peer freshness issue.
Before proposing a change that would reverse part of #15427's behavior, can a maintainer clarify the intended contract here? Should Docker builds select the projects present in the build context with
--filter, or should pnpm add an explicit way for an unfiltered frozen install to tolerate missing importer directories (which would also tolerate genuinely deleted projects)?Written by an agent (Codex, GPT-6).
zkochan commentedon Oct 1, 2026
#16462 restores the pre-12.8.0 behavior for this case. An unfiltered
pnpm install --frozen-lockfilenow skips a lockfile importer whose project directory is absent, so a Docker build context that excludestests/installs again. It still fails if the directory exists without apackage.json, which keeps the check from #15427 for that case. The fix covers both pnpm 12 and pnpm 11 and fully addresses this issue.Written by an agent (Claude Code, claude-opus-5-5).
fix(install): let a frozen install skip absent workspace project dirs (…
fix(deps): update dependencias no-major (#23)
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0
hoangzunguyen44-hub commentedon Oct 17, 2026
pnpm install --frozen-lockfile
cp .env.example .env
redis-server
pnpm dev