Writing TypeScript can be a bit hard or difficult at times. You can definitely get sucked into battles trying to figure out a lot of dumb shit that obviously works great but that you need to contort to something TypeScript can grok. Some of the errors it complains about are awful.
But on the other side, writing code consuming TypeScript libraries is amazing. Seeing all the type information in the IDE reveals so much, resolves so many questions, and builds confidence so quickly.
The other issue with TypeScript is that tooling is all awful & terrible. Tsconfig is a drag. There's a serious lack of good conventions to follow & tons of ad-hoc stringing shit together. Ideally libraries should output both esm & cjs but typescript literally doesn't support it & you have to run typescript twice, so now you maybe are introducing yet more new tools like concurrently if you want to do a good job. Oh and now your "watch" script is even more janked up too. Deno does a good job of making this pain all go away, but in general TypeScript is one of multiple layers of tooling that simply sucks, that thieves energy & attention.
But on the other side, writing code consuming TypeScript libraries is amazing. Seeing all the type information in the IDE reveals so much, resolves so many questions, and builds confidence so quickly.
The other issue with TypeScript is that tooling is all awful & terrible. Tsconfig is a drag. There's a serious lack of good conventions to follow & tons of ad-hoc stringing shit together. Ideally libraries should output both esm & cjs but typescript literally doesn't support it & you have to run typescript twice, so now you maybe are introducing yet more new tools like concurrently if you want to do a good job. Oh and now your "watch" script is even more janked up too. Deno does a good job of making this pain all go away, but in general TypeScript is one of multiple layers of tooling that simply sucks, that thieves energy & attention.