Report incompatible parallel route slots (#97430)
With strict route matching a layout can have sibling slots whose pages
can never form a complete route. For example:
```
app/
layout.tsx
@left/
foo/
page.tsx
@right/
bar/
page.tsx
```
`/foo` is always missing `@right`, and `/bar` is always missing `@left`.
The pages were authored as route targets, but neither URL can construct
the complete slot tree owned by `app/layout.tsx`. Catchall pruning
removes broad matchers that cannot render and the unmatched-page
validation reports dangling files, but neither explains this
project-level mistake.
This validates the finalized ordinary matcher set and reports each
incomplete URL at the layout that owns the conflicting slots. Adding the
corresponding pages or an explicit `default.tsx` makes the topology
valid. Framework-owned defaults do not invent a `children` slot, and
interception matchers remain exempt because they intentionally describe
partial router state updates.
<!-- NEXT_JS_LLM -->
Showing
This diff is collapsed.
This diff is collapsed.
Please
register
or
sign in
to comment