Reviewing files that changed from the base of the PR and between2a91221 and70ccf27.

• pnpm-lock.yaml is excluded by!**/pnpm-lock.yaml,!pnpm-lock.yaml

• docs/2.directory-structure/1.app/1.layouts.md (2 hunks)
• packages/nuxt/src/app/components/nuxt-layout.ts (1 hunks)
• packages/nuxt/src/app/composables/router.ts (3 hunks)
• packages/nuxt/src/app/index.ts (1 hunks)
• packages/nuxt/src/app/plugins/router.ts (1 hunks)
• packages/nuxt/src/app/types.ts (1 hunks)
• packages/nuxt/src/pages/module.ts (2 hunks)
• packages/nuxt/src/pages/runtime/composables.ts (2 hunks)
• packages/nuxt/src/pages/runtime/index.ts (1 hunks)
• test/basic.test.ts (1 hunks)
• test/bundle.test.ts (1 hunks)
• test/fixtures/basic-types/app/app-types.ts (1 hunks)
• test/fixtures/basic-types/app/layouts/with-props.vue (1 hunks)
• test/fixtures/basic/app/layouts/custom.vue (1 hunks)
• test/fixtures/basic/app/middleware/sets-layout.ts (1 hunks)

• GitHub Check: test-fixtures (windows-latest, built, vite-env-api, default, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (windows-latest, dev, vite, default, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, built, rspack, async, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, built, vite-env-api, default, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, built, webpack, async, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-on, js, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, built, rspack, default, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, built, vite, default, manifest-off, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, dev, vite-env-api, async, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, dev, vite, default, manifest-on, json, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-on, js, lts/-1)
• GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-off, json, lts/-1)
• GitHub Check: release-pkg-pr-new
• GitHub Check: test-benchmark
• GitHub Check: test-size
• GitHub Check: typecheck (windows-latest, bundler)
• GitHub Check: typecheck (ubuntu-latest, bundler)
• GitHub Check: code

test/bundle.test.ts (1)

98-98:LGTM! Expected bundle size increase.

The 1 KB increase in the server bundle size is minimal and expected given the addition of layoutProps functionality.

test/fixtures/basic-types/app/app-types.ts (1)

302-311:LGTM! Comprehensive type-checking coverage.

The test cases effectively verify thatsetPageLayout recognises named layouts and their associated props, including both valid usage patterns and expected type errors for invalid layouts and incorrect prop types.

test/basic.test.ts (1)

1408-1408:LGTM! Good integration test coverage.

The assertion verifies end-to-end functionality by confirming that middleware-provided layout props render correctly in the DOM, complementing the changes in the middleware fixture.

test/fixtures/basic/app/middleware/sets-layout.ts (1)

3-5:LGTM! Clear demonstration of the new API.

The middleware demonstrates the newsetPageLayout signature with layout props, which is then verified in the integration tests to ensure the props propagate correctly to the layout component.

packages/nuxt/src/pages/runtime/index.ts (1)

2-2:LGTM! Appropriate public API expansion.

AddingNuxtLayouts to the public type exports enables users to access layout typing, which is necessary for the type-safe layout props feature.

packages/nuxt/src/app/plugins/router.ts (1)

241-247:LGTM! Correct hydration flow for layout props.

The implementation properly handles layoutProps during hydration by:

1. ReadinginitialLayoutProps from the server payload (line 241)
2. Restoring it toto.meta.layoutProps during hydration (line 247)

This ensures layout props set on the server are correctly transferred to the client and preserved during the initial navigation.

packages/nuxt/src/app/components/nuxt-layout.ts (1)

99-99:LGTM! Props merging enables route-driven layout props.

TheLayoutProvider now merges three sources of props:

1. context.attrs (component-level props)
2. route.meta.layoutProps (route/middleware-driven props)
3. { ref: layoutRef } (internal ref)

This merge order allows route-driven props fromsetPageLayout to override component-level props, which aligns with the feature's intended behaviour.

packages/nuxt/src/app/types.ts (1)

3-3:LGTM! Consistent public API expansion.

AddingNuxtLayouts to the type exports maintains consistency with the public API surface expansion seen inpackages/nuxt/src/pages/runtime/index.ts and enables users to access layout typing.

test/fixtures/basic/app/layouts/custom.vue (1)

15-15:LGTM! Layout props integration looks good.

The optionalfoo prop is correctly defined and rendered, demonstrating the new layout props feature effectively. The implementation follows Vue composition API best practices.

Also applies to: 22-24

packages/nuxt/src/app/index.ts (1)

14-14:LGTM! Public API surface appropriately extended.

The export ofNuxtLayouts correctly expands the public type surface to support the new layout props feature.

packages/nuxt/src/pages/runtime/composables.ts (2)

9-13:LGTM! Empty interface is intentional for module augmentation.

The emptyNuxtLayouts interface is designed to be augmented at build time with layout-specific typings. This is a standard pattern for runtime-extended types in Nuxt.

Note: The Biome static analysis warning can be safely ignored—this is not a code smell but an intentional design pattern for TypeScript module augmentation.

---

56-62:LGTM! Router meta augmentation correctly preserves inheritance.

TheRouteMeta augmentation properly extendsUnwrapRef<PageMeta> whilst adding the internallayoutProps field. The@internal annotation appropriately indicates this is not part of the public API.

test/fixtures/basic-types/app/layouts/with-props.vue (1)

1-11:LGTM! Clean test fixture for layout props.

The component correctly demonstrates typed layout props with a requiredaProp parameter. The implementation follows Vue composition API best practices with<script setup lang="ts">.

packages/nuxt/src/app/composables/router.ts (1)

269-299:LGTM! Layout props propagation is well-structured across all contexts.

The enhancedsetPageLayout correctly:

• Uses generics to provide type-safe props based on the layout name
• PropagateslayoutProps through server payload (line 281), middleware (line 290), and client route meta (line 297)
• Guards theuseRoute() call (line 295) with!inMiddleware to avoid the warnings mentioned in lines 22-26
• Maintains backwards compatibility with the optionalprops parameter

The conditional type signature elegantly handles both typed layouts (whenNuxtLayouts is augmented) and fallback tostring when no layouts are defined.

packages/nuxt/src/pages/module.ts (1)

5-5:LGTM! Layout typings generation is well-implemented.

The code correctly:

• ImportsgenSafeVariableName to ensure valid variable names for layout components
• Generates imports for all layout files with safe identifiers
• Builds theNuxtLayouts interface mapping each layout name toInstanceType<typeof Layout>['$props'], which properly extracts Vue component prop types
• UpdatesLayoutKey to derive fromNuxtLayouts with a string fallback when no layouts exist

The generated typings will provide excellent IntelliSense and type safety forsetPageLayout calls.

Also applies to: 622-643