Webpack stopped working after upgrading to 4.10.1 "RuntimeTemplate.moduleId(): Module ... has no id. This should not happen."

[finom]

Bug report

What is the current behavior?

WP throws on build:

ERROR in chunk main [entry]
assets/[name].js
/Users/finom/Work/djavan-front-end/open-source/import-glob-webpack-loader/index.js!/Users/finom/Work/djavan-front-end/node_modules/babel-loader/lib/index.js!/Users/finom/Work/djavan-front-end/src/components/entities/ClientForm/FocalsArray/FocalForm.js
RuntimeTemplate.moduleId(): Module /Users/finom/Work/djavan-front-end/open-source/import-glob-webpack-loader/index.js!/Users/finom/Work/djavan-front-end/node_modules/redux-form/es/reduxForm.js has no id. This should not happen.

If the current behavior is a bug, please provide the steps to reproduce.

Don't know how to reproduce yet. The temporary fix was to downgrade back to 4.9.1. Config is split into many small files don't know would that be useful to paste them all there. Let me know if it is.

What is the expected behavior?

It should build without the error.

Other relevant information:
webpack version: 4.10.1
Node.js version: 10
Operating System: MacOS
Additional tools: Babel, React and stuff

[alexander-akait]

/cc @ooflorent @sokra looks we fixed this #7428, regression?

[christiango]

Can confirm that I'm also seeing this issue on one of my webpack configs. Also had to revert back to 4.9.1. It is happening in the only webpack config in the repo that leverages dynamic imports for code splitting. We have 3 other webpack configs that do not repro this issue

[jeremy-clearlabs]

Appears to be related to #7425.