webpack-bundle-analyzer icon indicating copy to clipboard operation
webpack-bundle-analyzer copied to clipboard

Published 20 hours ago • verified publisher icon webpack-contrib

I don't see gzip or parsed sizes, it only shows stat size.

Open Theoton opened this issue 5 years ago • 3 comments

Issue description

I don't see gzip or parsed sizes, it only shows stat size.

image image image

webpack.config.js

node v11.15.0 webpack v5.0.0-beta.18

image

Theoton avatar Jun 18 '20 04:06 Theoton

Please create a reproducible project or follow the issue template

valscion avatar Jul 01 '20 11:07 valscion

This is exact thing happened to me as soon as I added something to a worker file that is also imported by my main thread. This alone enough enough to cause: Error parsing bundle asset for every one of the output assets, and

No bundles were parsed. Analyzer will show only original module sizes from stats file.

Then none of them can be analyzed via parsed or gzip. Removing this shared dependency from the worker resolves everything. I'm not sure what happens under the hood in worker-loader that causes this strange behavior. I've had issues in the past with having common modules referenced in workers.

I would expect the worker to simply bundle everything independent of the main bundle. With some shared stuff (TS enums) webpack compilation just hangs, but with other stuff it works fine. In this case I'm pulling in an error reporting SDK. Everything works except for profiling.

bfricka avatar Sep 22 '20 22:09 bfricka

@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.

th0r avatar Sep 28 '20 13:09 th0r