The downsides of writing a large project in Typescript: https://medium.com/javascript-scene/the-typescript-tax-132ff4cb175b
I don't share all the author's views, but makes interesting comments on what percentage bugs get caught by the typechecker, and type declaration verbosity/placement challenges.
Related Posts
I've dabbled with 'conventional commits' for a personal project but I found they slowed me down.
It's not always easy to categorise a commit as a fix, a chore etc. Sometimes refactorings also fix bugs.
Do you use them? I can imagine a large, mature project benefitting more.
Really cute approach to reporting type errors: when there's a type error, show an example of a runtime error that the type check has prevented!
Data-Driven Techniques for Type Error Diagnosis https://escholarship.org/uc/item/59s4h4pv
ASTs typically discard comments, and that's usually what you want.
The only time (AFAICS) that preserving comments is useful is for writing a code formatter.
Could you write a formatter in terms of a list of lexemes? A CST is a non-trivial bit of code for one use case.