0👍
I had the same problem with running npm run dev
from CMD on Win7.
I dont know, as I did not require this plugin anywhere explicitly and when I started this error did not occure to me.
As i also started to get this error and I already tried setting NODE_ENV=development
provided by this issue report from the official repo, I tried playing around.
Finally i ended up editing the webpack.dev.conf.js
adding this specific plugin to the plugins key as follows:
// File header with other Imports
var utils = require('./utils')
// ...
var ExtractTextPlugin = require('extract-text-webpack-plugin')
// Then in Module definition
module.exports = merge(baseWebpackConfig, {
// ... other keys for module
plugins: [
// .. other plugins
// .. I copied this line from the webpack.prod.conf.js
new ExtractTextPlugin({
filename: utils.assetsPath('css/[name].[contenthash].css')
}),
Well there might be better and more beautiful solutions.
This is just the one that seems to fix it for me.
As I am new to VueJs and I am only using the dev server at the moment with autoreload, other answeres might be bit more polished.
- [Vuejs]-How to correctly make API calls inside store.js using Vuex to update data?
- [Vuejs]-Using independent Vue project within another as node package
Source:stackexchange.com