Closed bebraw closed 8 years ago
How should this be inferred from the config?
It cannot be inferred trivially. That's the problem. There would have to be something that's able to peek at webpack stat output.
Sounds like a tangential, new project, but not like webpack-validator, which only analyzes config, don't you think? It'd be interesting though, could be called "webpack-bundle-analyzer", analyzing result bundle by looking at stats.
Yup. A separate project would be fine. Just wanted to dump this somewhere. 👍
Related project btw, https://github.com/robertknight/webpack-bundle-size-analyzer .
I've used https://github.com/robertknight/webpack-bundle-size-analyzer in the past to analyze bundle size. Would this already be of help for the given problem?
Edit: ok you just posted it. :D
Yeah, I was just thinking it would make sense to discuss with that guy.
So we can probably close this here, right?
Yeah. Let's close this one.
This can bloat a bundle surprisingly so it would be good to at least warn against this. It's easy to end up in a situation where a dependency of a dependency brings some heavy Node part to your bundle.