Use Yarn modern #9324
Closed
Use Yarn modern #9324
Conversation
This file contains 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
|
No idea why some integration tests fail consistently, they do work fine locally for me. |
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.
This should help with the constant Yarn install timeouts we have on CI
Using pnpm would probably break lerna (though I haven't tested if the publish scripts still work now with the new Yarn)
"Known issues":
"scripts": {"x": "echo x"}and thenyarn xtakes 1 second for me: [Feature] Improve performance ofyarn runyarnpkg/berry#2575yarn install(e.g. running twice in a row) still takes 3.5sBugs preventing the pnpm linker:
turbowhen usingnodeLinker: pnpmwith v4 yarnpkg/berry#5165 (only with Yarn 4 though)