Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Error parsing bundle asset "*" no such file when mixing relative paths#593

Unanswered
Solant asked this question inQ&A
Discussion options

Error parsing bundle asset "*" no such file when mixing relative paths

Looks like mixing paths for outputstats.json and webpack entries causes this error.

Technical info

  • Webpack Bundle Analyzer version: 3.0.2
  • Webpack version: 4.6.15
  • Node.js version: 10.11.0
  • npm/yarn version: 6.4.1
  • OS: Archlinux

Debug info

Bundle analyzer is launched as npm script:
webpack --profile --json > dist/stats.json && webpack-bundle-analyzer dist/stats.json

And webpack entries look like that:

    entry: {        'otherplace/bundle1': ['*', '*'],        'otherplace/bundle2': '*',        'otherplace/bundle3': '*',        'dist/bundle4': '.*',        'dist/bundle5': '.*',    },

So, when
webpack --profile --json > dist/stats.json && webpack-bundle-analyzer dist/stats.json
Errors like

Error parsing bundle asset "<absolute path>/dist/dist/bundle5.js": no such file (/dist/ appear twice)Error parsing bundle asset "<absolute path>/dist/otherplace/bundle2": no such file (should be no /dist/, only /otherplace/)

appear, and no parsed size (only stat size) available, but when using
webpack --profile --json > stats.json && webpack-bundle-analyzer stats.json
everything works fine

You must be logged in to vote

Replies: 18 comments

Comment options

th0r
Oct 12, 2018
Maintainer

What does* mean in the paths?

You must be logged in to vote
0 replies
Comment options

What does* mean in the paths?

I just replaced the actual paths in the project

You must be logged in to vote
0 replies
Comment options

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

You must be logged in to vote
0 replies
Comment options

th0r
Oct 12, 2018
Maintainer

I can create small demo project for this issue, if you want

Yes, it would help a lot.

You must be logged in to vote
0 replies
Comment options

@th0r:
https://github.com/Solant/bundle-analyzer-paths
npm run analyze:fine is intended behavior
npm run analyze:error shows described error

You must be logged in to vote
0 replies
Comment options

same issue here. local macos builds fine, and remote CI produces this error saying:

Child mini-css-extract-plugin node_modules/css-loader/index.js!node_modules/vue-loader/lib/loaders/stylePostLoader.js!node_modules/sass-loader/lib/loader.js!node_modules/vue-loader/lib/index.js??vue-loader-options!src/views/Video.page.vue?vue&type=style&index=0&id=01422a34&scoped=true&lang=css&:    Entrypoint mini-css-extract-plugin = *    [0] ./node_modules/css-loader!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/sass-loader/lib/loader.js!./node_modules/vue-loader/lib??vue-loader-options!./src/views/Video.page.vue?vue&type=style&index=0&id=01422a34&scoped=true&lang=css& 162 bytes {0} [built]        + 1 hidden moduleError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/vendors.cb3f9722098fcd2c8907.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/1.c26fe07aa377bd74cdf2.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/app.e5b23854adf630ec7091.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/3.902eabc18fbeb40958b0.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/4.e7e88988441cd90f96ea.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/5.706427295ce3457d8589.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/6.adf191adef5bc477f936.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/7.83db1aa0a0f4751e3f03.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/8.8dd0451db14c6295a8db.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/9.39df996a12dec23833f6.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/10.bdb90602a0cd2b799d62.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/11.7dd6ec8635d6f9a72611.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/12.fc237f1f81c92dc8330f.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/13.a377c93a2452a355bb3f.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/runtime.9b6506fc815dcb500655.js": no such file

webpack version not locked using"webpack": "^4.16.5",

You must be logged in to vote
0 replies
Comment options

the same problem with me.

it is normal when build on mac os, but linux makes errors.

this is my package version

    "webpack": "^4.38.0",    "webpack-bundle-analyzer": "^3.4.1",    "webpack-cli": "^3.3.6",
You must be logged in to vote
0 replies
Comment options

Same thing here, any thoughts?

You must be logged in to vote
0 replies
Comment options

A possible workaround to make it work, in case you have an output directory nameddist:

webpack--profile--json>stats.json&&webpack-bundle-analyzerstats.jsondist/
You must be logged in to vote
0 replies
Comment options

@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.

You must be logged in to vote
0 replies
Comment options

always happen in webpack5

You must be logged in to vote
0 replies
Comment options

@vnues Can you provide example of the problem?

You must be logged in to vote
0 replies
Comment options

@vnues Can you provide example of the problem?

hello,This is myproject, you can perform the following steps

git clone git@github.com:art-design-ui/noov.js.gitnpm inpm run dev

The following prompt will occur

image

You must be logged in to vote
0 replies
Comment options

Is there any way for us to remove the extra noise right now?

You must be logged in to vote
0 replies

This comment has been minimized.

Comment options

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.

You must be logged in to vote
0 replies
Comment options

same issue here. local macos builds fine, and remote CI produces this error saying:

Child mini-css-extract-plugin node_modules/css-loader/index.js!node_modules/vue-loader/lib/loaders/stylePostLoader.js!node_modules/sass-loader/lib/loader.js!node_modules/vue-loader/lib/index.js??vue-loader-options!src/views/Video.page.vue?vue&type=style&index=0&id=01422a34&scoped=true&lang=css&:    Entrypoint mini-css-extract-plugin = *    [0] ./node_modules/css-loader!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/sass-loader/lib/loader.js!./node_modules/vue-loader/lib??vue-loader-options!./src/views/Video.page.vue?vue&type=style&index=0&id=01422a34&scoped=true&lang=css& 162 bytes {0} [built]        + 1 hidden moduleError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/vendors.cb3f9722098fcd2c8907.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/1.c26fe07aa377bd74cdf2.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/app.e5b23854adf630ec7091.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/3.902eabc18fbeb40958b0.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/4.e7e88988441cd90f96ea.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/5.706427295ce3457d8589.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/6.adf191adef5bc477f936.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/7.83db1aa0a0f4751e3f03.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/8.8dd0451db14c6295a8db.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/9.39df996a12dec23833f6.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/10.bdb90602a0cd2b799d62.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/11.7dd6ec8635d6f9a72611.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/12.fc237f1f81c92dc8330f.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/13.a377c93a2452a355bb3f.js": no such fileError parsing bundle asset "/builds/xxxxxx/backend/resources/dist/assets/js/runtime.9b6506fc815dcb500655.js": no such file

webpack version not locked using"webpack": "^4.16.5",

I had the same problem, did you solve it?

You must be logged in to vote
0 replies
Comment options

i replace the packaging code,and it's run ok:
yarn install;
npm run build;

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
11 participants
@Solant@th0r@valscion@rodoabad@yellowmegaman@alexander-akait@raphaelsoul@light0x00@vnues@agtemail11Soft@pump4kin
Converted from issue

This discussion was converted from issue #214 on March 29, 2023 06:03.


[8]ページ先頭

©2009-2025 Movatter.jp