We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See https://github.com/yarnpkg/berry/blob/master/CHANGELOG.md#400 for the yarn 4 CHANGELOG.
In #1541 there is an example of things that need to be done.
The text was updated successfully, but these errors were encountered:
Can I take this one sir @webmaster128 ?
Sorry, something went wrong.
I think yes, but especially for timing I wonder what is the motivation for the upgrade? Is there anything we need urgently and don't have in yarn 3?
@webmaster128 We will faster compile time and safer import check. I'm not sure if it's urgent or not but happy to work on it nonetheless ❤️🔥.
okay let's aim for this in the next breaking release. I think we can do a patch release or two without removing Node.js 16. Then we go for it
No branches or pull requests
See https://github.com/yarnpkg/berry/blob/master/CHANGELOG.md#400 for the yarn 4 CHANGELOG.
In #1541 there is an example of things that need to be done.
The text was updated successfully, but these errors were encountered: