The same file is being linted multiple times during a compilation, causing very long build times about eslint-webpack-plugin HOT 5 CLOSED

Hi, recently I've been working a lot with this plugin, and I think I have a solution to this issue but I don't know what are your thoughts on this:

change the module retrieving hook:

to:

compilation.hooks.finishModules.tap(ESLINT_PLUGIN, processModules) // function processModules needs to be written

now we retrieve all modules at once, so we can filter them after striping resource query:

function processModules(modules) {
  const resources = modules.map((module) => module.resource.split('?')[0]);
  const resourcesUnique = new Set(resources);
  // TODO: process resourcesUnique
}

now when we are sure that every file if processed only once, we can remove all logic involving resultStorage:

as far as I understand it was created to filter the results:

from eslint-webpack-plugin.

Don't think we should keep cache for compiler, we have modules, i.e. we can use module as key for weak map

from eslint-webpack-plugin.

I'm not sure if I understand your point. My idea is to completely remove everything involving our cache (called resultStorage)

from eslint-webpack-plugin.

@watjurk When you change one file, it will invalidate whole cache, it is not effective

from eslint-webpack-plugin.

This plugin as it is right now (in my understanding) doesn't use resultStorage as cache, every time lint (in src/linter.js) is called every file from files is linted again no matters what crossRunResultStorage says

from eslint-webpack-plugin.