DeprecationWarning: loaderUtils.parseQuery()
See original GitHub issueI just added the configuration to webpack, it is working fine but I always get this warning:
...s/svg-sprite-loader/lib/web/sprite.js(node:36437) 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.
Hash: ffb4fa842d0159348c88
Version: webpack 2.2.1
Time: 3725ms
Am I doing something wrong or does svg-sprite-loader
need to be updated to use getOptions()
?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:6 (3 by maintainers)
Top Results From Across the Web
loaderUtils.parseQuery() received a non-string value which ...
DeprecationWarning : loaderUtils.parseQuery() received a non-string value which can be problematic laravel-mix/laravel-mix#456.
Read more >How to resolve the Webpack 2 loaderUtils.parseQuery ...
loaderUtils.parseQuery() is used by loaders to get the options that are passed to the loader. It has been replaced with loaderUtils.
Read more >How I fixed Webpack 4 `loaderUtils.parseQuery() received a ...
How I fixed Webpack 4 `loaderUtils.parseQuery() received a non-string value which can be problematic` error… DeprecationWarning: loaderUtils.
Read more >Node deprecationWarning - Get Help - Vue Forum
parseQuery() will be replaced with getOptions() in the next major version of loader-utils. I read the issue but i still be confused. I...
Read more >Why doesn't my custom theme seem to be applied?
ok -- Template Parsing Finished. (node:2072) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@herrbischoff @jeremyzahner Should be fixed in upcoming 2.0 version. Please read about it here #91 and take part in discussion/voting.
Thank you! I will definitely try the new version next chance I get.