Typescript Is SO SLOW...Or Is It?
summary
TypeScript projects slow because the compiler treats everything as one big graph; a demo shows a single app build at 112 seconds, a naive monorepo at 235 seconds, and using workspaces plus Nx to build packages first drops the build to 76 seconds. The talk shows removing Vit for parity, explains that path aliases don’t isolate types, and recommends project references and prebuilding .d.ts outputs to fix editor lag (TRPC/template-literal-heavy types cause live-eval slowdowns).
AI-written summary · about
chapters (12)
- 0:00Introduction to TypeScript
- 1:50Why TypeScript is slow
- 2:55Build speed and hardware limits
- 3:38Demo: Slow TypeScript build
- 6:28Solution: Build smaller modules
- 8:23Path aliases and TypeScript resolution
- 10:49Workspaces for isolated modules
- 13:39Project references for types
- 17:15Editor speed and type complexity
- 19:47Live evaluation and performance
- 21:13Future: TypeScript Go
- 22:17Summary and best practices
related talks
28mThe Secret To Fast TypeScript
28mTypescript Performance: Going Beyond The Surface
24mTypeScript and how I've learned to love the compiler
36mNavigating TypeScript Performance for Better Dev Experience
01mMeet Mike Hartington
40mTypeScript: State of the Union
01h 00mTalkScript with the TypeScript Team
50mTypescript 2 and failing faster