Confusing useRouteContext behavior within an errorComponent

[JakeHaitsma]

I'm trying to understand the expected behavior of useRouteContext within an errorComponent.

I'm loading current user information in my __root route's beforeLoad, and I'd like to display some of that user information in error components throughout my application.

When a descendant route's beforeLoad throws an error, the errorComponent for that route can call useRouteContext(), but some of the parent context properties are undefined, even though the parent's beforeLoad completed successfully. Interestingly, context provided via the React <RouterProvider context={...}> is accessible.

Here's an example StackBlitz to demonstrate what I'm talking about: https://stackblitz.com/edit/github-4kchyyu8?file=src%2Froutes%2Findex.tsx (note also that when a module is hot replaced on edit, both the RouterProvider context property and the __root context property are available, but I'm less interested in digging into this because that's not something that will happen in production).

Questions:

• Is this the intended behavior? Should error components only have access to context from RouterProvider but not from ancestor route loaders?
• If parent route context should be available, is there a specific pattern I should follow to access it in error components?
• Are there any workarounds for sharing data loaded in parent routes with error components?

I'm guessing that using useRouteContext in errorComponent doesn't make sense and this is just user error (at least, the types seem to suggest this). Regardless, I'd appreciate any guidance on the expected behavior and best practices!