router-core/type-safety

Register your router type once with `declare module "@tanstack/react-router" { interface Register { router: typeof router } }` after calling createRouter. After registration, every Link, useNavigate, useSearch, and useParams across the app is fully typed automatically.

Do not add any type annotations or generics — the values are already inferred from the route definition. Narrow the hook with the `from` option, such as `useSearch({ from: "/posts/$postId" })`, to get that route's exact search param types.

Slow checks usually come from un-narrowed LinkProps unions, missing `from` on Link and hooks, or tuple-syntax addChildren in large route trees. Use `as const satisfies LinkProps`, narrow with `from`, and prefer object-syntax addChildren.

Yes, pass `strict: false` instead of `from`, for example `useSearch({ strict: false })`. This returns a union of all routes' search params without throwing a runtime error when the current route does not match.

Use `getRouteApi("/posts")` instead of importing the Route object, which avoids pulling route config into the lazy chunk. The returned routeApi exposes typed useLoaderData, useSearch, and other hooks.

No, TanStack Router has its own APIs and does not support getServerSideProps, Remix-style loaders, or React Router's useSearchParams. It uses createFileRoute with loader, validateSearch, and hooks like Route.useSearch.