EXAMPLES

Server components in Next.js 16 let you fetch data and render on the server, reducing client-side JavaScript. Use the App Router, mark components with 'use server' or leave them as server-default, and pass fetched data as props to client components that handle interactivity.

API routes handle REST-like requests in the app/api directory; server actions handle form submissions and mutations from client components. Server actions are simpler for client-server communication, while API routes work for external integrations and webhook handling.

Yes. Next.js 16 supports strict TypeScript configuration alongside Server Components and Tailwind CSS v4. Configure tsconfig.json with strict: true, install Tailwind v4, and use it in server and client components for type-safe styling.

Install Prisma, define your schema, and instantiate a PrismaClient. Use it in server components or server actions to query and mutate data; server actions automatically serialize responses for client consumption without manual API endpoints.

Docker and mise are optional but recommended for production and team consistency. Docker packages your Next.js app for deployment; mise manages Node.js and tool versions in mise.toml to ensure reproducible local environments.

Vitest runs unit and integration tests for server and client logic. Docker enables containerized deployments; Next.js 16 generates optimized production builds with server component prerendering and API route bundling for fast edge or Node.js runtimes.