-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
Update to 2.1.0-beta.25 causes parseQuery should get a string as first argument #3060
Comments
Instead of |
Having hard times debugging this and still no luck.
my config:
I guess something with loader
and moved babel configuration to .babelrc webpack stopped to show errors with this loader and started to show up errors with next loader which has options section ( |
In your rule config try using It looks like you missed that change for your url-loader and your babel-loader |
Unfortunately i've tried more verbose syntax with
|
There is old loader-utils in webpack's package.json "loader-utils": "^0.2.11" |
Thanks @achicu I got the same problem and was trying to work it out as your message came through. That fixes it for me. |
@AlexChepura thanks, finally it works!) |
Update loader utils dependency to fix #3060
* master: (77 commits) remove-automatic-loader-extension: update examples fix-2986: Remove automatic -loader module name extension replaced calls to Object.assign with objectAssign to support node 0.12.x (webpack#3080) docs(example): update examples template (webpack#3074) Fix plugin typos in options validation feat(readme): add jsbeautify-loader to readme (webpack#3062) Update loader utils dependency to fix webpack#3060 add number for schema info 2.1.0-beta.25 fix test fixed Validation message fixed dll test cases fixed browsertest added a note about applying the LoaderOptionsPlugin only for some modules added another custom error message for the debug property Adds empty into schema for node (webpack#3034) Moving parsing of the `progress` flag to webpack specific bin 2.1.0-beta.24 beautify fixed max line length ...
Anything below 0.2.16 for loader-utils causes issues with webpack 2 (webpack/webpack#3060 (comment) and I have replicated the issue)
Anything below 0.2.16 for loader-utils causes issues with webpack 2 (webpack/webpack#3060 (comment) and I have replicated the issue)
I'm submitting a bug report
Webpack version:
2.x
Please tell us about your environment:
Windows 10
Current behavior:
I recently upgraded to webpack 2 beta 25 from beta 20. In beta 20, my entire configuration worked and the compilation worked. Upgrading to webpack 25 causes this error:
I'm running the compiler script using
babel-node
.ES6/7
The text was updated successfully, but these errors were encountered: