Bryan Mishkin
Bryan Mishkin
Relatedly, I've had some success speeding up ESLint in a large codebase by running it on several large directories separately and in parallel instead of just running `eslint .` on...
@kaicataldo sure, I will work on putting an RFC together. Using the `invalid` array sounds good. In the interest of keeping this lightweight and leaving out irrelevant properties, what do...
Reopening this as something I may try to write an RFC for at some point.
I have opened an RFC for this: - https://github.com/eslint/rfcs/pull/103
I believe this is still ready for review. It's one of several breaking changes I'm trying to have lined up ready to go when ESLint v9 comes around.
This PR is ready, except there is a failure with one rule we need to fix, see: * https://github.com/eslint/eslint/pull/17661/files#r1413158284 * https://github.com/eslint/eslint/pull/17812
@nzakas done!
Another related issue is https://github.com/eslint/eslint/issues/14597#issuecomment-1003863524 where I was imagining a way to output various rule metrics (violations, disable directives, performance stats, etc). So perhaps any solution should be more general...
Since it's not a breaking change, either before or after could work. But note that we have a lot of breaking change PRs for ESLint v9 open right now which...
That's fair. Perhaps re-target the PR to the main ESLint repo to start getting reviewers so that it will be lined up for then?