\\d+)` is a named capture group that matches one or more digits\n- `$` asserts the end of the string\n\nThis route will match paths like \"/about/123\" or \"/about/456789\", but not \"/about/abc\".\n\n### Accessing Captured Parameters\n\nWhen a regex route matches, any named capture groups in the regex are passed to the component as props. You can access these in your component like this:\n\n```jsx\nconst AboutDetail = ({ params }) => {\n return About Detail for ID: {params.id}
;\n};\n```\n\n### Example: Numbers-Only Route\n\nHere's an example of a route that only accepts numeric paths:\n\n```jsx\n\\d+)$\" regex element={} />\n\nconst NumberComponent = ({ params }) => {\n return Numeric Route: {params.id}
;\n};\n```\n\nThis route will:\n- Match: \"/123\", \"/456789\"\n- Not match: \"/abc\", \"/123abc\", \"/\"\n\n### Tips for Using Regex Routes\n\n1. Always use the `^` and `$` anchors to match the entire path.\n2. Use named capture groups `(?...)` to extract parameters.\n3. Be careful with greedy quantifiers (`*`, `+`) as they might match more than intended.\n4. Test your regex thoroughly to ensure it matches and captures as expected.\n\n### Performance Considerations\n\nWhile regex routes offer great flexibility, they can be slower than simple string matching for very high traffic applications. Use them judiciously, especially if you have a large number of routes.\n\n## License\n\nMIT","readmeFilename":"README.md"}