From c93fd2b2cad2bb5d46a48a905d21ca9395d4ab7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C9=B9=C7=9D=CA=9E=C9=B9=C9=90=D4=80=20u=C7=9D=CA=8CS?= Date: Mon, 4 Oct 2021 10:19:22 +0200 Subject: [PATCH] Fix README.md (#473) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e522ad75..ebd37218 100644 --- a/README.md +++ b/README.md @@ -173,8 +173,8 @@ The Chunk Context Menu can be opened by right-clicking or `Ctrl`-clicking on a s 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. +Error parsing bundle asset "your_bundle_name.bundle.js": no such file +No bundles were parsed. Analyzer will show only original 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).