hasToggle
The lab

Everything Next.js can do, one chapter at a time.

Every chapter opens on something developers say — to ourselves, or to each other — and runs the real feature next to it. And as much of Vercel as can be proved from inside a web page.

components & state

  1. I’ll put “use client” on it, to be safe.server & client components
  2. I don’t need state for a simple counter.useState & re-renders

data & caching

  1. It’s either cached or it isn’t.caching & revalidation
  2. I’ll fetch it all first, then render.streaming & suspense
  3. You need an API route for that.server actions & cookies
  • optimistic UI & useActionState
  • ISR & pages baked on demand

routing & navigation

  1. navigation & prefetchinglands Monday · 31 Augprefetched for you · 0 routes
  • dynamic routes & params
  • proxy, redirects & rewrites
  • error, not-found & recovery
  • parallel & intercepted routes
  • i18n & locale routing
  • view transitions

metadata & assets

  1. I’ll need to design a card for every page.imageresponse & route handlers
  • next/image, fonts & the asset pipeline
  • metadata, sitemaps & SEO

the platform

  • edge network & geolocation
  • feature flags & Edge Config
  • web vitals, measured live
  • preview deploys & instant rollback
  • cron, queues & background work
  • blob, key-value & Postgres
The weekly build

A new chapter every Monday. The write-up lands in your inbox.