I just feel typescript usually gets in the way, sometimes in a good way, but all too often in a bad way.
Plus my main gripe with typescript is that microsoft owns and controls it so I won't use it just because of that.
Instead, I spent a whole bunch of time wrestling with the tooling and configs in order to get my (previously working) code to compile.
I'm not trying to make the conclusion that typescript is bad, as I've hardly even used it at this point. But from my experience, it's not exactly the 1:1 from JS that some people argue. My takeaway is that there can be real value to be had from static typing in JS, but it might not always make sense to introduce the tooling overhead for tiny codebases that are developed by a single maintainer.
People go in this trap again and again, including myself.
"Oh this FAANG uses this, it must be great and suitible for us" - no, it's suitible for them because they have completely different problems than you and have to do stuff in a much more complicated way than you need to.
I also feel Typescript is good, but sometimes it is hard to use because of so many typing. It needs VScode always for auto complete helper. I remember javascript as an old good days...