Remixing the Bundler
summary
Claim: frameworks stop owning bundlers and become plugins for Vite. Evidence: Remix migrates off esbuild into a Remix Vite plugin, ships an unstable plugin then keeps a CLI for build orchestration until Vite adds a Builder/environment API in v6. Specifics: esbuild for dev, rollup for prod historically, hot module reloading and multiple server builds force orchestration. Surprise: about half of all React installs use react router. Outcome: conventions move into a plugin and core routing merges back into react router.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:14Libraries vs frameworks in React
- 2:26Remix as full-stack framework
- 3:34Remix’s bundler and esbuild origins
- 5:21From esbuild to Vite
- 8:05Vite plugin limitations
- 10:00Remix Vite stable release
- 11:03Vite’s environment API
- 13:40Vite benefits for authors
- 15:11What remains of the framework today
- 16:00Merging Remix into React Router
- 17:07Why this shift matters
- 19:23Conclusion
related talks
36mYou build React apps: do you even know how?
10mReact Router + Vite is a Framework
38mVite, a New Era of Frontend Tooling?
51mDo We Need a Build System?
20mThe Inner Workings of Vite Build
25mThe Eternal Sunshine of the Zero Build Pipeline
55mUse the Platform With Framework Agnostic Routing
26mThe Ultimate Full Stack Framework for 2024: Remix