Open Netail opened 1 month ago
Important parts in the repro;
package.json
(versions defined)
https://github.com/Netail/repro-yarn-lock/blob/main/apps/web/package.json#L5-L8
yarn.lock
(how the yarn.lock entries also should look like after being pruned)
https://github.com/Netail/repro-yarn-lock/blob/main/yarn.lock#L25-L41
Currently blocking us from optimally using prune in our CI as we have to delete the pruned yarn.lock and generate a new yarn.lock based on the pruned repo. Slowing the pipeline a bit :(
Verify canary release
Link to code that reproduces this issue
https://github.com/Netail/repro-yarn-lock
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
2.0.11
Describe the Bug
Pruned yarn.lock results in merging
npm:
prefixed versions & non-prefixed versionsExpected Behavior
Split yarn.lock entries starting with the
npm:
prefixTo Reproduce
Additional context
This issue got fixed in Yarn 1.22.22 with https://github.com/yarnpkg/yarn/pull/9023.
A full thread on the issue; https://github.com/yargs/cliui/issues/138