Notre avis
Ce fournit des schémas d'ingénierie pour intégrer l'authentification Clerk dans les applications React Router v7, couvrant les loaders, le middleware, les routes protégées, les données utilisateur SSR et le changement d'organisation.
Points forts
- Modèle mental clair du pipeline middleware-loader.
- Tableaux de référence concis pour les tâches courantes.
- Pièges et correctifs pratiques avec des exemples de code.
- Exemples de code pour loaders, actions et composants clients.
Limites
- Nécessite React Router v7.9+ et Clerk React Router v3+.
- Se concentre sur les modèles spécifiques à Clerk, pas sur l'authentification générale.
- Ne couvre pas les flux avancés comme les webhooks ou la multi-tenantité avancée.
Lorsque vous implémentez l'authentification Clerk dans une application React Router v7 et que vous avez besoin de conseils sur les loaders, le middleware et les routes protégées.
Lorsque vous utilisez un autre fournisseur d'authentification ou une version de React Router qui ne prend pas en charge le pipeline middleware/loader.
Analyse de sécurité
SûrThe skill provides documentation and code examples for Clerk authentication with React Router. It uses only the WebFetch tool, no destructive or exfiltrating actions, and contains no sensitive data.
Aucun point d'attention détecté
Exemples
I'm building a React Router v7 app and want to add Clerk authentication. Show me how to set up rootAuthLoader, clerkMiddleware, and protect my routes.How do I use getAuth in a React Router loader to protect a dashboard route and redirect unauthenticated users to /sign-in?I need to implement organization switching in my React Router app using Clerk. How should I set up the OrganizationSwitcher and my loaders to handle org-scoped data?name: clerk-react-router-patterns description: 'React Router v7 patterns with Clerk — rootAuthLoader, getAuth in loaders, clerkMiddleware, protected routes, SSR user data, org switching. Triggers on: react-router auth, rootAuthLoader, getAuth loader, react-router protected route, loader authentication, SSR auth react-router.' license: MIT allowed-tools: WebFetch metadata: author: clerk version: 1.0.0
React Router Patterns
SDK: @clerk/react-router v3+. Requires React Router v7.9+.
What Do You Need?
| Task | Reference | |------|-----------| | Auth in loaders and actions | references/loaders-actions.md | | Protected routes and redirects | references/protected-routes.md | | SSR user data and session | references/ssr-auth.md |
Mental Model
React Router v7 uses a middleware + loader pipeline. Clerk plugs into both layers:
- Middleware (
clerkMiddleware()) — runs on every request, attaches auth to context rootAuthLoader— required inroot.tsxto pass Clerk state to the clientgetAuth(args)— called inside any loader/action to get the current user
Request → clerkMiddleware() → rootAuthLoader → page loader → component
↓ ↓ ↓
attaches auth injects state getAuth(args)
to context to response reads context
Minimal Setup
1. root.tsx
import { rootAuthLoader } from '@clerk/react-router/server'
import { ClerkApp } from '@clerk/react-router'
import type { Route } from './+types/root'
export async function loader(args: Route.LoaderArgs) {
return rootAuthLoader(args)
}
export default ClerkApp(function App() {
return <Outlet />
})
2. Middleware (root route or entry.server.ts)
import { clerkMiddleware } from '@clerk/react-router/server'
export const middleware = [clerkMiddleware()]
Required:
rootAuthLoadermust be called inroot.tsx's loader. Without it,getAuththrows in nested loaders.
Auth in Loaders
import { getAuth } from '@clerk/react-router/server'
import type { Route } from './+types/dashboard'
export async function loader(args: Route.LoaderArgs) {
const { userId } = await getAuth(args)
if (!userId) throw redirect('/sign-in')
const data = await fetchUserData(userId)
return { data }
}
Auth in Actions
import { getAuth } from '@clerk/react-router/server'
export async function action(args: Route.ActionArgs) {
const { userId, orgId } = await getAuth(args)
if (!userId) throw new Response('Unauthorized', { status: 401 })
const formData = await args.request.formData()
await saveData(userId, orgId, formData)
return redirect('/dashboard')
}
Client Components
import { useAuth, useUser } from '@clerk/react-router'
export function Profile() {
const { userId, isSignedIn } = useAuth()
const { user } = useUser()
if (!isSignedIn) return null
return <p>{user?.firstName}</p>
}
Org Switching
import { OrganizationSwitcher } from '@clerk/react-router'
export function Nav() {
return <OrganizationSwitcher afterSelectOrganizationUrl="/dashboard" />
}
export async function loader(args: Route.LoaderArgs) {
const { userId, orgId } = await getAuth(args)
if (!userId) throw redirect('/sign-in')
if (!orgId) throw redirect('/select-org')
return { data: await fetchOrgData(orgId) }
}
Common Pitfalls
| Symptom | Cause | Fix |
|---------|-------|-----|
| clerkMiddleware() not detected | Missing middleware | Export middleware = [clerkMiddleware()] from root route |
| getAuth returns empty userId | rootAuthLoader not called | Call rootAuthLoader(args) in root.tsx loader |
| Infinite redirect loop | Redirect target is also protected | Exclude /sign-in from protection check |
| redirect not working in action | Using Response instead of throw redirect() | Use throw redirect('/path') from react-router |
Import Map
| What | Import From |
|------|-------------|
| getAuth | @clerk/react-router/server |
| rootAuthLoader | @clerk/react-router/server |
| clerkMiddleware | @clerk/react-router/server |
| ClerkApp | @clerk/react-router |
| useAuth, useUser | @clerk/react-router |
| OrganizationSwitcher | @clerk/react-router |
See Also
clerk-setup- Initial Clerk installclerk-custom-ui- Custom flows & appearanceclerk-orgs- B2B organizations
Docs
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.