fix: Yarn 2+ no longer include peer dependencies in AllDependencies #2745
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
|
@chris-olszewski is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Ignored Deployments
|
nathanhammond
approved these changes
Nov 17, 2022
…uned-lockfile-unable
chris-olszewski
deleted the
chrisolszewski/turbo-554-failed-to-encode-pruned-lockfile-unable
branch
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.
Solves the issue that @jsbrain found in #2313. Still unable get reproduce the original issue.
The underlying issue was that
refine-antdlistedantdas a peer dependency and direct dependency with different version constraints and thepeerDependencyversion was overriding the direct version.We ran into a similar issue with pnpm that I fixed in #2151. I'll be investigating if we need to do something similar for npm as well.