We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It'd be awesome if the report indicated whether a dep was top-level, or if not, which packages caused it to be included.
The text was updated successfully, but these errors were encountered:
@ljharb I suspect read-package-tree includes that information in records. Perhaps "encoded" in the module's path.
read-package-tree
The place to bring that in is probably
licensee.js/index.js
Line 175 in 8c6b68f
The place to print it out is probably
licensee.js/licensee
Line 143 in 8c6b68f
I'm a bit slammed. Feel free to send a PR. npm run style lints.
npm run style
Sorry, something went wrong.
Could we just print path?
Dep hoisting makes the path unhelpful.
Yeah, this is going to get nasty.
If you'd like to send a PR, by all means do. But this isn't something I'm going to tackle.
No branches or pull requests
It'd be awesome if the report indicated whether a dep was top-level, or if not, which packages caused it to be included.
The text was updated successfully, but these errors were encountered: