Ben Regenspan

Now that there's a context menu concept in place, maybe that could be a good place to trigger this sort of thing. (The current context menu only relates to the...

@TheLarkInn that sounds good to me! For the semi-related issue https://github.com/webpack-contrib/webpack-bundle-analyzer/issues/265 (but to do with displaying **chunk graph**, as opposed to **module graph** details) , I started down this path...

One other avenue for this that could make sense (and would limit the number of UI changes needed) is to add integration with https://github.com/webpack/analyse since it already offers the richer...

(I have a work-in-progress branch for this here: https://github.com/bregenspan/webpack-bundle-analyzer/tree/issue-265-filter-related-chunks, going to find time to test it against various project configurations and finish up documenting the chunk graph)

Did some more exploratory work for this in [this branch](https://github.com/webpack-contrib/webpack-bundle-analyzer/compare/master...bregenspan:issue-265-filter-related-chunks?expand=1).  But what I'm seeing is that the utility of being able to...

> Repro wise, i think we need a page with a slow HTML SRT but then plenty of fast SRT requests served from the same origin. https://cuzillion.com/ sadly can't add...

I think the way loading happens in bootstrap.js is the culprit. It relies on an asynchronous loading technique to inject both lab.js and init.js, and so it's possible for init.js...

The query trees gzip pretty well, but I agree it'd be very nice to get things further compressed to reduce parse time (in the project I'm working on, queries represent...