-
-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
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
Feature Request: Nest modules by dependency graph instead of folder structure #30
Comments
But a module can be required by two different modules. How would you show that? |
@sirlancelot Thoughts? |
I think I'd like to see it in both places. Not sure what makes the most sense. I'll have to think about it more. Webpack's own Analyze tool is able to create a web but that may not work for the kind of visualization of this tool. Maybe if you have control of setting the node's color, the module color could be based on a hash of the path. That way the exact same modules would be the same color? |
@sirlancelot For example, every react component imports react. How do you want it to be shown in a flat treemap? |
It appears to be a common issue that the `webpack --json` output can include non-JSON content with certain plugins or loaders. Trying to extract the JSON output automatically from the mixed input is likely to be tricky, but we can at least provide a clearer diagnosis of the problem. Fixes webpack-contrib#13 Fixes webpack-contrib#19 Fixes webpack-contrib#21 Fixes webpack-contrib#30
This is a great tool! I really enjoy visualizations of my work. I think it would be neat if the treemap's nodes were only modules instead of following the folder structure. It might make the map more useful and you can already see the path when you mouseover the node.
The text was updated successfully, but these errors were encountered: