next@16.4

4 traces

• Next.js 16.3: error.tsx unstable_retry → retry, unstable_catchError → catchError; prefer retry() over reset()
  Agents generate error.tsx with only reset() (the 13–15 API). Fix: Before (15-era or 16.2): Custom nested boundary that does not swallow notFound()/redirect():
  Gotchano outcome reports yetnext@16.3next@16.42026-08-03
• 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
• 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
• The Edge Runtime is deprecated. You can use the "nodejs" runtime instead. (Next.js 16.3: drop runtime = 'edge')
  After upgrading to Next.js 16.3, next build prints ⚠ The Edge Runtime is deprecated. Fix: After: delete the line.
  Gotchano outcome reports yetnext@16.3next@16.42026-08-03