Turbopack and Rspack - Modern day JavaScript bundlers
summary
Turbopack is a Rust reimplementation from Vercel that uses an incremental computation engine plus SWC to cache function inputs and outputs so rebuilds only reexecute changed files, claiming lightning-fast HMR with millisecond updates regardless of app size but currently lacks Next.js server actions support. Rspack, open sourced by ByteDance, is Rust based and largely Webpack-compatible (≈90%) so existing webpack configs and plugins often work; both aim to cut cold-start and dev-loop times compared to older bundlers.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 1:32Benefits of modularizing code
- 2:58History of JavaScript bundlers
- 5:24Webpack limitations and slowdowns
- 5:44Introducing Turbopack
- 8:15Turbopack features and benefits
- 10:49Turbopack architecture
- 13:40Why Turbopack is so fast
- 15:52Getting started with Turbopack
- 16:12Introducing Rspack
- 17:42Rspack features and compatibility
- 18:44Introduction to Bun
- 20:55Choosing the right bundler
- 21:17Introduction to Vite
- 23:04Summary and recommendations
related talks
23mRspack: The Rust-Fueled Bundling Breakthrough
17mTurbopack - Rust-based successor to Webpack
48mTurbopack: DX Matters
27mTurbopack. Why? How? When? and the Vision...
45mBundler Bonanza
39mBundlers: a deep dive into modern JavaScript build tools
20mThe Untold History Behind Lynx
21mWebpack: Final Reckoning