> nextjs-data-fetching

Fetch API, Caching, and Revalidation strategies. Use when fetching data, configuring cache behavior, or implementing revalidation in Next.js. (triggers: **/*.tsx, **/service.ts, fetch, revalidate, no-store, force-cache)

fetch
$curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/nextjs-data-fetching?format=md"
SKILL.mdnextjs-data-fetching

Data Fetching (App Router)

Priority: P0 (CRITICAL)

[!WARNING] This skill covers App Router data fetching (fetch). If the project uses the pages/ directory, you MUST use getServerSideProps or getStaticProps instead. Ignore this file's native fetch caching advice.

Fetch data directly in Server Components using async/await.

Strategies

  • Static: Build-time. fetch(url, { cache: 'force-cache' }).
  • Dynamic: Request-time. fetch(url, { cache: 'no-store' }) or cookies().
  • Revalidated: fetch(url, { next: { revalidate: 60 } }).

Patterns

  • Direct Access: Call DB/Service layer directly. Do not fetch your own /api routes.
  • Colocation: Fetch exactly where data is needed.
  • Parallel: Use Promise.all() to prevent waterfalls.
  • Client-Side: Use SWR/React Query for live/per-user data (no SEO).

Revalidation

  • Path: revalidatePath('/path') - Purge cache for a route.
  • Tag: revalidateTag('key') - Purge by tag.

Anti-Patterns

  • No Root Awaits: Avoid blocking the entire page. Use <Suspense>.
  • No useEffect: Avoid manual fetching in client effects.
  • Internal API: Never call /api/... from Server Components.

Examples & References

┌ stats

installs/wk0
░░░░░░░░░░
github stars341
██████████
first seenMar 17, 2026
└────────────

┌ repo

HoangNguyen0403/agent-skills-standard
by HoangNguyen0403
└────────────

┌ tags

└────────────