webpack: Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin
Thank you for an awesome template. I have run into this error with Windows 10, node 7.5.0 and npm 4.1.2. This error is with the boilerplate code unmodified and running with NODE_ENV=production. There is no error with NODE_ENV=testing or development.
ERROR Failed to compile with 2 errors
error in ./src/App.vue
Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin, refer to https://github.com/webpack/extract-text-webpack-plugin for the usage example
at Object.module.exports.pitch (C:\iTurbineIO\Projects\vue-webpack\node_modules\extract-text-webpack-plugin\loader.js:27:9)
@ ./src/App.vue 3:0-335
@ ./src/main.js
@ multi ./build/dev-client ./src/main.js
error in ./src/components/Hello.vue
Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin, refer to https://github.com/webpack/extract-text-webpack-plugin for the usage example
at Object.module.exports.pitch (C:\iTurbineIO\Projects\vue-webpack\node_modules\extract-text-webpack-plugin\loader.js:27:9)
@ ./src/components/Hello.vue 3:0-345
@ ./src/router/index.js
@ ./src/main.js
@ multi ./build/dev-client ./src/main.js
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 3
- Comments: 16 (3 by maintainers)
I found out that
webpack.prod.conf
was not loaded whenNODE_ENV === 'production'
. I’ve solved it as followed indev-server.js
:Problem fixed for me too:
NODE_ENV=development
. I added it in ‘dev’ script (for windows):"dev": "cross-env NODE_ENV=development node build/dev-server.js"
NODE_ENV=development
fixed the problem for me too.I tried this template with no errors and NODE_ENV=development, testing and production: browserify Possible related issue: 537
I’m still experiencing this issue.
@Turqueso From command line
set NODE_ENV=development
and if you’re on windows you should take a look at your environment variables 😉This is still an issue and setting
NODE_ENV=development
is not a fix… It’s fundamental this template works setting the node environment to productionto replicate: