What problem does it solve? TanStack Router applications need consistent handling of unmatched URLs, missing resources, and loader errors, but the API surface spans notFound(), notFoundComponent, errorComponent, and route masking with several deprecated patterns and subtle pitfalls. ## Core Features & Use Cases - Not-Found Handling: Configure global 404 pages via notFoundComponent on the root route, router-wide defaults, and per-route notFound() throws for missing resources like a post that does not exist. - Error Boundaries: Attach errorComponent per route or router-wide, with retry logic driven by router.invalidate() to re-run loaders and reset the boundary. - Route Masking: Display a different browser URL than the rendered route using the mask option on Link, useNavigate, or declarative createRouteMask definitions. - Use Case: When building a photo gallery, throw notFound() in a loader for missing photos, render a contextual 404 via notFoundComponent, and mask the modal route so the URL shows /photos/$photoId while rendering the modal. ## Quick Start Ask the assistant to add a global 404 page and per-route error boundaries with retry buttons to your TanStack Router routes.