All modules are linted in watch mode after changing only a single file about eslint-webpack-plugin HOT 7 CLOSED

@WilkinWendy for this you can enable lintDirtyModulesOnly

I’ve tried it，but not work.

from eslint-webpack-plugin.

Solving it now. =)

from eslint-webpack-plugin.

My problem is a little different. In my project, there remains a lot of errors & warnings. I only want to lint what is saved by current user in his IDE.
Now, when the project starts, all files are linted..about 100+

from eslint-webpack-plugin.

@WilkinWendy for this you can enable lintDirtyModulesOnly

https://github.com/webpack-contrib/eslint-webpack-plugin#lintdirtymodulesonly

from eslint-webpack-plugin.

@WilkinWendy for this you can enable lintDirtyModulesOnly

I’ve tried it，but not work.

{ exclude: 'node_modules', extensions: ['.js', '.jsx', '.vue', '.ts', '.tsx'], quiet: true, cache: true, fix: true, lintDirtyModulesOnly: true, formatter: 'codeframe' }

from eslint-webpack-plugin.

@WilkinWendy for this you can enable lintDirtyModulesOnly

I’ve tried it，but not work.

In my project, the compilation seems to be triggered in a dead loop, when fix:true

from eslint-webpack-plugin.

@WilkinWendy for this you can enable lintDirtyModulesOnly

I’ve tried it，but not work.

In my project, the compilation seems to be triggered in a dead loop, when fix:true

I‘ve worked out reason of this problem.
If a file is unfixable,which means the output of the fixed file is the same as the source file,
eg: no-console rule is unfixable.
the outputFixes function will be executed in a dead loop.

from eslint-webpack-plugin.