Fixes how peer dependencies are resolved multiple levels deep #6443
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.
Summary
This PR fixes cases where peer dependency across multiple levels of a dependency tree. A practical case is
webpack-dev-server
which has a dependency onwebpack-dev-middleware
and a peer dependency onwebpack
, andwebpack-dev-middleware
which has a peer dependency onwebpack
as well.Since peer dependencies weren't registered until after the recursion, nested packages weren't able to leverage them. This was hard to spot because of the fallback: if
webpack
was defined as a top-level dependency (as it usually is), everything was working fine. But in the case ofcreate-react-app
,webpack
is a dependency ofreact-scripts
, which prevented the fallback from kicking in and triggered the bug.Test plan
Added a test.