You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When looking at the buildHealth report, there are a number of unused dependencies that can be removed, and a number of transitive dependencies that are suggested to add directly. For many of our internal libraries that are relatively lightweight, the transitive dependencies are okay to be included in a transparent way, if it means we add a single internal library instead of 15 other dependencies.
Describe the solution you'd like
For each suggested unused dependency to remove, I would like it to include a count of how many transitives from that dependency are used. If the count is zero, then that dependency can be removed no questions asked. If it's 10+, we'd probably just leave it for conciseness of the build file.
Describe alternatives you've considered
I think I saw an issue asking for the "reason" report to include all dependencies in one go - this would also be useful. Running the reason on every dependency one at a time isn't really practical for us.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When looking at the
buildHealth
report, there are a number of unused dependencies that can be removed, and a number of transitive dependencies that are suggested to add directly. For many of our internal libraries that are relatively lightweight, the transitive dependencies are okay to be included in a transparent way, if it means we add a single internal library instead of 15 other dependencies.Describe the solution you'd like
For each suggested unused dependency to remove, I would like it to include a count of how many transitives from that dependency are used. If the count is zero, then that dependency can be removed no questions asked. If it's 10+, we'd probably just leave it for conciseness of the build file.
Describe alternatives you've considered
I think I saw an issue asking for the "reason" report to include all dependencies in one go - this would also be useful. Running the reason on every dependency one at a time isn't really practical for us.
The text was updated successfully, but these errors were encountered: