Skip to content
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

Closed
sirlancelot opened this issue Nov 30, 2016 · 4 comments

Comments

@sirlancelot
Copy link

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.

@th0r
Copy link
Collaborator

th0r commented Nov 30, 2016

But a module can be required by two different modules. How would you show that?

@th0r
Copy link
Collaborator

th0r commented Dec 1, 2016

@sirlancelot Thoughts?

@sirlancelot
Copy link
Author

sirlancelot commented Dec 1, 2016

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?

@th0r
Copy link
Collaborator

th0r commented Dec 2, 2016

@sirlancelot For example, every react component imports react. How do you want it to be shown in a flat treemap?
What I'm trying to say is treemap is not suitable for many-to-many relationships like this.

@th0r th0r closed this as completed Dec 7, 2016
eirikurn pushed a commit to aranja/webpack-bundle-analyzer that referenced this issue Feb 7, 2017
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants