uncached by default
The Next.js 15 behaviour where fetch requests, GET Route Handlers and client navigations are not cached unless you opt in.
In more detail
Next.js 14 cached fetch and GET handlers automatically, which surprised many developers with stale data. Version 15 flipped these defaults; use force-cache, revalidate, staleTimes or dynamic = 'force-static' to cache again.
Related terms
- Data Cache — The second Next.js caching tier: a server-side store of fetch results that persists across requests, users and deployments.
- force-cache — The fetch option that tells Next.js to look in the Data Cache first and store the response there on a miss.
- staleTimes — An experimental next.config option that sets how long the Router Cache may reuse dynamic and static page segments.
Taught in
- Data Cache: Cross-Request Persistence & Fetch Tags — Next.js 15 & Modern App Router Architecture