-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Config dependency manager doesn't take into account all the hooks until "initialize". #1768
Comments
@jantimon you can move |
@jantimon Friendly ping |
Ref: #1722 (comment) - need add a test case for this use case |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
What is the current behavior?
I use configuration dependencies to make sure that the plugins from the second config
'server'
will always be executed after the first config'client'
output is emitted:Doesn't work in the right order for the hooks like
afterResolvers
(orinitialize
), as seen in the console output:However, this works as expected starting from the
beforeRun
hook:What is the expected behavior?
Other relevant information:
webpack version: 5.74.0
Node.js version: 16.17.0
Operating System: Windows 10
This issue was moved from webpack/webpack#16312 by @alexander-akait. Original issue was by @reves.
The text was updated successfully, but these errors were encountered: