-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NormalModuleFactory.afterResolve is no longer a waterfall hook #248
Comments
Please create reproducible test repo |
I'm not sure if I'll be able to do that I'm afraid. The modules involved all appear to be internal to webpack, we're not using them directly. Our build is large/complex with many plugins/loaders and can't be pared down to a reproduction case. It only happens when using webpack-dev-middleware (3.7.2, which is compatible with webpack 5). I'm ok if you want to close this, I'll reopen if I find any lines of investigation, and I'll try the next RC when it's released. |
I think bug in plugin/loader, I can't help without configuration |
This is a breaking change in webpack 5, but the error message is not very helpful in finding the offending plugin. We should improve the error message. |
By a process of elimination I found that pmmmwh/react-refresh-webpack-plugin#27 was the issue, which has been fixed but yet to be released. Agree with keeping this issue to improve the error message, thanks |
When I tried Webpack 5 RC 0, I received the following error. It looks like this module may be the cause.
In particular, the returning here:
The text was updated successfully, but these errors were encountered: