Migrating 600k+ Lines of Code from Flow to TypeScript
summary
Project migrates 600,000 lines from Flow to TypeScript using a Babel-based converter followed by the TypeScript compiler and a Stripe code mod as the automation backbone. Custom third‑party Flow types require manual fixes but migration finishes quickly in real work time. Results show build times cut to about half the compile time, editor feedback moves from tens of seconds to near instant, fewer hand‑written types, and faster onboarding and CI.
AI-written summary · about
chapters (20)
- 0:00Flow to TypeScript migration intro
- 1:06What is Git Kraken
- 2:52Why choose a type system
- 3:55Flow vs TypeScript differences
- 5:59Flow vs TypeScript compilers
- 7:04Nominal vs structural typing
- 8:27Why migrate 600k lines
- 9:10Popularity and ecosystem
- 10:56Flow performance issues
- 11:38Developer productivity gains
- 11:59Migration planning and automation
- 13:02What is a code mod
- 14:26Three phases of code mod
- 15:10Migration challenges
- 15:51Third-party library types
- 16:35Results and benefits
- 16:57Faster build times
- 17:39Improved developer experience
- 18:21Fewer custom types
- 19:03Q&A
related talks
37mSo You Decided to Do a Technical Migration
34mSo You’ve Decided to Do a Technical Migration
29mSo you’ve decided to do a technical migration
23mMoving from Flow to TypeScript — How the Yandex Zen Migration Went and Why the New Stack Is Better
47mSo You've Decided to Do a Technical Migration
31mSo you've decided to do a technical migration...
16mAll aboard the type train
38mPorting 100K lines of code to TypeScript