🎉 Using TypeScript is fun, but Flow is even better. The typing systems are similar, but the community is quickly supporting Flow for React. Take React Native for example, Flow is supported by default while TypeScript is a nightmare to configure (think /build dir, hot reloading, and concurrent typescript compilation separate from babel).
With this increase in open-source effort, many companies are doubling down on Flow (Facebook, Uber, etc.).
Adopt Flow instantly with TypeWriter.
⚡️ Tell TypeWriter which files you care about, and it will run a big list of codemods instantly!
⚠️ This is early stage software. There will be bugs. Please help improve it by using this and reporting issues ⚠️
🔧 There is minor manual work after running TypeWriter. If you see room for improvement, create an issue!
ensure your types are in types, types/*, interface/*, or interfaces/*
// imports from types change// "import {Prop} from './types'" -> "import type {Prop} from './types'"// imports from everywhere else are left alone// "import {NotProp} from './not-types'" -> "import {NotProp} from './not-types'"
Remove readonly
Before:
{ readonly color: string}
After:
{ color: string}
JSX.Element -> React.Node
In prop typings for TypeScript, a react element is called JSX.Element while in Flow this is React.Node.