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

I just posted an answer to a StackOverflow question: Typescript ESlint conflict between no-inferrable-types and typedef. The user is asking, in 2025, about the right way to use @typescript-eslint/typedef.

Looking back on https://typescript-eslint.io/rules/typedef - the page doesn't actually mention the rule is deprecated until after the description & example code block. On smaller monitors and phones it's not even above the fold.

Proposal: how about we mark the rule as deprecated and feature-frozen?

Affected URL(s)

https://typescript-eslint.io/rules/typedef/

Additional Info

I'm not suggesting we remove the rule (yet?). I think a lot of folks have come to rely on it. But I don't see any reason to keep it around long-term, given the inexorable increase in cases where it's harmful.

💖