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
the second parameter of cleverMerge
could be undefined
#9424
Comments
How we can reproduce bug? |
This comment has been minimized.
This comment has been minimized.
Merged
The second argument is actually required. Unsure why it's omitted here by happypack. Anyway fix is on the way... |
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
releases as 4.36.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
bug, the second parameter of
cleverMerge
could be undefinedWhat is the current behavior?
In https://github.com/amireh/happypack/blob/master/lib/WebpackUtils.js#L137,
resolverFactory.get("loader")
miss the second parameter,and then cause the problem aboveIf the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
The text was updated successfully, but these errors were encountered: