-
-
Notifications
You must be signed in to change notification settings - Fork 483
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
Analyzer getting parsing errors after upgrade to Webpack 5 for edge cases #409
Labels
Comments
So just wanted to share that the I am no longer seeing this error after I started using optimization: {
runtimeChunk: {
name: 'js/runtime'
},
splitChunks: {
cacheGroups: {
vendor: {
test: /[\\/]node_modules[\\/](jquery|foundation-sites|foundation-datepicker|intersection-observer)[\\/]/,
name: 'js/vendor',
chunks: 'all',
},
},
},
} I don't know if this issue should be closed based on this or whether bundle should work even if no special runtime file is created. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
I had been easily creating analyzer reports with my very old configuration of laravel-mix 2 (running webpack 2 underneath). Finally I have managed to upgrade our config to laravel mix 6 (running webpack 5). Webpack is correctly creating all my bundles and webpack-bundle-analyzer even creates a proper report for this configuration. But the anazlyer is also throwing the following errors:
Sadly I don't get any more errors that would give me a clue why bundle is failing.
I think my issue is similar to problems mentioned in #327
Technical info
Debug info
I am using it as a plugin and here is how I run it:
What other Webpack plugins were used?
I am not explicitly using any more plugins but laravel mix under the hood is using plugins for minification and versioning etc..
The stats file is attached below. Also no exception was thrown while creation of the stats file based on your recommended method (with analyzer disabled and source: false).
stats.json.zip
The text was updated successfully, but these errors were encountered: