router-core/not-found-and-errors

Handle not-found pages in TanStack Router by throwing the notFound() function in a route loader and rendering a fallback UI via notFoundComponent, with configurable notFoundMode for global or per-route behavior.

notFound() triggers a dedicated not-found UI through notFoundComponent when a resource is missing, while errorComponent catches unexpected runtime errors and supports recovery via router.invalidate() for retrying failed data fetching.

Yes, you can configure a global not-found fallback for nested route trees in TanStack Router using defaultNotFoundComponent and notFoundMode, or target specific routes with notFound({ routeId }) and rootRouteId.

Display safe data inside a TanStack Router notFoundComponent by ensuring the component only accesses data already resolved by the parent route's loader, satisfying frontmatter metadata requirements for safe data usage.

Yes, TanStack Router supports route masking for not-found scenarios, allowing URL masking to hide internal route paths while rendering a notFoundComponent or errorComponent for the targeted layout.

A per-route errorComponent might not catch errors in TanStack Router layouts if the error boundary is not properly orchestrated across the nested route tree, requiring correct errorComponent placement alongside router.invalidate() for retry logic.