Measure rule performance through VSCode ESLint

[christianvuerings]

Description:

ESLint Stats makes it possible to capture rule execution times after a lint run. This would be valuable in VSCode to identify slow rules and optimize configurations without running ESLint manually from the CLI.

Ideas

1. Enable via settings:

   "eslint.options": {
     "stats": true
   }

   How could we parse this data in the extension?

2. Override ESLint executable path to run a wrapper that sets --stats and --output-file, then parses the JSON before passing normal output back.

Questions

• Is there any API/hook in the extension to capture ESLint stats output after each run?
• Can we override the ESLint executable path for a custom wrapper?
• Any limitations in the extension/server protocol for sending this extra data?

Goal
Collect & log ESLint rule performance data directly in VSCode.