-
Notifications
You must be signed in to change notification settings - Fork 121
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
Error: Rule can only have one resource source when using webpack-stream #233
Comments
It looks like others have fixed it by deleting their So maybe some kind of cached module the build doesn't like? |
Hi, Actually, many people in that thread recommend downgrading to webpack@v4 - that's not a solution, just a temporary workaround (which I am using atm). |
@marekdedic Ah ok, I'm not sure what the solution is then. I would try searching that error on https://github.com/webpack/webpack as the error originates from webpack directly. |
Ok, I submitted webpack/webpack#12640 - I am not sure where the issue lies, let's try and get to the bottom of this 🙂 |
Hi,
I've recently encountered this very weird error after updating from webpack v4 to v5.
However, calling webpack directly works just fine:
I've tried to clean up the repo and make it into a minimal repro, here it is: https://github.com/skaut/shared-drive-mover/tree/webpack-5-issue-repro
This issue only happens to me with webpack@v5, webpack-stream, vue and typescript. Removing any of these makes the issue disappear. I honestly don't know which package is the culprit but since there is a clear difference between using and not using this one, that'd be my most probable guess.
The text was updated successfully, but these errors were encountered: