Videos / Web Dev

Episode 14 of 16 · Web development, end to end

Next.js: rendering on the server, and the boundary that decides everything

Chapters

1. Three places to make a page0:00
2. Static, and stale0:16
3. Rendered per request0:34
4. The empty page, and the wait0:52
5. Sent in pieces1:10
6. Painted, and still dead1:27
7. Folders are the URL1:46
8. The reserved names2:02
9. Layouts survive the move2:20
10. Brackets are parameters2:39
11. Loading is a boundary, not a spinner2:58
12. Navigation patches the tree3:15
13. The printing plate3:34
14. Await, right here3:50
15. What runs once cannot react4:07
16. What comes down the wire4:24
17. What may cross the seam4:42
18. The imports that never ship5:02
19. A door, not a wall5:20
20. The directive is contagious5:36
21. Children is the escape hatch5:55
22. Props, and the one exception6:14
23. Providers and state6:30
24. Interactivity is a leaf6:49
25. Two people in the same room7:06
26. The waterfall7:23
27. Four caches, named7:41
28. The two dials8:02
29. Revalidation, the hard half8:20
30. The stale copy, served8:39
31. The form, before all this8:56
32. The server action9:13
33. One submit, two paths9:29
34. Pending, and the errors9:46
35. An action is a public endpoint10:05
36. Closing the write loop10:24
37. The whole thing10:42

Next.js: rendering on the server, and the boundary that decides everything. A web page has to become H T M L somewhere, and there are only three places that can happen. On a build machine, before anyone asks. On a server, the moment someone asks. Or in the

Mark as watchedSaved in this browser only.