vue-loader: DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic

Hi all! I made a new webpack-simple project, and when running npm run build I get presented with the message in the title. Specifically:

404s will fallback to /index.html
webpack: wait until bundle finished: /dist/build.js
(node:568) 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.

This is visible when using performance: { hints: "warning" } in your webpack config.

Additionally, doing an npm run dev I get this warning text:

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (250 kB).
This can impact web performance.
Assets: 
  build.js (1.55 MB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (250 kB). This can impact web performance.
Entrypoints:
  main (1.55 MB)
      build.js


WARNING in webpack performance recommendations: 
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

What can be done about any of this two things? This is coming from a plain new vue init webpack-simple $myproject build, not something particularly involved and I’m not sure it is intentional

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 11
  • Comments: 19

Commits related to this issue

Most upvoted comments

set process.noDeprecation = true , the warning will be removed

where is the webpack config? how to set process.noDeprecation = true?

@connor11528 process.noDeprecation = true goes anwhere inside the webpack.config.js file. process is a global variable it seems.

Don’t do this though. This just suppresses deprecation warnings but doesn’t actually fix anything. Webpack should still load properly

you need update:dev-server .js var config = require(‘…/config’) if (!process.env.NODE_ENV) { process.env.NODE_ENV = JSON.parse(config.dev.env.NODE_ENV) !!! process.noDeprecation = true }

Why was this issue closed? I’m seeing this on 14.2.2 and it seems to be a valid issue.

Is this fixed to #671? I still have parseQuery() to use vuejs/vue-loader/loader.js#L440