An error for an HTTP request.

Gets environmental variables. In the browser, only environmental variables shared with it by the server will be accessible.

Used to determine if the code is running in the browser.

Used to determine if the code is running in the development environment.

Used to determine if the code is running in the production environment.

Used to determine if the code is running on the server.

Used to determine if the code is running in the test environment.

Any errors within the boundary will be captured by it. Unlike ErrorBoundary, the AppErrorBoundary can be used to render errors on the server. For the error on the server to be caught by it, it must have the same boundary.

Creates a context object for the App. State stored within the AppContext will be serialized and shared with the browser.

A simple error fallback that will show the error and provide a button for trying again. The error will clear when clicking the try again button or navigating to a different route.

Used to hydrate the app in the browser. Hydration isn't required if you want to do server side rendering only. This function will turn the application into an SPA.

Checks if the value as an HttpError.

For internal use only. This is used in the generated _main.tsx file for routes to automatically add error boundaries to routes that have a FallbackComponent.

This component can be used to throw a 404 not found error. It's used as the default wildcard route at the top level of your app.

Wraps a component with an AppErrorBoundary. Any errors within the boundary will be captured by it. Unlike withErrorBoundary, withAppErrorBoundary can be used to render errors on the server. For the error on the server to be caught by it, it must have the same boundary.

Options for initializing an HttpError.

A file containing the react component for a route. Optionally, it can export an ErrorFallback that will be used for an AppErrorBoundary on the component.