router-core-type-safety

Register your router type once with declare module '@tanstack/react-router' and an interface Register containing router: typeof router. After that, every Link, useNavigate, useSearch, and useParams across the app is fully typed with no further annotations.

Do not annotate them at all; types are inferred from the route definition. Narrow the hook with the from option, such as useSearch({ from: '/posts/$postId' }), so it returns that route's exact search params instead of a union of all routes.

Slow checks usually come from un-narrowed LinkProps unions, missing from narrowing on Link and hooks, or loaders returning large inferred types into the route tree. Use as const satisfies LinkProps, add from, and prefer void-returning loaders with TanStack Query.

No. Imports like useSearchParams from react-router-dom or useRouter from next/navigation are different libraries and will break the build or create conflicting routes. All routing exports must come from @tanstack/react-router.

Use strict:false for shared components rendered across multiple routes, such as a global search bar, where the hook should return a union of all routes' params without runtime errors. Use from when the component belongs to one specific route.