Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with ... #6526

Closed
ValeryG opened this issue May 10, 2023 · 11 comments

Comments

@ValeryG
Copy link

ValeryG commented May 10, 2023

In monoreposotory getting following error

ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with packages/package1/package.json

pnpm version:

Error is not happening with pnpm ver 7 but happens in pnpm ver 8.4 & 8.5 on UBUNTU only (when running in GitHub actions).

The same version on the same repo is working just fine on Mac.

node version: 18.16

Unfortunately repository is private so I cannot provide it for debugging, but would be happy to try any suggestion or provide as much of info I can.

  • I did re-build pnpm-lock.yaml and have correct version of it when running pnpm I --forzen-lockfine.
  • My .npmrc has strict-peer-dependencies=false
@zkochan
Copy link
Member

zkochan commented May 10, 2023

Do you have node-linker set to hoisted?

@ValeryG
Copy link
Author

ValeryG commented May 11, 2023

Do you have node-linker set to hoisted?

I've tried both with and without. same symthoms - works in mac , fails in ubuntu.

@zkochan
Copy link
Member

zkochan commented May 13, 2023

Probably same as #6312

@ValeryG
Copy link
Author

ValeryG commented May 15, 2023

with 8.5.1 getting same error in Ubuntu as before, but now it is telling me failure reason:

Scope: all 20 workspace projects
Lockfile is up to date, resolution step is skipped
 ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with packages/core/core/package.json

Failure reason:
specifiers in the lockfile ({}) don't match specs in package.json ({"vue":"^3.2.47"})
Error: Process completed with exit code 1.

@jakebailey
Copy link
Member

Might be the bug fixed in my first commit of #6468?

@zkochan
Copy link
Member

zkochan commented May 15, 2023

I don't know what is happening. It would be great to have a repro repo. Maybe try to create a workspace with only package.json files and remove all private dependencies. It might be enough just to include the packages/core/core/package.json and package.json from the root of the monorepo.

@ValeryG
Copy link
Author

ValeryG commented May 15, 2023

https://github.com/ValeryG/pnpm8-issue - but of course the issue is not reproducible there. CI just works as expected on PR workflow :( https://github.com/ValeryG/pnpm8-issue/actions/runs/4985311560/jobs/8924752920

@zkochan
Copy link
Member

zkochan commented May 15, 2023

Error is not happening with pnpm ver 7 but happens in pnpm ver 8.4 & 8.5

maybe related to auto-install-peers, which became true by default in v8.

@ValeryG
Copy link
Author

ValeryG commented May 16, 2023

yes, that was it. When I am setting auto-install-peers to false - no error in ubuntu run.

@zkochan
Copy link
Member

zkochan commented May 16, 2023

your error message said

specifiers in the lockfile ({}) don't match specs in package.json ({"vue":"^3.2.47"})

If you look in you lockfile, at importers[packages/core/core].dependencies. Is there no vue?

@zkochan
Copy link
Member

zkochan commented May 17, 2023

Closing this as it is a duplicate of #6312

@zkochan zkochan closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants