Replies: 18 comments
|
What does |
I just replaced the actual paths in the project |
|
Probably there is something with joining paths from here: https://github.com/webpack-contrib/webpack-bundle-analyzer/blob/master/src/analyzer.js#L50 I can create small demo project for this issue, if you want |
Yes, it would help a lot. |
|
@th0r: |
|
same issue here. local macos builds fine, and remote CI produces this error saying: webpack version not locked using |
|
the same problem with me. it is normal when build on mac os, but linux makes errors. this is my package version |
|
Same thing here, any thoughts? |
|
A possible workaround to make it work, in case you have an output directory named webpack --profile --json > stats.json && webpack-bundle-analyzer stats.json dist/ |
|
@Solant thank you! But didn't help. In the end we've resolved it by adding second build, since it's always building OK on the second time in CI. First build is allowed to fail. |
|
always happen in webpack5 |
|
@vnues Can you provide example of the problem? |
|
Is there any way for us to remove the extra noise right now? |
This comment has been minimized.
This comment has been minimized.
|
Looks like @agtemail11Soft your build is broken as webpack says it has errors. This is likely not an issue with webpack-bundle-analyzer and is not the same thing as what the first message in this issue is about. |
I had the same problem, did you solve it? |
|
i replace the packaging code,and it's run ok: |

Uh oh!
There was an error while loading. Please reload this page.
Error parsing bundle asset "*" no such file when mixing relative paths
Looks like mixing paths for output
stats.jsonand webpack entries causes this error.Technical info
Debug info
Bundle analyzer is launched as npm script:
webpack --profile --json > dist/stats.json && webpack-bundle-analyzer dist/stats.jsonAnd webpack entries look like that:
So, when
webpack --profile --json > dist/stats.json && webpack-bundle-analyzer dist/stats.jsonErrors like
appear, and no parsed size (only stat size) available, but when using
webpack --profile --json > stats.json && webpack-bundle-analyzer stats.jsoneverything works fine
All reactions