HighFile-scopeJavaScript / TypeScript Plug & play

Revalidate after mutations to keep UI cache coherent

After server-side mutations, call revalidatePath or revalidateTag to refresh cached RSC data.

Why this matters

Prevents stale UI after POST/PUT/DELETE.

Bad vs. good

Side-by-side examples engineers can pattern-match during review.

Avoid

export async function POST(){ await db.post.create(...); return NextResponse.json({ ok:true }) }

Prefer

import { revalidatePath, revalidateTag } from 'next/cache'
export async function POST(){ await db.post.create(...); revalidateTag('posts'); revalidatePath('/posts'); return NextResponse.json({ ok:true }) }

More snippets

Bad

Mutation without revalidate*

Good

revalidateTag('posts') after create/delete

Related rules

From the same buckets as this rule.

High
Keep 'use client' at the leaf: default to Server Components
Prefer Server Components for pages/layouts and move interactivity to small leaf Client Components. Only add 'use client' where browser APIs or event handlers are strictly necessary.
stack-nextjsstack-react+2
High
Make fetch caching explicit in Server Components
For dynamic data use { cache: 'no-store' } or file-level dynamic = 'force-dynamic'. For ISR use { next: { revalidate: N, tags: [...] } }.
stack-nextjsstack-react+2
High
Middleware only for light auth/rewrites
Keep middleware fast and side-effect free (no DB writes). Narrow the matcher and skip static assets. Use Route Handlers for heavy logic.
stack-nextjsstack-react+2

Why this matters

Bad vs. good

More snippets

Related rules

Keep 'use client' at the leaf: default to Server Components

Make fetch caching explicit in Server Components

Middleware only for light auth/rewrites

Why this matters

Bad vs. good

More snippets

Related rules

Keep 'use client' at the leaf: default to Server Components

Make fetch caching explicit in Server Components

Middleware only for light auth/rewrites