Overview

We're going to want performance comparisons against both ourselves (Flint) and other linters. It's hard to make claims about your own performance characteristics without public, reproducible tests against

I'd like to suggest we matrix something like:

• Linted files size: a dozen, a few hundred, a thousand, a few thousand, tens of thousands
• Linting rules: just one, ESLint's JS recommended, TSESLint's recommended, TSESLint's recommended type checked, TSESLint's strict & stylistic type checked, an equivalent of create-typescript-app's large config, the large set Flint uses for itself

For each of those, the project generator should be able to spin up a codebase with that config, then use something like https://github.com/sharkdp/hyperfine to test them.

Additional Info

https://github.com/typescript-eslint/performance is a step in this direction I've previously done.

❤️‍🔥