Add packageManager fields for Corepack compat #29114
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
For users with Yarn defaulted to >1 / Berry, setting up the repo will result in the creation of the
.yarn/
directory,yarn.lock
updates, andpackage.json
edits. This change enables corepack users to automatically detect and use Yarn Classic with no effect on anyone else.I targeted the latest version of Yarn Classic as a guess, since there were no engines entries to key off of. Happy to change this as desired.
How did you test this change?
Before this, running
yarn
in a fresh clone in either the root or compiler workspaces resulted in Yarn Berry making the above changes to the repo: 2000+.yarn/cache
entries, lockfile regeneration, andpackage.json
formatting changes.After this,
yarn
is handled by Yarn Classic as expected and no changes occur (and repo functions as expected).