Skip to content
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

Webpack loader issue - DeprecationWarning: loaderUtils.parseQuery() #848

Closed
slavab89 opened this issue Mar 26, 2017 · 6 comments
Closed

Comments

@slavab89
Copy link
Member

When running the project i see the following warning:

(node:19056) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.

I've tried to add process.traceDeprecation = true to various places but for some reason it doesnt show which loader causes this issue.

Anyone knows how to fix this?

@ZeroCho
Copy link
Member

ZeroCho commented Mar 26, 2017

One of loaders must be using parseQuery instead of getOptions but I searched all loaders(postcss, babel, style, json, css, url, file) I could not find parseQuery. That's very weird.

@slavab89
Copy link
Member Author

If i search for ./parseQuery in all node_modules the almost all loaders have a require to this. But i'm not sure if this is it - cause its in all loaders

@slavab89
Copy link
Member Author

So, i've looked at this a bit further.
Seems to be happening on babel-loader plugin
It is fixed on version 7 that's on beta there.

So nothing much that we can do here other than wait =]

@GGAlanSmithee
Copy link
Member

That's been bugging me too, thanks for diggin @slavab89

@slavab89
Copy link
Member Author

So... getting back to this. Just after 2 days since i've close this issue. They've released version 7 of babel-loader.

I've updated to the latest version of all loaders and dont see this happen anymore

@zoruc
Copy link

zoruc commented May 11, 2017

@slavab89 I did the same thing and it fixed the issue thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants