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
{{ message }}
This repository has been archived by the owner on Jul 27, 2021. It is now read-only.
When your webpack config is invalid, it won't output to the console because quiet is true, but the plugin has not been 'applied'.
Error with quiet set to to false:
$ cross-env NODE_ENV=development webpack-dev-server --inline --progress --config build-tools/config/webpack/webpack.dev.conf.js
✖ 「wds」: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration.output.filename: A relative path is expected. However the provided value "/asset/[name].js" is an absolute path!
-> Specifies the name of each output file on disk. You must **not** specify an absolute path here! The `output.path` option determines the location on disk the files are written to, filename is used solely for naming the individual files.
Please use output.path to specify absolute path and output.filename for the file name.
error Command failed with exit code 1.
Adding a log in the constructor and in the apply(compiler) { methods, only the constructor is executed.
So it seems there is a 'gap' before the plugin kicks in, where errors could happen, but don't get outputted because quiet needs to be set to true for this plugin to 'work'.
I'm not sure if there is a way to fix this, otherwise it would be good to clearly mention it in the readme/docs; when webpack exits without an error, temporarily disable the quiet mode.
The text was updated successfully, but these errors were encountered:
I believe this will be fixed with #66 as that change will watch on the "failed" hook. This means webpack failures will be caught in addition to the compilation errors.
When your webpack config is invalid, it won't output to the console because
quiet
is true, but the plugin has not been 'applied'.Error with
quiet
set to to false:Error with
quiet
set to true:Adding a log in the
constructor
and in theapply(compiler) {
methods, only the constructor is executed.So it seems there is a 'gap' before the plugin kicks in, where errors could happen, but don't get outputted because
quiet
needs to be set to true for this plugin to 'work'.I'm not sure if there is a way to fix this, otherwise it would be good to clearly mention it in the readme/docs; when webpack exits without an error, temporarily disable the quiet mode.
The text was updated successfully, but these errors were encountered: