It does make sense with TypeScript as it's a language. It, however, does not make sense with "tooling" (IMHO - there may be of course obvious stuff I may be missing).
Tooling may also use a transpiled language but again, I, as a developer who's very experienced with JS, don't see a big win there.
Someone mentioned Flow + OCaml as a bad example and how it doesn't work out for them, but that's more than tooling. At that point you are not using tools written in other languages to build JS, you are just using other languages.
Flow failed because Microsoft enabled TypeScript by default in VS Code. It had nothing to do with OCaml in my opinion.
However, TypeScript is now suffering from long compile-times because it targets JS. If it was implemented in a language with more control over threading etc. I think it could be faster.
Tooling may also use a transpiled language but again, I, as a developer who's very experienced with JS, don't see a big win there.
Someone mentioned Flow + OCaml as a bad example and how it doesn't work out for them, but that's more than tooling. At that point you are not using tools written in other languages to build JS, you are just using other languages.