Skip to main content

Next.js

13 articles · written by Niraj Kumar

Next.js changed shape with the App Router, and a lot of advice written for the Pages Router is now actively wrong. These articles are written against the current model: Server Components by default, Server Actions for mutations, and caching you have to reason about explicitly rather than inherit.

Coverage includes what actually changed in Next.js 16 and what is worth adopting, streaming AI responses through the App Router with Server Actions, performance work for AI-heavy SaaS pages, React Server Component patterns, securing Next.js applications, CI/CD pipelines with GitHub Actions, and accessible form patterns with shadcn/ui.

Where a post touches retrieval or agents, it uses Next.js as the application layer rather than treating it as the subject.

Need this built rather than explained?

Next.js 15/16 App Router apps with TypeScript, Server Actions, and Vercel/AWS deploys.

Next.js Developer Services

Related topics

← All articles