Skip to content

fix : build-time validation for dynamic slug name conflicts in app routes#91629

Open
naaa760 wants to merge 1 commit intovercel:canaryfrom
naaa760:fix/tubr-valid-dyn-conf-leaf-seg
Open

fix : build-time validation for dynamic slug name conflicts in app routes#91629
naaa760 wants to merge 1 commit intovercel:canaryfrom
naaa760:fix/tubr-valid-dyn-conf-leaf-seg

Conversation

@naaa760
Copy link
Contributor

@naaa760 naaa760 commented Mar 19, 2026

What?

  • Fail next build when app routes have mismatched dynamic slug names at the same path depth.

Why?

  • These conflicts currently slip past validateAppPaths, then crash next start at runtime.

How?

  • Run getSortedRoutes(appPaths) inside validateAppPaths and add a unit test for the sibling-slug mismatch case.

Closes NEXT-

Fixes : #91628

@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: 7397ee5

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

1 similar comment
@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: 7397ee5

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Turbopack validateAppPaths misses dynamic slug conflicts when sibling routes have different leaf segments

2 participants