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
Gulp is watching the src directory and should run the build task without any errors.
What is actually happening?
Webpack errors on every build after the first with:
WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration has an unknown property '__vueOptions__'.
......
It seems that vue-loader mutates the webpack config object here:
// /lib/loader.js line 52varoptions=this.options.__vueOptions__=Object.assign({},this.options.vue,this.vue,query)
This introduces an option that webpack doesn't allow.
It isn't an issue if you are running webpack from the command line, but when you are using the API, the config object gets re-used for each call, giving the error.
Cloning your config object before you pass it to webpack avoids any of these problems:
webpack(config,callback)// badwebpack(Object.assign({},config),callback)// good
The text was updated successfully, but these errors were encountered:
Version
12.1.0
Reproduction link
https://github.com/arichardsmith/vue-loader-bug-report
Steps to reproduce
gulp dev
What is expected?
Gulp is watching the src directory and should run the build task without any errors.
What is actually happening?
Webpack errors on every build after the first with:
It seems that vue-loader mutates the webpack config object here:
This introduces an option that webpack doesn't allow.
It isn't an issue if you are running webpack from the command line, but when you are using the API, the config object gets re-used for each call, giving the error.
Cloning your config object before you pass it to webpack avoids any of these problems:
The text was updated successfully, but these errors were encountered: