Let’s Make A Framework
summary
Builds a tiny Next.js-style framework using Express + renderToString, dynamic file-system routing, and basic server component support that moves data fetching off useEffect into async components. Implements an async unwraper that waits for promise-returning components, serializes the resulting JSX tree to window for the client, and restores it to enable soft navigation and state persistence. Demo is a hackfest but functional after a fix — server rendering, server-side data fetching, and client pick-up of serialized trees all work; not production-ready but shows the exact mechanisms.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:11Why use a framework
- 3:18Building server rendering
- 8:14Adding data fetching
- 10:20Server components explained
- 17:45Soft navigation demo
- 21:19Does everyone need a framework
- 22:44Summary and closing
related talks
32mWhy everybody needs to use a framework
30mReact Server Components
39mReact Server Components: A Deep Dive
27mAnd Now You Understand React Server Components
21mReact Server Components
40mServer Components for the Rest of Us
12mReact Server Components and SSR: How it Fits
34mWhat's Next? Exploring the future of React