Before You File a Documentation Request Please Confirm You Have Done The Following...

• I have looked for existing open or closed documentation requests that match my proposal.
• I have read the FAQ and my problem is not listed.

Suggested Changes

ESLint allows you to profile your lint run with the TIMING=1 env var ¹. Alternately it provides the --stats flag to do a similar thing in a JSON form ².

These flags are great debug tools for non-type-aware rules. But they're mostly useless for type-aware rules because types are computed lazily and cached. This means that the first type-aware rule that runs will bear the brunt of doing the "pre-cached" calculations and then folllowing rules mostly just read from the caches and do little work in comparison.

This can actually paint a misleading and harmful picture because people will read the times and think a particular rule is much slower than it is in reality and sometimes people will turn off a rule thinking it was the cause of slowness.

We should have an FAQ section about this so we can help inform people to not trust the output for type-aware rules.

Affected URL(s)

Faq