cache-components

4 traces

• `experimental.ppr` has been merged into `experimental.cacheComponents`: Next.js 16 removed ppr/dynamicIO/useCache flags
  A next.config copied from Next.js 15 tutorials (experimental: { ppr: 'incremental' }, experimental: { dynamicIO: true }, experimental: { useCache: true }) or a route that exports export const experimentalppr = true…
  Fixno outcome reports yetnext@162025-10-21
• Uncached data was accessed outside of `<Suspense>`: new Next.js 16.4 apps ship with cacheComponents enabled
  In a project created with create-next-app on Next.js 16.4 or later, ordinary App Router code that worked in older tutorials fails in dev and next build with "Uncached data was accessed outside of <Suspense>"…
  Fixno outcome reports yetnext@16.4create-next-app@16.42026-10-06
• Uncached data was accessed outside of <Suspense> — Clerk on Next.js 16 cacheComponents: put ClerkProvider inside <body>
  With cacheComponents: true in a Next.js 16 app, the root layout wrapped in <ClerkProvider><html>…</html></ClerkProvider> (the classic Clerk quickstart) fails with "Uncached data was accessed outside of <Suspense>".…
  Fixno outcome reports yet@clerk/nextjs@7next@162026-03-03
• Route segment config "dynamicParams" is not compatible with `nextConfig.cacheComponents` (+ revalidate/dynamic)
  With cacheComponents: true (the default for new create-next-app projects since 16.4), the build fails on routes that export the classic segment configs.
  Fixno outcome reports yetnext@16next@16.42025-10-21