Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork503
-
Error parsing bundle asset "*" no such file when mixing relative pathsLooks like mixing paths for output Technical info
Debug infoBundle analyzer is launched as npm script: And webpack entries look like that: So, when appear, and no parsed size (only stat size) available, but when using |
BetaWas this translation helpful?Give feedback.
All reactions
👍 7
Replies: 18 comments
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
What does |
BetaWas this translation helpful?Give feedback.
All reactions
-
I just replaced the actual paths in the project |
BetaWas this translation helpful?Give feedback.
All reactions
-
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 |
BetaWas this translation helpful?Give feedback.
All reactions
-
Yes, it would help a lot. |
BetaWas this translation helpful?Give feedback.
All reactions
-
@th0r: |
BetaWas this translation helpful?Give feedback.
All reactions
-
same issue here. local macos builds fine, and remote CI produces this error saying: webpack version not locked using |
BetaWas this translation helpful?Give feedback.
All reactions
👍 6
-
the same problem with me. it is normal when build on mac os, but linux makes errors. this is my package version |
BetaWas this translation helpful?Give feedback.
All reactions
-
Same thing here, any thoughts? |
BetaWas this translation helpful?Give feedback.
All reactions
-
A possible workaround to make it work, in case you have an output directory named webpack--profile--json>stats.json&&webpack-bundle-analyzerstats.jsondist/ |
BetaWas this translation helpful?Give feedback.
All reactions
👍 14
-
@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. |
BetaWas this translation helpful?Give feedback.
All reactions
-
always happen in webpack5 |
BetaWas this translation helpful?Give feedback.
All reactions
👍 20
-
@vnues Can you provide example of the problem? |
BetaWas this translation helpful?Give feedback.
All reactions
👀 4
-
hello,This is myproject, you can perform the following steps git clone git@github.com:art-design-ui/noov.js.gitnpm inpm run dev
|
BetaWas this translation helpful?Give feedback.
All reactions
👍 8
-
Is there any way for us to remove the extra noise right now? |
BetaWas this translation helpful?Give feedback.
All reactions
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. |
BetaWas this translation helpful?Give feedback.
All reactions
-
I had the same problem, did you solve it? |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
i replace the packaging code,and it's run ok: |
BetaWas this translation helpful?Give feedback.
All reactions
This discussion was converted from issue #214 on March 29, 2023 06:03.
