sdcorejs-review-code-nextjs

To review Next.js code for convention violations before merging, audit pages, components, and API routes for server/client boundaries, next/image usage, generateMetadata coverage, and typed i18n Link implementation. This identifies line-level issues early to maintain build-website conventions and avoid broken pages.

Ensuring hydration-safe rendering in a Next.js application requires validating component rendering patterns against correctness guardrails during per-file audits. This process prevents runtime mismatches and surprises during client-side hydration.

Yes, this Next.js code review covers internationalization by validating typed locale-aware Link components and explicit locale context setup. It targets i18n-enabled navigation to ensure landing-site code correctly handles locale requirements.

To check for unsafe dynamic HTML rendering in Next.js components, scan for dangerouslySetInnerHTML usage applied to user content. This security check flags unsafe patterns during per-file audits to prevent potential vulnerabilities.

During a pre-merge review, enforce explicit caching setup alongside Next.js conventions for pages and API routes. This ensures codebase adherence to build-website standards and prevents runtime surprises related to data fetching.

Code review findings for Next.js convention issues are structured as Critical, Important, or Minor categories. Each includes actionable file:line references for fast fixes, ensuring consistent review outcomes across pages, components, and API routes.