Reimplements yarn explain peer-requirements #5834
Merged
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.
What's the problem this PR addresses?
I didn't update the
yarn explain peer-requirements
when I refactored the peer dependency warnings to report aggregates rather than independent entries. As a result, the reported hash doesn't work.Fixes #5826
How did you fix it?
I reimplemented
yarn explain peer-requirements
to take those warnings into account. I also updated the output to use a more natural language which might help better understand the situation:Note that I temporarily removed support for calling
yarn explain peer-requirements
on missing peer dependencies, as I'd like to take another look at those warnings in general (I noticed they aren't aggregated, but they probably should be too). Since they are fairly easy to understand by themselves, I don't feel like this is a significant regression.Checklist