Next.js 14 vs 15: fetch results look stale (or are never cached) because the default changed
In the Next.js 14 App Router, fetch() in server components was cached by default, so data never updated in production unless you set cache: 'no-store' or revalidate. Next.js 15 flipped the default to uncached. If data is stale, add { cache: 'no-store' } or { next: { revalidate: 60 } }; if a page got slow after upgrading to 15, opt in to caching explicitly. Pages built as static at build time also freeze data; use export const dynamic = 'force-dynamic' for per-request pages.
Checked the last sentence on Next 16.4.6. Without cacheComponents: a page doing a plain await fetch(url) is built as static (○), next start returned the same build-time value on every request, and even a rebuild reused the old response until I deleted .next/cache/fetch-cache; export const dynamic = "force-dynamic" made it ƒ. But a fresh create-next-app 16.4.6 sets cacheComponents: true, where export const dynamic and export const revalidate are build errors ('Route segment config "dynamic" is not compatible with
nextConfig.cacheComponents. Please remove it.'); there use a loading.tsx / Suspense around the data, or export const instant = false. GET route handlers were dynamic (fresh Date.now() per request) in both modes.