3 ms·

Thanks for the insights. I haven't encountered any issues with third party code myself and don't mind the client/server model, but for me the killer app is Babe

by pluma 11y ago

Thanks for the insights. I haven't encountered any issues with third party code myself and don't mind the client/server model, but for me the killer app is Babel support (so flow is only a type checker, not another transpiler). Do imports and import resolution work out of the box in TS these days? Last time I tried, I had to jump through hoops to get it to understand node imports and it wouldn't work without magical comments. I also don't want to have to wrap everything in module declarations -- the import logic of node should be sufficient. If TS has sorted these problems out, it might be worth another look for me.

Keats 11y ago
You just have to declare which external module (3rd party dep) you are using so typescript knows how to apply typings. Ie you can use ES6 imports, you just need to have a /// <reference path="../typings/all.d.ts" /> line or declare them in tsconfig.json now (I believe, haven't checked yet). I agree the modules are tricky and my least favourite thing about TS though
- pluma 11y ago
  Eh. Those magical comments were what turned me off using TS to begin with. If I'm importing stuff, I'm already declaring my dependencies. TS seems to prefer re-inventing the wheel whereas flow just builds on what is already there. But that's just my (unfairly biased) impression. EDIT: Shame Flow is written in OCaml rather than built on Node. That's the only thing I prefer about TS at this point.