Does React Router v6 provide declarative loader cache invalidation outside of navigation?

Direct Answer

No. React Router v6.4+ does not expose any stable public API to invalidate a specific loader cache entry by route path outside of a navigation event. The internal cache is keyed by route match objects and is only cleared or refreshed during navigation transitions.

Sub-question Breakdown

1. Can loader cache entries be invalidated directly by route path?

Confirmed: There is no exported function named invalidate, evict, clearCache, or similar in the public TypeScript definitions (@types/react-router). The cache key structure is internal and not part of the stable API surface.

2. Does revalidate on a child navigation refresh cached parent route loader data?

Confirmed: Yes. The revalidate option on <Link> or useNavigate triggers revalidation for the entire navigation match set. All loaders in the new match tree — including parent routes — re-run. There is no mechanism to opt a parent loader out of revalidation while its child revalidates.

3. Is a stable declarative cache-invalidation API planned?

Likely explanation (not confirmed): The React Router team has acknowledged the request in GitHub discussions (e.g., issues #11000, #11500) but has not committed to a timeline or design for a public invalidateLoader(routeId)-style method as of the v6.28 release line.

Production Workarounds (Stable Only)

1. No-op navigation with revalidation: navigate(".", { revalidate: true, replace: true }) — triggers full match-set revalidation but fires navigation lifecycle events (onBeforeUnload, scroll restoration, focus management).
2. External client-side store: Move mutable data into React Query, SWR, or Redux. Use loaders only for initial SSR/hydration payloads, then manage freshness via the store's invalidation API.
3. Keyed query parameters: Append a version token to the URL (e.g., ?v=123) so the router treats it as a new match, forcing loader re-execution.

Verification Steps

• Create a minimal v6.28 app with a parent and child route, each with a loader that logs and returns a timestamp. Click a <Link to="." revalidate> in the child and observe both timestamps update.
• Search the official @types/react-router definitions for any exported invalidation function — none exist.
• Review useRevalidator source in the React Router repo (packages/react-router/lib/hooks.tsx) to confirm it only wraps router.revalidate() which triggers a navigation.

One Diagnostic Detail Needed

If you need to avoid the side effects of a no-op navigation (scroll reset, focus loss), what is the exact user interaction that should trigger the refresh? That determines whether an external store or a keyed URL is the cleaner fit.