Errors when using with the webpack dev server 4

Issue description

I got errors when using bundle analyzer wit the webpack dev server 4.

Error parsing bundle asset "d:\projects\devel\rankrocket\app\www\js\app.a49e5464.js": no such file
Error parsing bundle asset "d:\projects\devel\rankrocket\app\www\js\pdfmake.d2d0b128.js": no such file
Error parsing bundle asset "d:\projects\devel\rankrocket\app\www\js\vendors.aa8b04ed.js": no such file
Error parsing bundle asset "d:\projects\devel\rankrocket\app\www\js\private.18a4a042.js": no such file
Error parsing bundle asset "d:\projects\devel\rankrocket\app\www\js\public.6ce47ae2.js": no such file
Error parsing bundle asset "d:\projects\devel\rankrocket\app\www\js\node_modules_fortawesome_fontawesome-free_css_all_min_css.2124fe27.js": no such file
Webpack Bundle Analyzer is started at http://127.0.0.1:8888

This happens only, when running under dev server, regular build completes normally.

Technical info

System:
    OS: Windows 10 10.0.19043
    CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
    Memory: 5.88 GB / 15.78 GB
  Binaries:
    Node: 16.10.0 - d:\devel\node\node.exe
    npm: 7.20.2 - ~\.npm\npm.cmd

webpack: 5.55.1
webpack-dev-server: 4.3.0
webpack-bundle-analyzer: 4.4.2

Debug info

I am using it as plugin with the following options:

new BundleAnalyzerPlugin( {
        "analyzerMode": process.env.WEBPACK_DEV_SERVER ? "server" : "static",
        "analyzerPort": 8888,
        "openAnalyzer": false,
})

What other Webpack plugins were used?

html-webpack-plugin
copy-webpack-plugin
terser-webpack-plugin
case-sensitive-paths-webpack-plugin
mini-css-extract-plugin
css-minimizer-webpack-plugin

Please provide reproducible test repo

Here is the minimal project to repro this issue:
https://github.com/zdm/webpack-bundle-analyzer-issue-471

npm i
npx webpack-dev-server

See errors:

...
Error parsing bundle asset "d:\downloads\webpack-bundle-analyzer-issue-471\www\js\vendors.1989a8af.js": no such file
Error parsing bundle asset "d:\downloads\webpack-bundle-analyzer-issue-471\www\js\app.f747955a.js": no such file

...

You are on windows, but uses https://github.com/zdm/webpack-bundle-analyzer-issue-471/blob/main/webpack.config.js#L17 (i.e. /), please use path.resolve(__dirname, '/www')

I updated code to use path.resolve. Results are the same.

…

On 02.10.2021 19:06, Alexander Akait wrote: |path.resolve(__dirname, '/www')|

Under linux results are the same too.
The problem is not in the paths separators.

Yep, I see, investigating

@valscion

@valscion Found a bug, we should use compiler.outputFilesystem, not fs to be compatibility with dev server and not only (because other plugins can override fs)

You mean this code?

https://github.com/webpack-contrib/webpack-bundle-analyzer/blob/194c62da11b4858982c5e1c374ce04010e893d3d/src/parseUtils.js#L10-L11

@valscion

@valscion Yes 👍

Is it fixable?

It's likely that it's fixable. It would require adding more test coverage to make sure the fix would not regress in the future and we don't have much tests for webpack-dev-server integration yet so it's not a straightforward task.

That's why I haven't had time to fix this yet. Feel free to try to fix it and provide a PR if it would be important to you for this bug to be fixed ☺️

This can be problematic for me because I am not in the context of this project.
I can help in testing.
Will wait, no other way...

Is it possible to fix this?
Same problem with webpack 5.

@zdm

@zdm Yes, do you want to send a PR? I can point where to fix it

I can take a look.
Give me point in code, where this happens and some description.

@zdm

@zdm We should pass compiler.outputFileSystem to here - https://github.com/webpack-contrib/webpack-bundle-analyzer/blob/master/src/parseUtils.js#L9 and use it instead fs, starting from - https://github.com/webpack-contrib/webpack-bundle-analyzer/blob/master/src/BundleAnalyzerPlugin.js#L55, we have compiler in this scope

I'd like to work on this. The fix detects memfs used by webpack-dev-server 4 by checking the __vol property on outputFileSystem and returns null to prevent reading from disk. PR: #712

I tested. it works and PR can be merged. Thank you.

fix: read bundle assets via compiler.outputFileSystem

Navigation Menu

Repository navigation

Errors when using with the webpack dev server 4 #471

Issue description

Technical info

Debug info

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Errors when using with the webpack dev server 4 #471

Description

Issue description

Technical info

Debug info

Activity

alexander-akait commented on Oct 2, 2021

zdm commented on Oct 2, 2021

alexander-akait commented on Oct 2, 2021

zdm commented on Oct 2, 2021

zdm commented on Oct 2, 2021

alexander-akait commented on Oct 2, 2021

alexander-akait commented on Oct 2, 2021

valscion commented on Oct 4, 2021

alexander-akait commented on Oct 4, 2021

zdm commented on Oct 7, 2021

valscion commented on Oct 7, 2021

zdm commented on Oct 7, 2021

zdm commented on Apr 25, 2025

alexander-akait commented on Apr 25, 2025

zdm commented on Apr 25, 2025

alexander-akait commented on Apr 25, 2025

Br1an67 commented on Mar 9, 2026

zdm commented on Mar 9, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions