Update to use Yarn v3 #828
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While this project may ultimately switch back to using npm, or may opt to use pnpm instead, Yarn 3 is a significant win for as long as this app *is* using Yarn: 1. Yarn v3 is maintained; Yarn v1 is *not*. This is the most important reason to make this switch. 2. Yarn v2+ handles peer dependencies much more rigorously than Yarn v1 (or npm), albeit not quite as well as pnpm. As part of the ecosystem's move to using properly Node-resolvable packages, we are increasingly making use of peer dependencies, so this is important future-readiness.
|
We chatted about this very briefly at the learning team meeting! We need a little time to let everyone read and think about this. We will check in again next week! |
|
Superseded by #835. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While this project may ultimately switch back to using npm, or may opt to use pnpm instead, Yarn 3 is a significant win for as long as this app is using Yarn:
Yarn v3 is maintained; Yarn v1 is not. This is the most important reason to make this switch.
Yarn v2+ handles peer dependencies much more rigorously than Yarn v1 (or npm), albeit not quite as well as pnpm. As part of the ecosystem's move to using properly Node-resolvable packages, we are increasingly making use of peer dependencies, so this is important future-readiness.