> i) Like a framework, you are at the whim of TS devs as it gets updated (edited)
I have been using TypeScript for almost 6 years and not experienced this problem. Like everything else keep things simple, don’t chase trends, and so long as do right by your product everything will be smooth. I also don’t waste time with large SPA frameworks.
> ii) Libraries are badly documented
I don’t use many dependencies. The DOM and Node type definitions are extremely well documented and inspired me to write better documentation.
> iii) Error messages are hard to follow
For me this depends on the complexity of a given object or type definition. When things are primitive the error messages are more clear. My only suggestion is to keep your interfaces primitive.
> iv) It requires yet more transpilation
I use SWC as a TypeScript stripper. My nearly 50kloc project takes about 2seconds to covert to JS, which pushes out my total build time to about 2.5seconds.
I have been using TypeScript for almost 6 years and not experienced this problem. Like everything else keep things simple, don’t chase trends, and so long as do right by your product everything will be smooth. I also don’t waste time with large SPA frameworks.
> ii) Libraries are badly documented
I don’t use many dependencies. The DOM and Node type definitions are extremely well documented and inspired me to write better documentation.
> iii) Error messages are hard to follow
For me this depends on the complexity of a given object or type definition. When things are primitive the error messages are more clear. My only suggestion is to keep your interfaces primitive.
> iv) It requires yet more transpilation
I use SWC as a TypeScript stripper. My nearly 50kloc project takes about 2seconds to covert to JS, which pushes out my total build time to about 2.5seconds.