router-core/data-loading

Route data loading in TanStack Router is managed by coordinating client-side loaders with parameter-aware caching, using loaderDeps for cache keys and staleTime to balance freshness and performance across nested routes.

Cache keys for dynamic route parameters are set up using loaderDeps, which allows the loader function to derive unique cache entries based on search parameters and dynamic URL segments.

Deferred data loading is supported using Await patterns, allowing non-blocking UX by rendering pending states while secondary route data fetches complete in the background.

Error handling and context sharing across nested routes are handled via beforeLoad functions and router.invalidate, providing robust recovery mechanisms and injecting contextual data into downstream loaders.

Preloading and SWR-like caching are supported by configuring staleTime and gcTime, ensuring route data remains fresh while optimizing performance through background revalidation and garbage collection.

Duplicate fetches occur when loaderDeps are not configured to track specific search parameters, causing cache misses; defining explicit loaderDeps ensures proper cache key generation for parameter-aware data loading.