Closed gpoitch closed 7 years ago
Thanks for the info, I haven't done much testing with Webpack 3. I'll look into it.
@gpoitch I believe these plugins are usually run in order, when you were using the ModuleConcatenationPlugin
was it before the CircularDependencyPlugin
?
I tested both before and after. I believe the issue is that this plugin runs on the 'done' plugin event, at which point the ModuleConcatenationPlugin has already did its thing (merged/hoisted dependencies).
It makes sense that some circular dependencies could actually be eliminated by what the ModuleConcatenationPlugin
does, but not all of them. I still saw some undefined
imports and no warning from this plugin.
@aackerman Here's a minimal reproduction: https://github.com/gpoitch/webpack-circ-dep-bug
@gpoitch thanks, I imagine this will help a lot in addressing this issue.
This should be fixed in version 4.1.0
👏 thanks!
When using the
webpack.optimize.ModuleConcatenationPlugin
introduced in webpack 3, it appears that this plugin in unable to detect a lot of circular dependencies.When removing ModuleConcatenationPlugin, it outputs more warnings.