Add logging of resulting webpack loader objects during invalid configuration object errors

Feature request

Is your feature request related to a problem? Please describe.

Webpack 5 is out and I was excited to try using it! I’ve pinned the dependency via the resolutions field in package.json, but - upon running next build - I’m met with a large callstack related to: “ValidationError: Invalid configuration object.”. The problem is that the Webpack config is defined as a result of many functions in next source code AND the amalgamation of many plugins (or not if one doesn’t use them.)

It would be helpful for both myself and plugin owners, if the specific loader in question (and it’s shape/appearance) was brought to the attention of developers when facing a webpack build validation error.

Describe the solution you’d like

If a webpack build validation error throws, the problematic loaders should be logged.

[ScriptedAlchemy]

Yeah it’s transpile modules. Use my copy till the author updates it. Mine is a little slower because I turn off caching on transpiled modules to make it work.

It’s not recommended ofc. But it works and would unblock you at the expense of slightly slower builds. Had the fork in production for about a month or two. I pushed a bunch of new fixed to it today as I’ve started updating all my apps to v5 stable

https://www.npmjs.com/%40module-federation%2Fnext-transpile-modules

I won’t be maintaining the fork once the main repo is updated. So keep an eye transpile-modules

Docs are outdated but it works on next 955 and v5 stable

[ScriptedAlchemy]

Haha sure. Just unblocking you 👍