he/him 
TypeScript doesn't support top-level await either 
https://github.com/Microsoft/TypeScript/issues/25988 …
Show this thread
Anyone migrated a large Flow codebase (40K+ lines) to TypeScript very easily? Bashing my head against the wall with a personal project, and am dealing with the lack of bigint, proper Symbol support, top-level await, missing core typelibs, type widening, poor IDE support etc...
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
To be clear, the items listed are things Flow does not support, or supports poorly.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
As a use of neither, mind me asking what are your reasons for going Flow -> Typescript
-
Flow does not have the things listed, so those are my complaines
End of conversation
New conversation -
-
-
wait, flow has top-level await? why?
-
It doesn't support it.
End of conversation
New conversation -
-
-
Is the IDE support often very different for TypeScript? The Flow support seems about the same as TypeScript support in PhpStorm, I haven't tried other IDEs though. Both should support LSP, so it should be similar.
-
In VSCode it’s not great. I’m comparing it to the CLI output and support in Atom.
End of conversation
New conversation -
-
-
4 weeks for a team doing in in their spare time to migrate 30k lines of code. Flow and TS are very similar, but our Flow coverage wasn't as good as it could have been, so certain modules were easier than others. It's more grunt work than technically difficult. Blog post coming!
-
Thanks got the details! This is a strongly typed app with zero third-party dependencies so seems like it would avoid some of the trouble the Jest migration had.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.