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
I was trying to analyse my project dependency for reusing code in another project which is nearly the same. But found the are over 500 modules, with only 230 of them are belonging to my project. So I think if I can hide modules just by filtering or shortcut, that would be much more helpful.
By now my only solution is for read asset.json as object and filter them by hand and save it again.
The text was updated successfully, but these errors were encountered:
Agreed. Hiding deps (accounting size to the parent) and sorting by size are critical. Drawing a hairball is not useful. Listing hundreds of deps un-ordered is not useful.
I was trying to analyse my project dependency for reusing code in another project which is nearly the same. But found the are over 500 modules, with only 230 of them are belonging to my project. So I think if I can hide modules just by filtering or shortcut, that would be much more helpful.
By now my only solution is for read
asset.json
as object and filter them by hand and save it again.The text was updated successfully, but these errors were encountered: