Use an equivalent lockfile for v1 #2
Merged
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
This dramatically affects times for the v1 install, increasing it from 25s to 60s. (The v2 install is ~40s.)
Merged
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 dramatically affects times for the v1 install, increasing it from 25s to 60s. This makes Yarn 2 installs faster as it is around 40s on my machine.
The issue was that originally, the
packages-v1folder was created as a copy ofpackages-v2and runningyarnin it to "downgrade" theyarn.lockfile to v1. However, Yarn doesn't downgrade formats – it basically recreatedyarn.lockfreshly, which lead to a much simpler install structure. That made the comparison unfair.It was spotted by @larixer – thanks a lot! See Discord chat.