-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Module build failed after update to 2.0.1 #348
Comments
Hello. Thanks for report. I guess this is a mistake, if you're using webpack v5, this should not happen. I just updated the release note to point this out. If you still need webpack v4 or lower, pls use 1.x of this plugin. Thanks. If you are using webpack v5 and this issue happens, pls let me know. We can continue on this topic. |
That makes sense. I cannot go into webpack upgrade at the moment, so I'll stay on the old version. Thanks for clearing it up! |
Welcome. |
Hi,
I am getting the below error on 2.0.1, but not on 2.0.0.
I could be totally wrong, but looking at the source and what changed, I would guess that
loader-utils
should not have been removed like they were in 59ae702. The v3 way of callinggetOptions()
makes it seem like we don't need the dependency but I guess we do.Downgrading fixes it for me, but I thought it was worth pointing out anyway.
The text was updated successfully, but these errors were encountered: