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
It would be very helpful to see the scope of unused dependencies, or maybe exclude certain scopes from the analysis. IMO, debloating is particularly useful for those scopes needed at runtime.
The text was updated successfully, but these errors were encountered:
Thanks, @henrikplate, we have added scope information of each dependency to the report.
We also added a parameter to the plugin that allows excluding dependencies with particular scopes from the Depclean analysis. This way, the users have the option of removing unused dependencies that are only needed at runtime, if they want to.
Great idea, thank you (again).
It would be very helpful to see the scope of unused dependencies, or maybe exclude certain scopes from the analysis. IMO, debloating is particularly useful for those scopes needed at runtime.
The text was updated successfully, but these errors were encountered: