router-core/search-params

To validate TanStack Router search params, define a validateSearch contract using a schema from Zod, Valibot, ArkType, or a custom parse function. This enforces param shapes and provides strongly typed runtime values accessible via Route.useSearch().

Search-param inheritance allows child routes to access and inherit validated search params from parent routes. By defining validateSearch on parent routes, children automatically receive the typed values, ensuring consistent behavior and type-safe access across the nested route hierarchy.

The best way to scope re-validation for dynamic query parameters is using loaderDeps. This feature selects specific search params needed by a loader, ensuring that route data only re-fetches or re-validates when those particular parameters change, improving performance.

Yes, you can use custom serialization to parse and stringify URL search params. This skill supports custom parse and stringify logic alongside middlewares like retain or strip, allowing you to maintain URL hygiene and control how query parameters are serialized and deserialized.

You can access typed search params in code-split components using Route.useSearch(). This hook provides strongly typed values directly from the validated search params without requiring extra annotations, ensuring type safety across routes and dynamically loaded components.