3 ms·
It basically depends how deep the other tooling is sticking its claws into TS internals which won’t be accessible in the same way anymore. I’ll bet the two mos
by anon7000 1y ago
It basically depends how deep the other tooling is sticking its claws into TS internals which won’t be accessible in the same way anymore.
I’ll bet the two most painless improvements will be:
- tsc just for type checking. (A lot of places run tsc just as a type checking step, and avoid type checking during the full build.)
- TS language server. By far the worst part of TS for large repos today — in my main monorepo, it consumes like 10GB of RAM and actions like “jump to definition” become so slow that it’s unusable.
Things that may be painful:
- Integration with 3rd party compilers like webpack which use TSC. Also unsure how tools like Rspack will need to consume tsc, given that they use a highly parallel rust architecture already.
- Integration with tools like Jest which need to transpile code before running TS.
- Integration with running Node directly — eg swchook or ts-node for bin scripts