Static and Dynamic Next.js
summary
Claims that Next.js gives automatic server-rendering, code-splitting and hot reload with no setup are demonstrated with concrete builds: a Hacker News clone (next news) showing real‑time vote updates and a Messenger clone (next sender) that lazy-loads photos and Google Maps. The talk shows next export producing static HTML, uses dynamic import plus a server-side synchronous require trick, relies on webpack chunks and link preload tags, and wires into deployment tooling — the examples run and the techniques scale.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:12Hot Code Reloading
- 4:25Server Rendering
- 4:46Next Export
- 5:30Code Splitting and Routing
- 6:09Team Scalability
- 7:10Automatic Road Mapping
- 8:10React Lifecycle
- 9:05Workflow
- 19:30Linked Preload Tags
- 20:15Reactor Reconciliation
- 26:49Render versus Pwa
- 28:29How Do You Handle Coding while Also Caring about Authentication and Permissions
- 31:19How Do You Handle a Piece of State Is Common for Multiple Pages
- 37:56How Does Next Deal with Dynamic Dependencies for the Client Code and Also What Does It Use under the Hood
related talks
36mNext.js by Example
34mWhat's Next? Exploring the future of React
27mAn introduction to Next.js and what's to come in 2021
15mBuilding Isomorphic JavaScript Apps Faster with Next.js
26mNext level Coding
33mUniversal React Apps Using Next.js
12mNext.js at the Edge
18mNext.js - The Hybrid Architecture for Web Developer