From 66f48d92446d958be0e20c83e4adca3532415291 Mon Sep 17 00:00:00 2001 From: fanich37 Date: Mon, 10 Dec 2018 09:22:58 +0300 Subject: [PATCH] Update troubleshooting section at README.md --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index dab77f78..53ed842d 100644 --- a/README.md +++ b/README.md @@ -166,6 +166,15 @@ ng build --stats-json --build-optimizer=false --vendor-chunk=true ``` The resulting stats.json can be found at `dist/stats.json` +### I don't see `gzip` or `parsed` sizes, it only shows `stat` size + +It happens when `webpack-bundle-analyzer` analyzes files that don't actually exist in your file system, for example when you work with `webpack-dev-server` that keeps all the files in RAM. If you use `webpack-bundle-analyzer` as a plugin you won't get any errors, however if you run it via CLI you get the error message in terminal: +``` +Couldn't parse bundle asset "your_bundle_name.bundle.js". +Analyzer will use module sizes from stats file. +``` +To get more information about it you can read [issue #147](https://github.com/webpack-contrib/webpack-bundle-analyzer/issues/147). + *Please be aware, that this is not a reasonable build for production use, as it increases the build output size considerably.*

Maintainers