nextjs-developer

Use the native fetch API directly inside an async Server Component 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 and pass it to a form's action attribute. Inside the action, validate the FormData (for example with Zod), perform the mutation, then call revalidatePath or revalidateTag to refresh cached data.

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 Components to the leaves of the component tree.

Yes, export an async generateMetadata function from a dynamic page that fetches the resource and returns title, description, and openGraph fields. Never hardcode title or meta tags directly in JSX.

Yes, set output: 'standalone' in next.config.js to produce a self-contained build, then run it with Node.js, PM2, or a multi-stage Dockerfile. The references include a Dockerfile and docker-compose setup with a database service.

Cached fetches are not refreshed automatically after mutations. Call revalidatePath for the affected route or revalidateTag for fetches tagged with next: { tags: [...] } inside your Server Action after the data change.