Webpack 5: lintDirtyModulesOnly fails because getDirtyFiles returns lots of non-existent files about eslint-webpack-plugin HOT 9 CLOSED

@ricardogobbosouza, it's the globs. Since the my files option didn't contain glob paths, processModule isn't matching them. That's a breaking change, I think.
Also, in the previous version, running watch with lintDirtyModulesOnly would only run the linter after files were changed. Now it lints the whole graph on the first run -- that makes the initial build MUCH slower, killing much of lintDirtyModulesOnly's value.

from eslint-webpack-plugin.

Hi @jrnail23
Resolved v2.3.0
If the problem persists, reopen this

from eslint-webpack-plugin.

@ricardogobbosouza, I just tried v2.2.0, and it doesn't seem to be raising eslint warnings at all when using lintDirtyModulesOnly in watch mode.

I'm using the same config as above:

new ESLintWebpackPlugin({
  files: ['src/client', 'src/shared'],
  extensions: ['js', 'jsx'],
  cache: true,
  lintDirtyModulesOnly: true,
}),

from eslint-webpack-plugin.

I have same problem on windows with [email protected]

from eslint-webpack-plugin.

Hi @jrnail23
Try v2.2.0

from eslint-webpack-plugin.

@ricardogobbosouza trying it now. Thanks for the heads up. I'll let you know what happens.

from eslint-webpack-plugin.

@ricardogobbosouza, to be clear, that's a bad thing. It's not outputting eslint errors or warnings when I add them to a file in watch mode.

from eslint-webpack-plugin.

@jrnail23
If you can share the repository it would be of great help

from eslint-webpack-plugin.

@jrnail23 Remembering that only files imported on the graph will be linted, at least it is the expected behavior.

Ex:
src/index.js

import('./lint')

src/lint.js

// this file will linted
const foo = 'bar'

src/no-lint.js

// this file will not linted, why not being used

webpack.config.js

const ESLintPlugin = require('eslint-webpack-plugin');

module.exports = {
  plugins: [new ESLintPlugin({lintDirtyModulesOnly: true})],
};

from eslint-webpack-plugin.