create-next-pro-cli 0.1.32 → 0.1.33

package/README.md

@@ -126,6 +126,8 @@ Every page belongs to an explicit route area. Use `--area public` for routes ren
 
 `addpage` creates `layout`, `page`, and `loading` files by default. Available long options are `--layout`, `--page`, `--loading`, `--not-found`, `--error`, `--global-error`, `--route`, `--template`, and `--default`. The historical short forms remain available.
 
+Generated page-level layouts accept only `children` because they do not read route parameters. If a customized Next.js 16 layout needs the locale, make the component asynchronous, type `params` as `Promise<{ locale: string }>` and await it before use. Projects generated with `create-next-pro-cli@0.1.32` may contain the obsolete synchronous `params: { locale: string }` signature: remove that property when it is unused, or migrate it to the asynchronous contract.
+
 `rmpage` only lists routes that contain an actual `page.tsx` in the `(public)` or `(user)` route group. Technical directories remain hidden. Removal is confined to the selected area and project, and it preserves shared parent directories and unrelated files.
 
 ## Generated project architecture

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-next-pro-cli",
-  "version": "0.1.32",
+  "version": "0.1.33",
   "description": "Advanced Next.js project scaffolder with i18n, Tailwind, App Router and more.",
   "repository": {
     "type": "git",

package/templates/Page/layout.tsx

@@ -1,11 +1,5 @@
-import React from "react";
+import type { ReactNode } from "react";
 
-export default function templateLayout({
-  children,
-  params,
-}: {
-  children: React.ReactNode;
-  params: { locale: string };
-}) {
+export default function templateLayout({ children }: { children: ReactNode }) {
   return children;
 }

package/templates/Projects/default/.agents/skills/create-next-pro-addpage/SKILL.md

@@ -47,6 +47,8 @@ For `Account.Security --area user`, expect resources under:
 
 The route area affects only the App Router path and layout. UI and message paths remain area-independent. Public page UI uses its own `<main>` landmark; user page UI uses `<section>` because the user layout already provides `<main>`.
 
+The generated page-level `layout.tsx` accepts only `children` because it does not read route parameters. If you customize it to read the locale under Next.js 16, make the component asynchronous, type `params` as `Promise<{ locale: string }>` and await it before use.
+
 The command creates only missing code files and preserves existing ones as `unchanged`. Repeating the command in the same area is idempotent and can add requested missing route files. Requesting the same logical page in the other area fails with `TARGET_EXISTS`. Flat historical routes or ambiguous route definitions fail with `INCONSISTENT_ROUTE` before any write.
 
 ## Workflow
@@ -87,3 +89,5 @@ bun run check
 ```
 
 Confirm every `created` or `updated` event path exists. A repeated command should preserve existing code and normally report those resources as `unchanged`.
+
+When a generated or customized layout reads route parameters, include `next build` in validation so Next.js checks the inferred `LayoutProps` contract.

package/templates/Projects/default/README.md

@@ -107,6 +107,12 @@ interactive page flows expose the same area-aware catalog. Areas select a route
 layout without changing the public URL; see the linked command skills for the
 complete contract.
 
+Page-level layouts generated by the CLI accept only `children` when they do not
+read route parameters. A customized Next.js 16 layout that reads the locale must
+type `params` as `Promise<{ locale: string }>` and await it. Projects created
+with `create-next-pro-cli@0.1.32` should remove the obsolete synchronous
+`params` property when unused, or migrate it to this asynchronous contract.
+
 ## Template Features
 
 - Next.js 16 App Router