Feature request

Logging this issue as per @evilebottnawi's request here

A plugin that can identify circular dependencies in modules, similar to aackerman/circular-dependency-plugin, would work well in core Webpack.

What is the expected behavior?

Either enabled by default for mode: development, or registered by the user manually in the plugins array.

What is motivation or use case for adding/changing the behavior?

We've recently upgraded to Webpack 4, set mode: production, and modules: false in Babel, and we've been pleasantly surprised by ModuleConcatenationPlugin and the tree-shaking features. However, we've had a few instances where circular dependencies would break at runtime, and this plugin helped us quicky identify where these were.

How should this be implemented in your opinion?

as webpack.CircularDependenciesPlugin with the ability to include/exclude module patterns, as some circular dependencies are not avoidable.

Are you willing to work on this yourself?

I can help test it, but I don't have enough experience with the Webpack codebase.