ModuleConcatenationPlugin produces a bundle with mixin name collisions #11840
Labels
Comments
sokra
added a commit
that referenced
this issue
Nov 2, 2020
sokra
added a commit
that referenced
this issue
Nov 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
What is the current behavior?
When building JS application with mixins I get exception because of mixin name collision.
If the current behavior is a bug, please provide the steps to reproduce.
To reproduce please refer to this repository which contains simple and complete test case: https://github.com/bmblb/ModuleConcatenationPluginNameCollision
Just checkout repo, install packages, run
npm run serveand check out app page (see README.md)What is the expected behavior?
I expect no naming collision to occur, probably plugin could use unique generated name. I found a similar issue, but problem is still reproducible with latest version on webpack: #11743
As a workaround I had to disable plugin in production config, but docs suggest performance will suffer, so it would be great to get this fixed.
Cheers.
Other relevant information:
webpack version: 5.3.0
Node.js version: 12.19.0
Operating System: Windows 10 2004
Additional tools:
The text was updated successfully, but these errors were encountered: