This is the context passed in to your server adapter's getLoadContext() function. It's a way to bridge the gap between the adapter's request/response API with your React Router app. It is only applicable if you are using a custom server adapter.
Dynamic route params for the current route.
Matched un-interpolated route pattern for the current path (i.e., /blog/:slug). Mostly useful as a identifier to aggregate on for logging/tracing/etc.
A Fetch Request instance which you can use to read headers (like cookies, and URLSearchParams from the request.
A URL instance representing the application location being navigated to or fetched.
In Framework mode, this is a normalized URL with React-Router-specific
implementation details removed (.data suffixes, index/_routes search
params). For the raw incoming URL, use request.url.
This normalization preserves standard URL pathname encoding and casing.
For example, a request to /%61dmin.data produces a url.pathname of
/%61dmin. This is not a canonical representation of the matched route.
For authorization, attach server middleware
to the protected route or a common ancestor instead of relying on literal
pathname-prefix comparisons.
Arguments passed to loader functions