-
Notifications
You must be signed in to change notification settings - Fork 21
Experiment with yarn 2 on workshop repo #138
Comments
Support was added on 04/05 prettier/prettier-vscode#1293 |
yarn v2 migration is not straight-forward, and has many issues yarnpkg/berry#843
|
yarn v2 is stable, and 2.1 was released on July 9th |
Comparison between yarn 1 vs yarn 2 vs npm from Feb 2020 Conclusion: it's better to stick with yarn 1 primarily because of broad support and build speed. |
Update: yarn 2.2 is released on Aug 28th https://dev.to/arcanis/yarn-2-2-dedupe-faster-lighter-ha5 New features:
The yarn team is in discussion with Node TSC to bundle yarn with node in some capacity nodejs/TSC#904 |
The original creator of yarn is not supportive of yarn 2 (berry) |
Update: yarn 2.3 released on Oct 2nd: https://dev.to/arcanis/yarn-2-3-info-command-detailed-options-nohoist-409h
|
Update: yarn 2.4 released on Nov 30th: https://dev.to/arcanis/yarn-2-4-log-filters-audits-better-warnings-49io
|
Is your feature request related to a problem? Please describe.
Not a problem, but yarn v2 was announced in January 2020:
Describe the solution you'd like
Once yarn 2 is stable, experiment with using it in workshop repo. So that we can use it on main repo aws/aws-sdk-js-v3 if it's helpful.
Describe alternatives you've considered
Stick with yarn 1
The text was updated successfully, but these errors were encountered: