Turbopack. Why? How? When? and the Vision...
summary
Claims a Rust core using Rust+SWC to get parallelism and memory safety, plus a Turbo Engine that records dependencies as a task graph (about 200 tasks per module in practice) to make incremental builds independent of app size. Implements lazy asset graphs so dev-server builds only requested pages, and plans remote shared caching and team-wide graphs. TurboPack and the engine are open source, alpha-quality and not yet feature-complete for production.
AI-written summary · about
chapters (10)
- 0:00Turbopack intro and mission
- 1:56Why Turbopack was created
- 6:30Webpack challenges and incremental builds
- 10:49Turbo Engine architecture and Rust
- 13:19Caching and parallelism in Turbo Engine
- 17:53Turbopack as mixed-environment bundler
- 19:58Next.js integration and plans
- 21:46Turbopack plugin system and vision
- 23:51Turbo Engine future and cloud builds
- 25:38Granular caching and performance insights
related talks
48mTurbopack: DX Matters
17mTurbopack - Rust-based successor to Webpack
24mTurbopack and Rspack - Modern day JavaScript bundlers
23mRspack: The Rust-Fueled Bundling Breakthrough
45mBundler Bonanza
16mRealtime Webpack - Pushing on-demand bundling to the limits
36mWhat’s Inside TurboFan?
20mThe Untold History Behind Lynx