Closed NasKadir123 closed 5 years ago
webpack-stream@5
upgraded to webpack@4
where they've made some config changes: https://webpack.js.org/migrate/4/#moduleloaders You might just need to rename loaders
to rules
.
If you can't upgrade to webpack@4
yet though, you can install whatever version of webpack your build is currently compatible with and feed that version of webpack as a compiler: https://github.com/shama/webpack-stream#usage-with-gulp-watch
webpack-stream@5
upgraded towebpack@4
where they've made some config changes: https://webpack.js.org/migrate/4/#moduleloaders You might just need to renameloaders
torules
.If you can't upgrade to
webpack@4
yet though, you can install whatever version of webpack your build is currently compatible with and feed that version of webpack as a compiler: https://github.com/shama/webpack-stream#usage-with-gulp-watch
Thanks!!! Sorry for late answer, it gets worked!
Hi! I have some problem with webpack-stream version 5.2.1. I'm using it with gulp and have this error: WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
NormalModuleFactory
). at webpack (/Applications/MAMP/htdocs/wordpress/wp-content/themes/modest_portfolio_theme/node_modules/webpack/lib/webpack.js:31:9) at Stream.I'm using babel-loader for ES6, vinyl-named and yargs. Error come in this task with scripts:
This code has worked in webpack-stream version 4.0.3. What should I do? Can you help me, please?