Yuriy Grunin

> Hello, thanks for an amazing tool. Thanks! > What do you think about this? > If this is something that sounds useful, I can try to improve this PoC...

Yep, idea is nice but unfortunately I don't have time to implement it. PR would be great.

@wood1986 may I kindly ask you to: 1. Fix PR review issues in a separate commits and don't use force-push as it's really difficult to track changes you've made 2....

Why can't you use either `-p` CLI flag or `analyzerPort` config option?

> But it won't be evaluated as JS unless you put it in backticks? This string is inserted in the generated code as-is - it should not be evaluated at...

@Theoton there is not enough information to solve your issue. Could you please create a reproducible example repo or I'll have to close this issue.

I think the reason is `webpack-stats.json` size is `1gb` and we're using something like `readFileSync` to read it as a string.

I think here are the problematic code: https://github.com/webpack-contrib/webpack-bundle-analyzer/blob/e5b617e44df299e7ad4f7dc1bb1cac41e204648c/src/analyzer.js#L164-L168 Maybe there is some package that parses JSON without reading it into a string first. @sokra maybe you've already solved such problem?

What do you want to see inside a CSS chunk?

Bad news: seems like webpack doesn't provide a symlinked path in stats info - it only contains already expanded path to the real file. I think the most proper way...