Back to stack guides
nextjs-app-router
Next.js App Router
Use Server Components by default, narrow client boundaries, framework routing and metadata, and explicit static-generation contracts.
Stack guidesContextual
Intent
Keep UI implementations aligned with current Next.js architecture while avoiding hydration, rendering, and deployment mistakes.
Checks
- Keep interactive Client Components small and pass serializable data into them.
- Use framework layouts, links, metadata, loading, error, and not-found conventions.
- For static export, generate every dynamic path and avoid unsupported server features.
Warnings
- Do not access browser globals during server rendering or add client boundaries to entire route trees without need.
Exceptions
- A heavily interactive editor may justify a larger client-owned island with explicit boundaries.