Skip to content

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

@Solant

Description

@Solant

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

Looks like mixing paths for output stats.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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions