Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webpack.NamedChunksPlugin breaks parsing #67

Closed
hjeti opened this issue May 2, 2017 · 4 comments · Fixed by #68
Closed

webpack.NamedChunksPlugin breaks parsing #67

hjeti opened this issue May 2, 2017 · 4 comments · Fixed by #68

Comments

@hjeti
Copy link

hjeti commented May 2, 2017

When using the webpack.NamedChunksPlugin the bundle can't be parsed anymore by the analyzer.

Couldn't parse bundle asset "dist\version\1493729489528\js\app.js".

If I disable the plugin everything works like a charm.

Attached a bundle that can't be parsed.
app.txt

@valscion
Copy link
Member

valscion commented May 2, 2017

Hmm interesting. Would you be able to provide a stats.json as well, @hjeti ?

@valscion
Copy link
Member

valscion commented May 2, 2017

Instructions for generating a stats.json were in the issue template:

It would be nice to also attach webpack stats file.
It can be generated using these options:

new BundleAnalyzerPlugin({
  analyzerMode: 'disabled',
  generateStatsFile: true,
  // Excludes module sources from stats file so there won't be any sensitive data
  statsOptions: { source: false }
})`

stats.json will be created in Webpack bundle output directory.

Zip the contents of your bundle directory and upload them here so we have all the pieces necessary for debugging this :)

@hjeti
Copy link
Author

hjeti commented May 2, 2017

I couldn't upload a zip (We don't support that file type.) so I have uploaded it to wetransfer.

https://wetransfer.com/downloads/36dc814a5d80c97a77c112ba0ad07b6020170502131503/e0aa2fde1c0ba9e6ce2b20cb14a16b7120170502131503/2dc762

@chrisui
Copy link

chrisui commented Jun 23, 2017

@valscion FYI I'm still seeing this issue after updating to 2.4.1

Couldn't parse bundle asset "~/build/vendor.1fb1fe7bbfafd8be0b4b.js".

Following up with a dump (it's a big build)...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants