flowts
flowts copied to clipboard
zxbodya
utility script to convert project from flow to typescript
👋 big fan of this project! Has worked surprisingly well for my use case :) Though doing a roughly 1:1 syntax translation is nice, I've found that migrations can often...
1. Add support for replacing global types like `Intl$DateTimeFormatOptions` with expressions like `Intl.DateTimeFormatOptions`, generate such replacements for built-in types 2. ~~Fix `.importFlow` - currently it might work not correctly when...
TypeScript has both `undefined` and `void` types. But in flow there is only `void`, which is used for both use-cases. Currently `void` type is not changed in converted code, however...
Hi @zxbodya. I was wondering what's the current state of the project? What made you not use https://github.com/Khan/flow-to-ts for the migration from flow to TypeScript? For context, we are currently...
We have the need to generate a type report that we can see to what the types of a package are converted. Basically generating a report.json that shows all types...
Interesting concept. Wondering if this could be something that is also interesting for flowts: https://github.com/Airtable/typescript-migration-codemod/blob/main/src/typescript/flow_type_at_pos.ts This would add annotations, where flow knows the type so it would increase type coverage....
Not sure if it is valid to use multiline comments like this, any idea what could cause this? ```js export const foo = (): string[] => /** * Multiline comment...
What do you think about removing all sorts of flow suppression comments? Happy to do it if nothing speaks against it :)
Commands run with `--no-prettier` ### before/after JSX property Input: ``` // @flow ({ a, b: ( ), c, }); ``` Output with recast: ``` ({ a, b: ( ), c...
I am doing a conversion from Flow to TypeScript when I am modifying the Flow source in order to get the TypeScript to compile properly without errors with tsc. So...
