nextjs-app-router

Next.js 16 App Router projects in a monorepo should reserve the app/ directory strictly for routing files like page.tsx, placing business logic in features/core/services to streamline routing and enforce clear component boundaries across apps/web.

In Next.js 16, server components handle data fetching, server actions, and metadata configuration, while client components manage interactivity. Clear guidance enforces these boundaries to maintain consistent component structure across apps/web.

Configure next.config.ts in a Turborepo by enabling typedRoutes and specifying package transpilation settings, which ensures proper package transpilation and enables typed routing within your Next.js 16 App Router architecture.

The best way to create a new app page is to add a page.tsx file under apps/web/app/(site)/. Following this routing-first convention ensures your Next.js 16 App Router structure remains consistent and properly separated from business logic.

Yes, Next.js 16 App Router conventions require YAML frontmatter containing name and description fields. Meeting this technical requirement ensures your app structure, server actions, and environment setup align with the standardized monorepo conventions.