Webpack dev server needs a restart after an ESLint error occurs

[ePaLy]

When failOnError is set to true (it is by default) and an ESLint error occurs, the following error is printed to webpack dev server console:

No other output is printed to the console after that (after code modifications, etc.)

I think it is related to the fix in version 5.0.1: https://github.com/webpack-contrib/eslint-webpack-plugin/releases/tag/v5.0.1

Is it an expected behavior when failOnError is set to true?
Should it be documented?
Is it possible to set it defaultly to false based on environment?

[alexander-akait]

Sorry, no, the problem is not related to webpack-dev-server, if you set failOnError: true, it means webpack will stop bundling, it is a critical error, you should not use this for serve command

[alexander-akait]

4ef97cd#diff-bfe9874d239014961b1ae4e89875a6155667db834a410aaaa2ebe3cf89820556R175

It means hook returns an error and webpack stops doing anything

[ePaLy]

OK, thanks.
It would be nice if failOnError: process.env.NODE_ENV !== 'development' were set by default, so that eslint-webpack-plugin works smoothly with webpack-dev-server out of the box for the many users who use the process.env.NODE_ENV variable.

[alexander-akait]

@ePaLy You can create an issue in eslint-webpack-plugin, we have mode, that is the same as process.env.NODE_ENV, so it is easy to fix

[stefpb]

You can fix that with this line:

  // webpack.config.base.js
  plugins: {
  // …
    new ESLintPlugin({
      // …
      failOnError:  process.env.NODE_ENV === 'production'
      // …
    }),