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
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
This tool would be very useful to visualize JavaScript dependencies.
Webpack has built-in tools that can do this to some degree (See "Webpack Analyzer" at this article), but the resulting visualization is not pleasant to use as the amount of code grows. Some issues in webpack's analyzer include - too many nodes & lines; "filtering down" could be somewhat better (filtered-out nodes remain in graph, but less opaque); performance suffers due to it being an interactive force-directed graph with very many elements that is implemented with JS & canvas, etc.
The shortest/simplest path to having SourceTrail be able to show JS dependencies - I think - might be to create a script (a "binding" ?) that simply imports the "webpack-stats.json", converts to data format/structure needed internally for SourceTrail, and then allows to visualize.
After making issue, realized an existing issue #2 exists for TypeScript support. As well as in other repo - CoatiSoftware/Sourcetrail#294. If there's more progress with that/those approaches, might be worth closing this topic.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This tool would be very useful to visualize JavaScript dependencies.
Webpack has built-in tools that can do this to some degree (See "Webpack Analyzer" at this article), but the resulting visualization is not pleasant to use as the amount of code grows. Some issues in webpack's analyzer include - too many nodes & lines; "filtering down" could be somewhat better (filtered-out nodes remain in graph, but less opaque); performance suffers due to it being an interactive force-directed graph with very many elements that is implemented with JS & canvas, etc.
The shortest/simplest path to having SourceTrail be able to show JS dependencies - I think - might be to create a script (a "binding" ?) that simply imports the "webpack-stats.json", converts to data format/structure needed internally for SourceTrail, and then allows to visualize.
After making issue, realized an existing issue #2 exists for TypeScript support. As well as in other repo - CoatiSoftware/Sourcetrail#294. If there's more progress with that/those approaches, might be worth closing this topic.
The text was updated successfully, but these errors were encountered: