fix(router): fix issue with top-level catch-all not being matched in server renderer #26861
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
[[...a]]
syntax, which isn't supported in the client router and would require a breaking change to add. This resulted in a forked behavior between client-side routing and server-side routing. This change treats[...a]
as optional catch-alls (matching/
and/a
) to behave the same across routers.Test Plan
app/[...a].tsx
will work in server and static rendering modes.Checklist
npx expo prebuild
& EAS Build (eg: updated a module plugin).