-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
- I'd be willing to implement this feature (contributing guide)
- This feature is important to have in this repository; a contrib plugin wouldn't do
Describe the user story
As a developer, I often want to find out why a particular version of a package is in our dep tree when trying to resolve "CVEs", but the output of yarn why
can be verbose and confusing for 'core packages' that can have multiple depended on versions, such as semver
Describe the solution you'd like
yarn why
should should version selectors such as yarn why semver@npm:6.3.1
which would only show why that version is in your package. And/or, it would be useful if it supported ranges - yarn why semver@^6
for all 6.x.x versions.
Describe the drawbacks of your solution
I don't think there's many major drawbacks. Users could potentially be confused if they inadvertantly filter by a version, and this could have extra complexity in the codebase.
Describe alternatives you've considered
Rather than re-implementing yarn why
in a plugin, I feel like this is a natural extension of the existing functionality.