I have written at least 10 apps in TS with dozens of libraries, including some server-only stuff.

All the problems I've had were with JS and npm. TS has been amazing and worked flawlessly. I just can't understand your experience at all.

That's alright. We're obviously not working on the same projects, and are likely taking different approaches to reach our goals.

NestJS is quite a bit better in that regard, but in general I agree with your overall point. What do you feel most of these frameworks are missing re. dev experience?

Mostly use other languages for back-end systems, but I will definitely be checking out NestJS soon.

With regards to TS, generally, it takes a lot of effort to get it to work. More often than not, getting to that point in a way that is actually useful/practical and cost effective, requires yet another library to be installed.

Just look at the TSLint/ESLint migration problems, the popularity of all those TS runners such as ts-node/ts-node-dev/tsx-watch/ts-babel/etc., the complete lack of interoperability between all those separate pieces.

Many issues and even proposed fixes to parts of the TS ecosystem - which is all community ran - are either ignored, left open because no one seems to be able to figure it out, or deemed to be out of scope.

I don't know how to fix this honestly. Some leadership from Microsoft would be a good start.

Yeah that’s fair: I’m a bit of an early adopter of Deno [0] for that reason, it helps standardise quite a bit of that. Promising, anyway, if a bit rough currently.

[0] https://deno.land

You don't need any of those. TSLint was deprecated long ago, and TS runners are only mildly useful in development (to the point where I don't bother and just `tsc && node dist`). Are you sure it's a problem with the ecosystem?