feat(router): support optional catch all routes#2043
Merged
brandonroberts merged 7 commits intoanalogjs:betafrom Feb 24, 2026
Merged
feat(router): support optional catch all routes#2043brandonroberts merged 7 commits intoanalogjs:betafrom
brandonroberts merged 7 commits intoanalogjs:betafrom
Conversation
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This allows for next-style optional catch-all routes.
d748b39 to
50eb506
Compare
Contributor
Author
|
apologies for the delay here @brandonroberts. we're looking good in testing! |
brandonroberts
approved these changes
Feb 24, 2026
Member
|
No worries, nice work! |
Contributor
|
This came in right on time Thanks @mhartington @brandonroberts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows for next-style optional catch-all routes.
PR Checklist
Closes # n/a
What is the new behavior?
For a more flexible routing setup, this allows for having a dynamic catch all routing setup, like nextjs provides.
For example, if you wanted to include a
docs/route, but did not want to hard-code every route that could be generated from it, you can use this new[[..slug]].page.tssyntax to support that.There's also an included example project for testing and validation that shows how this feature works in combination with markdown content.
Does this PR introduce a breaking change?
Other information
[optional] What gif best describes this PR or how it makes you feel?