migrate-react-router

Work route-by-route, bottom-up: replace the Vite plugin with rango(), convert route configs to the urls() DSL, merge loaders into server component handlers, and convert actions to "use server" functions. Finish by running npx rango generate and verifying no react-router imports remain.

Merge each loader into its route's server component handler, which fetches data and renders directly. Convert route actions to "use server" functions called from native forms or useActionState. Use createLoader() only when you need live client-side data or shared loaders across segments.

Yes, the migration covers React Router v7 framework mode (file-based route modules), v7 library mode, v6, and Remix v2. Framework-mode route module exports like loader, action, meta, and ErrorBoundary each map to a specific Rango handler or DSL construct.

useNavigate becomes useRouter() from @rangojs/router/client with push, replace, and back methods. useLoaderData has no direct equivalent; handlers fetch and render directly, while client components use useLoader() with a registered createLoader() for live data.

No. The guide explicitly forbids mock react-router modules, Vite aliases, or compatibility wrappers because they freeze old semantics and hide unsupported behavior. Replace every react-router or @remix-run import at its call site and remove the packages from package.json.

Use clientUrls() for route groups whose components are irreducibly hook-heavy client components, or high-navigation-speed surfaces like dashboards. It preserves the React Router route-module shape almost 1:1, including browser-run revalidate predicates, and can be re-migrated to server handlers later.