giuseppe-trisciuoglio/developer-kit / plugins/developer-kit-typescript/skills/nextjs-data-fetching
nextjs-data-fetching
VerifiedProvides Next.js App Router data fetching patterns including SWR and React Query integration, parallel data fetching, Incremental Static Regeneration (ISR), revalidation strategies, and error boundaries. Use when implementing data fetching in Next.js applications, choosing between server and client fetching, setting up caching strategies, or handling loading and error states.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.7 KB |
| references/caching-strategies.md | markdown | 2.7 KB |
| references/client-fetching.md | markdown | 3.2 KB |
| references/data-fetching.md | markdown | 2.8 KB |
| references/error-boundaries.md | markdown | 2.2 KB |
| references/error-loading-states.md | markdown | 3.3 KB |
| references/react-query.md | markdown | 8.2 KB |
| references/server-actions.md | markdown | 3.3 KB |
references/data-fetching.md
View on GitHub# Data Fetching Patterns
## Server Component Fetching (Default)
Fetch directly in async Server Components when the data is needed for the first render and no browser-only state is required.
```tsx
async function getPosts() {
const res = await fetch('https://api.example.com/posts');
if (!res.ok) throw new Error('Failed to fetch posts');
return res.json();
}
export default async function PostsPage() {
const posts = await getPosts();
return (
<ul>
{posts.map((post) => (
<li key={post.id}>{post.title}</li>
))}
</ul>
);
}
```
Use this as the baseline approach for content pages, dashboards, and route-level data requirements.
## Parallel Data Fetching
Fetch multiple independent resources in parallel to reduce total waiting time.
```tsx
async function getDashboardData() {
const [user, posts, analytics] = await Promise.all([
fetch('/api/user').then((r) => r.json()),
fetch('/api/posts').then((r) => r.json()),
fetch('/api/analytics').then((r) => r.json()),
]);
return { user, posts, analytics };
}
export default async function DashboardPage() {
const { user, posts, analytics } = await getDashboardData();
// Render dashboard
}
```
Use this pattern whenever requests do not depend on one another.
## Sequential Data Fetching (When Dependencies Exist)
Fetch sequentially only when a later request requires data from an earlier one.
```tsx
async function getUserPosts(userId: string) {
const user = await fetch(`/api/users/${userId}`).then((r) => r.json());
const posts = await fetch(`/api/users/${userId}/posts`).then((r) => r.json());
return { user, posts };
}
```
Document the dependency explicitly so the slower path is intentional.
## Pattern Selection
Use this checklist when choosing the fetch shape:
- Start with a Server Component when the page can render from server data alone.
- Use `Promise.all()` for unrelated requests.
- Keep sequential requests only for real dependencies.
- Split large pages into smaller async components when separate Suspense boundaries improve UX.
## Example: Dashboard with Parallel Requests
**Input:** Build a dashboard showing user profile, stats, and recent activity.
```tsx
// app/dashboard/page.tsx
async function getDashboardData() {
const [user, stats, activity] = await Promise.all([
fetch('/api/user').then((r) => r.json()),
fetch('/api/stats').then((r) => r.json()),
fetch('/api/activity').then((r) => r.json()),
]);
return { user, stats, activity };
}
export default async function DashboardPage() {
const { user, stats, activity } = await getDashboardData();
return (
<div className="dashboard">
<UserProfile user={user} />
<StatsCards stats={stats} />
<ActivityFeed activity={activity} />
</div>
);
}
```
**Output:** All requests execute concurrently, reducing total load time.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |