nextjs

Next.js server components fetch data directly on the server using async/await syntax. This approach leverages server-side rendering strategies like SSR and SSG to fetch dynamic content securely without client-side JavaScript overhead.

SSG pre-renders pages at build time, ISR allows static regeneration incrementally, and SSR renders pages per request. Next.js App Router supports these rendering techniques alongside streaming to optimize dynamic content delivery and performance.

Yes, Next.js middleware intercepts incoming requests to handle authentication checks and execute redirects. It runs before a request completes, allowing you to control access and modify routing behavior based on user session or token states.

Next.js provides built-in components for image and font optimization to automatically resize, serve modern formats, and reduce layout shifts. Metadata APIs manage SEO tags, ensuring proper search engine indexing and optimal page performance.

Common Next.js anti-patterns include overusing client components instead of server components, improper environment variable management, and ignoring streaming benefits. Avoiding these ensures scalable, production-ready applications with optimal rendering and caching.

Parallel routes render multiple pages simultaneously within a single layout using named slots. Intercepting routes load a route within the current context, enabling complex interfaces like modal previews while maintaining the underlying URL structure.