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.
Please select one of the following
Summary:
There's nothing preventing us from using yarn 4, and there are several long term benefits that could be had by being on the latest version of the package manager. Let's update! I ran the following steps:
yarn set version berry
locallylinker: "node-modules"
in the.yarnrc.yml
fileyarn
An interesting side effect is that by running
yarn
now lints/formats all thepackage.json
files in the mono repo. So that we don't maintain this extra diff, I'm opening facebook#42256 to upstream theses formats to React Native.Changelog:
[INTERNAL] [CHANGED] - Use Yarn 4 for the mono repo
Test Plan:
CI should pass. After all, running
yarn
should be the same.