-
Notifications
You must be signed in to change notification settings - Fork 344
chore: migrate to yarn v4 #6695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
86965b9
to
99c2476
Compare
"generateVersions": "node scripts/generateVersion", | ||
"bumpVersions": "yarn changeset version && yarn generateVersions" | ||
"bumpVersions": "yarn changeset version && yarn generateVersions", | ||
"g:jest": "cd $INIT_CWD && jest", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm curious why we need these scripts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is due to this problem: yarnpkg/berry#2825
The solution is described here: https://yarnpkg.com/getting-started/qa/#how-to-share-scripts-between-workspaces
1cff4ea
to
4793867
Compare
5bf022c
to
e0bcd48
Compare
e0bcd48
to
447f7e7
Compare
Description of changes
Migrate from yarn v1 to yarn v4 (modern)
Description of how you validated changes
Ran build and test scripts in all packages
Checklist
yarn test
passes and tests are updated/addeddocs
,e2e
,examples
, or other private packages.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.