Setup Yarn 3
Summary
Let's see how it goes
Test plan
⚠️ No Changeset found
Latest commit: 1dfbb9457131339b8744bd3c59ac7cb20b434a28
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
If you aren't committing the cache to the repo then maybe enableGlobalCache would be good in the yarn config.
@satya164 maybe we should commit the cache to the repo. Any experiences, pros/cons?
@thymikee cons: cloning the repo took significantly more time and made diffs harder to read when there were dep changes, pro: super quick to switch branches with different deps, simple CI setup since no caching-related config needed.
Build fails with example-native:build: Unknown Syntax Error: Unsupported option name ("--force"). Seems like our yarn install --force invocation.
@satya164 thanks. For now I think we'll keep the global cache behavior. when switching branches locally on a hot cache it's pretty fast already
Closing as stale.