nextjs-developer

Use the native fetch API directly inside async Server Components with explicit cache options. Pass cache: 'force-cache' for static data, cache: 'no-store' for fresh data, or next: { revalidate: 60 } for ISR-style periodic revalidation.

Define an async function with the 'use server' directive, then pass it to a form's action attribute. Validate input with Zod, perform the mutation, and call revalidatePath to refresh cached data after the change.

Add 'use client' only when a component needs interactivity such as event handlers, useState, useEffect, or browser APIs. Keep components as Server Components by default and push client boundaries to the leaves of the component tree.

Yes, use the generateMetadata function or the static metadata export to define titles, descriptions, and OpenGraph tags. Never hardcode title or meta tags directly in JSX, as the Metadata API handles deduplication and streaming.

Set output: 'standalone' in next.config.js, then use a multi-stage Dockerfile that installs dependencies, builds the app, and copies the standalone output with static assets. Run it with node server.js on port 3000.

Cached fetches persist until their revalidate window expires or you trigger on-demand revalidation. Call revalidatePath for a specific route or revalidateTag for fetches tagged with next: { tags: [...] } inside a Server Action or route handler.