check-cache

Audit caching configuration in $ARGUMENTS for Next.js 15 correctness.

This project uses Next.js 15, where the default fetch cache behavior is no-store (no cache). Pre-Next.js 15 defaults (force-cache) are incorrect unless explicitly intentional.

Scan for these patterns:

1. fetch calls without explicit cache option

   • In Next.js 15 these default to no-store, which is correct
   • Flag if the data looks like it should be cached (static content, rarely-changing data)
   • Suggest adding { next: { revalidate: N } } if appropriate

2. { cache: 'force-cache' } usage

   • Flag every instance — this was the pre-15 default but is now an explicit choice
   • Verify it's intentional: is this data truly static and safe to cache indefinitely?
   • If not, replace with { next: { revalidate: N } } with an appropriate revalidation period

3. export const revalidate at segment level

   • Check the value is intentional and matches the data freshness requirements
   • Flag export const revalidate = false (cache forever) — usually too aggressive

4. Missing revalidatePath or revalidateTag after mutations

   • Check Server Actions that mutate data
   • If no revalidation call exists after a write, the UI may show stale data indefinitely
   • Suggest appropriate revalidation based on what was mutated

5. export const dynamic = 'force-static' with dynamic data

   • Flag if the route fetches user-specific or frequently-changing data while forced static

6. GET Route Handlers without explicit caching config

   • In Next.js 15, GET Route Handlers are no longer cached by default
   • If a Route Handler returns data that should be cached (e.g., a product list, static config), flag the missing export const dynamic = 'force-static' or export const revalidate = N
   • Do NOT flag handlers that return dynamic/user-specific data — uncached is correct there

Output format: For each file with caching issues:

app/products/page.tsx
  Line 12: fetch('/api/products', { cache: 'force-cache' })
  ⚠️  force-cache is now explicit in Next.js 15. Is this data truly static?
  Suggestion: { next: { revalidate: 3600 } } if it changes hourly, or keep force-cache if truly static

app/actions/updateCart.ts  
  Line 8: await db.cart.update(...)
  ❌ No revalidatePath() call after mutation
  Suggestion: Add revalidatePath('/cart') after the update

End with a caching strategy summary: how many routes are uncached, how many are force-cached, how many use time-based revalidation, and whether the overall strategy looks coherent.