Skip to solution
mediumFrontend

Caching defaults in Next 15 — what is no longer cached by default?

989 views
01

Understand the problem

Next 15 flips GET Route Handlers and fetch to uncached unless you opt in — subtle upgrade gotcha.

cachingnextjs-15
02

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Nudge consolestandby

Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.

03

Study the solution

Next 15 makes fetch and GET Route Handlers dynamic by default — add cache: 'force-cache' / 'use cache' or export const dynamic = 'force-static' to re-cache.

<marker id="a" viewBox="0 0 10 10" refX="9" refY="5" markerWidth=

Solution ready — 2 min read

Classified // press E to declassify

04

Join the discussion

Discussion (0)

Sign in to join the discussion.

No responses yet. Be the first to share what you think.

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

Dossier 22 of 95 decoded in the Next.js track. One more won't hurt.

Back to track