Upgrade from Yarn v1 to v3 while keeping node_modules #160
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 pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/kachkaev/njt/7qfNdC8QqiVsg9vdmUSNKD4ZnDqk |
kachkaev
force-pushed
the
yarn-berry-with-node-modules
branch
from
ff66426
to
57636f1
Compare
This was referenced Nov 21, 2021
Closed
|
Mission complete! 🕺 |
3 tasks
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 PR is a smaller version of #29. It upgrades Yarn, but does not migrate to PnP, which can be done separately.
Note that I had to stop using Snyk integration because it did not support
yarn.lockv2: https://github.com/snyk/snyk/issues/1518#issuecomment-974822508