Maintain a Next.js 15 app before the move to 16

Video transcript

1. 0:00–0:06

   Account page • Run the newest patch • Check the lockfile • Ship fixes within days

   The Account page badge stays fixed in its lane. A lockfile sheet of blank rows slides in and one row is highlighted. A cyan route runs from that row to a dashed socket on the account page; a patch tile lifts from the highlighted row, travels along the route and docks in the socket. No version number is shown.

2. 0:06–0:12

   Account page • Clear the upgrade blockers • Await request data • No sync access left

   The Account page badge does not move. Three small request tiles wait by the account page; each gains a cyan waiting ring, then travels along its own lane into the page, where its slot lights up as it arrives. A fourth, stray tile without a ring drifts towards the page and fades out before reaching it.

3. 0:12–0:18

   Account page • Decide every cache • Defaults changed • Some caches remain • Uncached by default now • Still cached • Decide per resource • Refresh event

   The Account page badge stays fixed. "Defaults changed" and "Some caches remain" appear. The article's cache-decisions figure enters: the "Uncached by default now" shelf of dashed empty boxes, the "Still cached" shelf of solid boxes, the "Decide per resource" card and the "Refresh event" trigger. A cyan trace runs from each shelf into the decision card and on along a thin link to the trigger; pulses follow each route and the trigger's button is ringed when they arrive. No box is filled.

4. 0:18–0:24

   Account page • Keep each user’s data private • Two users, two languages • Never a shared hit

   The Account page badge stays fixed. Two separate lanes run in parallel, each carrying one user's data card to that user: one card's lines read left to right, the other's right to left. Between the lanes stands a dashed shared cache box; both cards pass it at the same time and neither enters it, so it stays empty.

5. 0:24–0:30

   Account page • Authorise in the data layer • Actions are public endpoints • Check inside each action • Page component • Route handler • Server action • Data-access layer

   The Account page badge stays fixed. The article's data-access-layer figure enters: the "Page component", "Route handler" and "Server action" blocks with arrows into the "Data-access layer" band, and a plain storage drum that the band reaches by an arrow. The Server action block is outlined, and a ring closes inside it before its pulse leaves. Cyan pulses run from every block into the band and on to storage; no pulse goes around the band, and the storage lid is ringed when the last pulse arrives.