Jason Miller

Hiya - this seems the same as the second issue mentioned in #7. Are you able to share your Webpack configuration - in particular the `mode`, `target` and `output` options?

Awesome, thanks for this. I will try to set up a test case. I likely missed some bundle parsing cases for multi-entry since I avoid using multi-entry whenever possible for...

@keepitterron it's a little buried in the docs, but there now: https://webpack.js.org/plugins/module-concatenation-plugin/#optimization-bailouts

For those hitting this issue, you can disable automatic modernization via `new OptimizePlugin({ modernize: false })`. This improves performance, but will use the unmodified ES5 source of most npm modules...

Hiya - try passing `modernize:false`: ```js webpack: config => { config.plugins.push(new OptimizePlugin({ modernize: false })); return config; }, ``` That should perhaps be the default, since it's very much a...

@mohsinulhaq what version of Webpack are you using?

Yes - I haven't tested it on Webpack 5+. I'm thinking the issue here is related to Webpack output options folks have configured - `output.target`, etc. If anyone can post...

@Super-Fly unfortunately that error message only tells me that webpack failed to complete successfully (the stack trace is just from `npm run`). Are you able to share the repository or...

@Super-Fly hmm - those numbers mean something is misconfigured. Are you running babel-loader or transpiling typescript? Need to remove babel-loader to use this.

Just an update: I have a fix for this in `babel-preset-modernize` that should be released soon. In the meantime, you can disable automatic modernization by passing `new OptimizePlugin({ modernize: false...