Frameworks Panel
summary
Framework teams describe concrete wins and pain points: Vite becomes the shared build layer, Nitro is positioned as a framework-agnostic adapter runtime, and incremental static regeneration is now in Nitro with Netlify support. SvelteKit ships SSR route splitting that deploys individual routes to separate Lambdas; teams admit about 20 community-maintained adapters exist. Qwik pushes resumability over hydration. Work focuses on standardizing runtime APIs (Winter CG, hat-tip JS) so adapters stop being reimplemented for every platform.
AI-written summary · about
chapters (5)
- 0:00Introduction and panel setup
- 2:33Framework introductions
- 15:17Vite as a shared build tool
- 22:15Adapters and edge deployment
- 41:21Closing remarks and shoutouts
related talks
51mBeyond the Framework: Building for the Next Decade of the Web
50mNuxt and Vite Core Teams LIVE panel
38mBuilding a Framework for the Edge
53mThe Future of Frontend
20mThe formation of Framework Waves from the Epicenter
32mWhat's Happening in the JavaScript Ecosystem?
29mQuo vadis, frontend?
07h 16mJetBrains JavaScript Day 2022
