4 ms·
The reality is not that we don’t want to support TS, but that its pipeline is significantly different from what we use at FB, so we neither have the expertise,
by danabramov 9y ago
The reality is not that we don’t want to support TS, but that its pipeline is significantly different from what we use at FB, so we neither have the expertise, nor can integrate the other tools we rely on. This might get better as AST interop between tooling improves.
- hzoo 9y agoYep, and we (Babel) are trying to work with TS on integrating it into Babel similar to how flow works with Babel (parser support + a plugin/preset to strip types). Again, limited resources so if the community really wants it, we would appreciate help in reviewing PRs and testing! https://github.com/babel/babylon/issues/320 https://github.com/babel/babylon/issues/320, https://github.com/babel/babylon/issues/523 https://github.com/babel/babylon/issues/523
- Vinnl 9y agoThat's awesome, I didn't even know that was a potentially viable route! Thanks for sharing :)
- hzoo 9y agoYeah it's definetely a lot of work on both ends (also means would need to coordinate releases of both like we do with flow) but hopefully this helps the ecosystem that wants to use both (seems to be an increasingly higher number of people).