Overview

Following #7997 -> #9783 (comment) -> #9857: we'd like to not have a dependency on TypeScript's full JSDoc parsing. But at least our no-deprecated rule relies on it, as does the older community deprecated/deprecated. That means #9857 is blocked until at least ours can no longer use TypeScript's JSDoc parsing.

Instead, we'd like to write a separate, small, quick JSDoc parser utility. It could just look for @deprecated on a node & parse out any deprecation reason(s) as text. There's no need for it to look for other tags or get any more rich info.

💖