Closed wSedlacek closed 1 year ago
Thank you @wSedlacek for reporting the issue.
Can you provide a minimal reproduction repo, or at least the root pnpm-lock.yaml
and resulting package.json
so we can investigate what is happening?
In the meantime, can you try to remove node_modules
and pnpm-lock.yaml
and regenerate them with pnpm i
just to make sure this is not a result of messed up packages?
In the meantime, can you try to remove node_modules and pnpm-lock.yaml and regenerate them with pnpm i just to make sure this is not a result of messed up packages?
I have attempted this and I get the same results.
I have also attempted to install the dependencies that report to be broken directly and with some of them they get fixed, but with others they don't.
I have also tried enabling dedupe-peer-dependents=false
as this changed between pnpm 7 and 8.
This does cause different packages to be reported as missing in the lock file than without it.
Can you provide a minimal reproduction repo, or at least the root pnpm-lock.yaml and resulting package.json so we can investigate what is happening?
Here are the generated package.json
and pnpm-lock.ymal
output.zip
When installing they give this error
#11 4.385 WARN Broken lockfile: no entry for '/node-fetch/2.6.11(encoding@0.1.13)' in pnpm-lock.yaml
#11 4.388 ERR_PNPM_ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY The lockfile is broken! Resolution step will be performed to fix it.
It is generated from this lockfile pnpm-lock.yaml.zip
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
When building a project that generates a lock file with pnpm it comes out broken (when trying to install it errors like the following are reported)
Expected Behavior
Lockfiles should contain all references such that they are considered to be valid by pnpm
GitHub Repo
No response
Steps to Reproduce
pnpm install
Note: Issue depends on dependency tree of that project.
Nx Report
Failure Logs
No response
Operating System
Additional Information
This issue did not occur in 15