-
Notifications
You must be signed in to change notification settings - Fork 25
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
Upgrade to Yarn 4 #8061
Upgrade to Yarn 4 #8061
Conversation
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 slightly grouped some of the more obvious ignored files. Only moved stuff around.
**/screenshots/*.diff.png | ||
**/screenshots/*.new.png | ||
|
||
# Yarn |
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.
Added a new yarn
group as described in their docs: https://yarnpkg.com/getting-started/qa#which-files-should-be-gitignored
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.
sweet 🕺
.gitignore
Outdated
!.yarn/releases | ||
!.yarn/sdks | ||
!.yarn/versions | ||
tools/proxy/.yarn/install-state.gz |
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.
why not add a wildcard à la tools/proxy.yarn/*
?
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.
Good idea.
@@ -0,0 +1 @@ | |||
nodeLinker: node-modules |
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.
out of curiousity: did you try other linkers? we don't need to switch in this pr, but I'm wondering if it's complicated.
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.
Not yet. I wasn't sure how this works together with webpack
/esbuild
.
"resolutions": { | ||
"**/mini-store": "^1.1.0", | ||
"**/redux": "3.7.2", | ||
"**/rc-resize-observer": "^1.4.0", | ||
"**/rc-util": "^5.39.1" | ||
}, |
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.
are resolutions not supported, anymore? I'm wondering whether the reasons, why we added these initially, are really obsolete now.
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.
They were outremoved. I already removed redux
, rc-*
on the react-18
branch, leaving only mini-store
. I cannot find a reference to mini-store
either... So this should be fine.
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.
really cool! I'm also very happy about the CI speed up 💯
Updated yarn to version 4 following the offical migration guide.. Except for the
.gitignore
file all files were auto-created/auto-updated.Other changes:
yarn
installation of thecommand
-JS-package during the SBT asset compilation. The package is already installed as a dev-dependency of the main yarn WK installation.Restore Cache
(51s) andSave Cache
(2 min) are slower than justyarn install
including the download (18s).Steps to test:
node
18+ is installedcorepack enable
yarn install
Issues:
(Please delete unneeded items, merge only when none are left open)