-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Considerations for yarn-related packages #748
Comments
No, I think it's important to keep the history of the project. If we were to move
I think it will, yes. Right now we wanted to preserve the behaviour pretty much as it was before the Yarn 2 release so that workflows that expect a 1.x release have time to update their workflows if they need to. In a few weeks we'll start switching the tags and |
Also note that the https://github.com/yarnpkg/berry/blob/master/packages/yarnpkg-cli/bin/yarn.js |
Cool, thank you! |
Hi all, I currently use a tool called Volta to manage global JavaScript tooling. I just posted an issue there regarding Yarn 2 support and it brought up a few questions about how the official Yarn 2 launch will work:
Will the
yarnpkg/berry
repo be moved into the mainyarkpkg/yarn
repo? Because 1x and 2x are currently spread across multiple repos npm is the only canonical source of all of the 1x and 2x versions in one list: https://registry.npmjs.org/yarnThe previous docs site had a url to return the latest version of yarn. It currently redirects to the legacy docs: https://yarnpkg.com/latest-version. Will this be maintained on the new site, and should it even be used as a retrieval method of the latest version?
Super excited about the 2.0 release, and thanks for reading!
The text was updated successfully, but these errors were encountered: