foxlau/react-router-better-auth / .agents/skills/react-router-framework-mode
react-router-framework-mode
VerifiedBuild full-stack React applications using React Router's framework mode. Use when configuring routes, working with loaders and actions, handling forms, handling navigation, pending/optimistic UI, error boundaries, or working with react-router.config.ts or other react router conventions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.5 KB |
| references/actions.md | markdown | 8.9 KB |
| references/data-loading.md | markdown | 3.8 KB |
| references/error-handling.md | markdown | 4.5 KB |
| references/middleware.md | markdown | 6.6 KB |
| references/navigation.md | markdown | 4.1 KB |
| references/pending-ui.md | markdown | 6.8 KB |
| references/rendering-strategies.md | markdown | 3.8 KB |
| references/route-modules.md | markdown | 8.5 KB |
| references/routing.md | markdown | 6.0 KB |
| references/sessions.md | markdown | 10.2 KB |
| references/special-files.md | markdown | 12.2 KB |
| references/type-safety.md | markdown | 4.1 KB |
references/error-handling.md
View on GitHub---
title: Error Handling
description: ErrorBoundary, error responses, isRouteErrorResponse, error reporting
tags: [errors, ErrorBoundary, useRouteError, isRouteErrorResponse, 404, 500]
---
# Error Handling
React Router catches errors in loaders, actions, and rendering, then displays them in error boundaries.
## ErrorBoundary Export
Export an `ErrorBoundary` from any route module:
```tsx
import { isRouteErrorResponse, useRouteError } from "react-router";
export function ErrorBoundary() {
const error = useRouteError();
if (isRouteErrorResponse(error)) {
return (
<div>
<h1>
{error.status} {error.statusText}
</h1>
<p>{error.data}</p>
</div>
);
}
if (error instanceof Error) {
return (
<div>
<h1>Error</h1>
<p>{error.message}</p>
{process.env.NODE_ENV === "development" && <pre>{error.stack}</pre>}
</div>
);
}
return <h1>Unknown Error</h1>;
}
```
## Throwing Responses
Throw Response objects for expected errors:
```tsx
export async function loader({ params }: Route.LoaderArgs) {
const product = await db.getProduct(params.id);
if (!product) {
throw new Response("Product not found", { status: 404 });
}
return product;
}
```
Use the `data` helper for structured error data:
```tsx
import { data } from "react-router";
export async function loader({ params }: Route.LoaderArgs) {
const product = await db.getProduct(params.id);
if (!product) {
throw data(
{ message: "Product not found", productId: params.id },
{ status: 404 },
);
}
return product;
}
```
## isRouteErrorResponse
Check if an error is a Response thrown from a loader/action:
```tsx
import { isRouteErrorResponse, useRouteError } from "react-router";
export function ErrorBoundary() {
const error = useRouteError();
if (isRouteErrorResponse(error)) {
// This was a Response thrown intentionally
// error.status, error.statusText, error.data are available
return <NotFoundPage />;
}
// This was an unexpected error
return <GenericErrorPage />;
}
```
## Error Bubbling
Errors bubble up to the nearest ErrorBoundary:
```
root.tsx (has ErrorBoundary)
└── products.tsx (no ErrorBoundary)
└── product.$id.tsx (has ErrorBoundary)
```
- Error in `product.$id.tsx` → caught by `product.$id.tsx`
- Error in `products.tsx` → caught by `root.tsx`
## Root Error Boundary
Always define an ErrorBoundary in your root route as a last resort:
```tsx
// app/root.tsx
export function ErrorBoundary() {
const error = useRouteError();
return (
<html>
<head>
<title>Oops!</title>
</head>
<body>
<h1>Something went wrong</h1>
{isRouteErrorResponse(error) ? (
<p>
{error.status}: {error.data}
</p>
) : (
<p>An unexpected error occurred</p>
)}
</body>
</html>
);
}
```
## Error Reporting
Report errors to a logging service in `entry.server.tsx`:
```tsx
// app/entry.server.tsx
import type { HandleErrorFunction } from "react-router";
export const handleError: HandleErrorFunction = (error, { request }) => {
// Don't log aborted requests
if (request.signal.aborted) {
return;
}
// Report to your error tracking service
reportErrorToService(error);
// Always log for debugging
console.error(error);
};
```
Reveal the server entry if it doesn't exist:
```shellscript
npx react-router reveal entry.server
```
## Validation Errors (Not Error Boundaries)
For form validation, return errors from the action instead of throwing:
```tsx
import { data } from "react-router";
export async function action({ request }: Route.ActionArgs) {
const formData = await request.formData();
const email = formData.get("email")?.toString() ?? "";
if (!email.includes("@")) {
return data({ errors: { email: "Invalid email" } }, { status: 400 });
}
// Success
await createUser({ email });
return redirect("/welcome");
}
```
Access in component via `fetcher.data`:
```tsx
function SignupForm() {
const fetcher = useFetcher();
const errors = fetcher.data?.errors;
return (
<fetcher.Form method="post">
<input type="email" name="email" />
{errors?.email && <span className="error">{errors.email}</span>}
<button>Sign Up</button>
</fetcher.Form>
);
}
```
## Production vs Development
In production, error messages are sanitized to prevent leaking sensitive info. Full error details are only shown in development.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |