router-core/search-params

TanStack Router search params are validated by attaching a schema from Zod, Valibot, ArkType, or a manual function to route definitions via validateSearch. This enforces typed, safe access and produces strongly-typed route params for navigation.

Search params inheritance automatically merges validated URL state from parent routes to child routes. You can control this behavior using retainSearchParams and stripSearchParams middlewares to keep UI state consistent across nested views.

Yes, you can use Valibot or ArkType instead of Zod for TanStack Router search params validation. The system supports multiple validators including Zod, Valibot, ArkType, and manual custom validators to produce strongly-typed route params.

The best way to share paging or currency params across nested shop routes is leveraging search params inheritance. By validating these params on a parent route, children automatically inherit the state, ensuring consistent UI behavior and typed access.

You prevent unnecessary data fetching by using loaderDeps to limit re-fetches. By defining specific dependencies, the router only triggers loaders when the relevant validated search params change, optimizing navigation behavior.

You handle custom serialization by applying custom parse and stringify options on a per-route basis. This allows you to manage how validated URL state is converted to and from the JSON-like search params structure.