TypeScript at Google
summary
Google migrates from zero to 70,000 TypeScript files by building a Closure→TypeScript translator, typed interoperability tooling that preserves checks at boundaries, and Bazel-integrated compiler upgrades that take about three to four engineering weeks. One-compiler-for-all policy yields a 0.8s median compile and allows repo-wide automated fixes via MapReduce jobs that converted RxJS usages and updated 8% of users. A new cc checker surfaces bugs that 21% of responders say would otherwise be missed.
AI-written summary · about
chapters (20)
- 0:00Intro
- 3:10Benefits
- 5:16Ecosystem
- 7:13TypeScript
- 8:30Hard Part
- 11:06Big Takeaway
- 12:00Where we are now
- 13:49Downside
- 17:11Code Formatting
- 18:13Style Guides
- 20:45Static Analysis Tools
- 22:38Examples
- 25:08TT
- 25:50CCC
- 26:53Early feedback
- 27:55How we do it
- 28:10Example
- 32:17Incremental builds
- 32:55Monitoring
- 34:13Open Source
related talks
24mTypeScript and how I've learned to love the compiler
39mTypeScript: Why? When? How?
40mTypeScript: State of the Union
30mTypeScript: Seeing Past the Hype
38mPorting 100K lines of code to TypeScript
33mTypeScript - JavaScript you are gonna love
57mTypeScript : More than just another JS transpiler
31mJavaScript That Scales