Q50: How did fetch() default caching change between Next.js 14 and Next.js 15?

In Next.js 14, fetch() requests defaulted to aggressive caching (cache: 'force-cache'). In Next.js 15, fetch() GET requests default to uncached (cache: 'no-store') by default. To cache requests in Next.js 15, developers must explicitly pass { cache: 'force-cache' } or set revalidate timers.

Explicit Caching in Next.js 15+
// Next.js 15: fetch is UNCACHED by default!
// To explicitly cache in Next.js 15:
const data = await fetch('https://api.com/data', {
  cache: 'force-cache', // Explicitly enables Data Cache
});
💡 Next.js 15 switched fetch defaults to uncached, requiring explicit flags for data caching.
Key Takeaways
  • Next.js 14 default: force-cache (cached static default).
  • Next.js 15 default: no-store (uncached dynamic default).
Knowledge Check

What is the default caching behavior for fetch() GET requests in Next.js 15?