Given eslint-loader configuration from 05-Splitting..., whenever webpack-dev-server tries to hot reload on code change and there are eslint errors in code it can't with the following in the browser console:
[WDS] App updated. Recompiling...
[WDS] Errors while compiling. Reload prevented.
// and then error logs
Webpack stumbles over these errors. I think it is better if errors (especially purely syntactic ones) are only reported. To enable that eslint-loader docs suggest turning errors to warnings with emitWarning: true option. That would make eslint-config into:
Given
eslint-loader
configuration from 05-Splitting..., whenever webpack-dev-server tries to hot reload on code change and there are eslint errors in code it can't with the following in the browser console:Webpack stumbles over these errors. I think it is better if errors (especially purely syntactic ones) are only reported. To enable that
eslint-loader
docs suggest turning errors to warnings withemitWarning: true
option. That would makeeslint-config
into:Would you consider changing it? Or do you think it is better to not reload on some errors?