router-core/path-params

To capture dynamic URL segments in TanStack Router, define routes with a leading $ in the path, such as /posts/$postId. You then read these dynamic path parameters within your component using the Route.useParams() hook to drive UI state and navigation.

TanStack Router handles optional parameters and splat routes using specific syntax. Use the _splat keyword for catch-all routing and the {-$param} syntax for optional segments, enabling versatile and strongly-typed dynamic path matching.

To build internationalized routes, apply i18n-aware routing concepts using optional locale path parameters. By leveraging optional params like {-$param}, you can prefix paths with locale segments and parse them to drive localized UI state and navigation.

You access parsed route parameters in a TanStack Router component by calling Route.useParams(). This hook retrieves the dynamic values parsed from URL segments, splats, and optional params, allowing you to use them directly in your UI logic.

Yes, you can use prefix and suffix patterns when defining dynamic route paths in TanStack Router. These patterns work alongside dynamic segments, splats, and optional params to create flexible matching rules across nested and internationalized routes.