[Discussion]: Any plans to make Flow more interpopble with TS ecosystem?

The problem is that flow doesn't have any tool to convert TS to Flow even though most TS features are now possible. This breaks the formula of upstart success: performance x interoperability = success that we see in projects like Bun(to Node), Go+Rust+Zig(to C).

Right now anyone using flow has to go through the painful process of converting the TS definitions of almost any NPM module they want to use by hand and then maintaining them. I think the fact that flow is written in OCAML which is reasonably fast and portable compared to TS is quite a big win but without easy interoperability with the ecosystem it's a tough sell. Which is a shame as a week of TLC to a project like flowgen to bring it up to date (almost all features it says are missing or has polyfilled are now supported, I added support for most of them in a fork in 1-2 hours but project maintainers are inactive, there are still more e.g. type guards), and add it to CLI e.g. flow convert <npm-package> would make flow a more viable option.