You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to request a feature or report a bug? Bug
What is the current behavior?
When upgrading to webpack 4 and with the node tracing turned on (process.traceDeprecation = true; in webpack.config.js), by running the webpack-dev-server --mode development, the following DeprecationWarning with stack trace is shown.
(node:32184) 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.
at Object.parseQuery (C:\app\node_modules\replace-loader\node_modules\loader-utils\index.js:78:3)
at Object.module.exports (C:\app\node_modules\replace-loader\index.js:7:27)
at LOADER_EXECUTION (C:\app\node_modules\loader-runner\lib\LoaderRunner.js:119:14)
at runSyncOrAsync (C:\app\node_modules\loader-runner\lib\LoaderRunner.js:120:4)
at iterateNormalLoaders (C:\app\node_modules\loader-runner\lib\LoaderRunner.js:229:2)
at iterateNormalLoaders (C:\app\node_modules\loader-runner\lib\LoaderRunner.js:218:10)
at C:\app\node_modules\loader-runner\lib\LoaderRunner.js:233:3
at Object.context.callback (C:\app\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
at Object.module.exports (C:\app\node_modules\eslint-loader\index.js:225:11)
at LOADER_EXECUTION (C:\app\node_modules\loader-runner\lib\LoaderRunner.js:119:14)
What is the expected behaviour?
I believe this is due to the loaderUtils.parseQuery() call:
Do you want to request a feature or report a bug? Bug
What is the current behavior?
When upgrading to webpack 4 and with the node tracing turned on (
process.traceDeprecation = true;
inwebpack.config.js
), by running thewebpack-dev-server --mode development
, the followingDeprecationWarning
with stack trace is shown.What is the expected behaviour?
I believe this is due to the loaderUtils.parseQuery() call:
replace-loader/index.js
Line 7 in af934cd
loaderUtils.getOptions()
as indicated on webpack/loader-utils#56 (comment) help remove the Deprecation Warning.Dependencies/Tool Lineup
The text was updated successfully, but these errors were encountered: