Post

Doug Parker
@develwithoutacause.dwac.dev

``` $ pnpm install # Success! $ pnpm install --frozen-lockfile Scope: all 15 workspace projects Error: ERR_PNPM_OUTDATED_LOCKFILE ``` 🤨

0 reposts4 likes

Doug Parker
@develwithoutacause.dwac.dev

#TIL `pnpm install --fix-lockfile`, which was apparently the solution I needed. And really begs the question of "What does `pnpm install` do the lockfile if not fix it? Is it `--break-lockfile` by default?"

naugtur
@naugtur.pl

Back in npm6 time I had some CI processes call `npm install` twice for good measure. These days it's rare but there are still some little details that change on the second run. Deterministically resolving a graph this complex is hard

Doug Parker
@develwithoutacause.dwac.dev

Credit where it's due, Alan followed up with a bug and pnpm fixed it basically immediately. 😯 github.com/pnpm/pnpm/is...

github.com[v12] Updating dependency from prerelease (e.g. `X.Y.Z-rc.0`) to stable (`X.Y.Z`) retains `X.Y.Z-rc.0` in lockfile, causing `pnpm install --frozen-lockfile` to fail · Issue #15528 · pnpm/pnpmVerify latest release I verified that the issue exists in the latest pnpm release pnpm version 12.6.0 (regression from 11.27.1; also reproduces in 12.4.2) Which area(s) of pnpm are affected? (leave...