
migrate-from-react-router
Step-by-step migration from React Router v7 to TanStack Router: route definition conversion, Link/useNavigate API differences, useSearchParams to validateSearch + useSearch, useParams with from, Outlet replacement, loader conversion, code splitting differences.
- Installs
- 181
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/tanstack/router --skill migrate-from-react-router- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads migrate-from-react-router automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Migrate from React Router v7 to TanStack Router
This is a step-by-step migration checklist. Each check covers one conversion task. Complete them in order.
CRITICAL: If your UI is blank after migration, open the console. Errors like "cannot use useNavigate outside of context" mean React Router imports remain alongside TanStack Router imports. Uninstall
react-router(andreact-router-domif present) to surface them as TypeScript errors.CRITICAL: TanStack Router uses
to+paramsfor navigation, NOT template literal paths. Never interpolate params into thetostring.NOTE: React Router v7 recommends importing from
react-router(notreact-router-dom). Thereact-router-dompackage still exists but just re-exports fromreact-router. Check for imports from both.
Pre-Migration
- Create a migration branch
git checkout -b migrate-to-tanstack-router
- Install TanStack Router alongside React Router temporarily
npm install @tanstack/react-router @tanstack/react-router-devtools
npm install -D @tanstack/router-plugin
- Configure bundler plugin (Vite example)
// vite.config.ts
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import { tanstackRouter } from '@tanstack/router-plugin/vite'
export default defineConfig({
plugins: [
tanstackRouter({ target: 'react', autoCodeSplitting: true }),
react(),
],
})
- Create routes directory
mkdir src/routes
Route Definitions
- Create root route
React Router: <BrowserRouter> or createBrowserRouter([{ element: <Layout />, children: [...] }])
TanStack Router: src/routes/__root.tsx
// src/routes/__root.tsx
import { createRootRoute, Link, Outlet } from '@tanstack/react-router'
import { TanStackRouterDevtools } from '@tanstack/react-router-devtools'
export const Route = createRootRoute({
component: () => (
<>
<nav>
<Link to="/">Home</Link>
<Link to="/about">About</Link>
</nav>
<Outlet />
<TanStackRouterDevtools />
</>
),
})
- Create router instance with type registration
// src/main.tsx
import { StrictMode } from 'react'
import ReactDOM from 'react-dom/client'
import { RouterProvider, createRouter } from '@tanstack/react-router'
import { routeTree } from './routeTree.gen'
const router = createRouter({ routeTree })
declare module '@tanstack/react-router' {
interface Register {
router: typeof router
}
}
const rootElement = document.getElementById('root')!
if (!rootElement.innerHTML) {
ReactDOM.createRoot(rootElement).render(
<StrictMode>
<RouterProvider router={router} />
</StrictMode>,
)
}
- Convert each route file to
createFileRoute
React Router:
// Defined in route config array
{ path: '/posts', element: <Posts />, loader: postsLoader }
TanStack Router:
// src/routes/posts.tsx
import { createFileRoute } from '@tanstack/react-router'
export const Route = createFileRoute('/posts')({
loader: async () => {
const posts = await fetchPosts()
return { posts }
},
component: PostsPage,
})
function PostsPage() {
const { posts } = Route.useLoaderData()
return (
<ul>
{posts.map((p) => (
<li key={p.id}>{p.title}</li>
))}
</ul>
)
}
- Convert dynamic routes
React Router: /posts/:postId (colon syntax)
TanStack Router: /posts/$postId (dollar syntax)
// src/routes/posts/$postId.tsx
import { createFileRoute } from '@tanstack/react-router'
export const Route = createFileRoute('/posts/$postId')({
loader: async ({ params }) => {
const post = await fetchPost(params.postId)
return { post }
},
component: PostPage,
})
function PostPage() {
const { post } = Route.useLoaderData()
return <article>{post.title}</article>
}
Navigation
- Convert all
<Link>components
React Router:
import { Link } from 'react-router'
;<Link to={`/posts/${postId}`}>View Post</Link>
TanStack Router:
import { Link } from '@tanstack/react-router'
;<Link to="/posts/$postId" params={{ postId }}>
View Post
</Link>
Key differences:
-
tois a route path pattern, NOT an interpolated string -
paramsis a separate prop with typed values -
Active styling: use
activeProps={{ className: 'font-bold' }}ordata-status="active"attribute for CSS -
Convert all
useNavigatecalls
React Router:
import { useNavigate } from 'react-router'
const navigate = useNavigate()
navigate(`/posts/${postId}`)
TanStack Router:
import { useNavigate } from '@tanstack/react-router'
const navigate = useNavigate()
navigate({ to: '/posts/$postId', params: { postId } })
Search Params
- Replace
useSearchParamswithvalidateSearch+useSearch
React Router:
import { useSearchParams } from 'react-router'
function Posts() {
const [searchParams, setSearchParams] = useSearchParams()
const page = Number(searchParams.get('page')) || 1
const goToPage = (p: number) => setSearchParams({ page: String(p) })
}
TanStack Router:
// In the route definition:
import { createFileRoute } from '@tanstack/react-router'
import { z } from 'zod'
export const Route = createFileRoute('/posts')({
validateSearch: z.object({
page: z.number().default(1).catch(1),
}),
component: Posts,
})
// In the component:
import { useNavigate } from '@tanstack/react-router'
function Posts() {
const { page } = Route.useSearch()
const navigate = useNavigate({ from: '/posts' })
const goToPage = (p: number) => {
navigate({ search: (prev) => ({ ...prev, page: p }) })
}
}
Key differences:
- Search params are validated and typed at the route level
useSearch()returns typed objects, notURLSearchParams- Update with function form to preserve other params
Path Params
- Update
useParamswithfromproperty
React Router:
import { useParams } from 'react-router'
const { postId } = useParams()
TanStack Router:
import { useParams } from '@tanstack/react-router'
const { postId } = useParams({ from: '/posts/$postId' })
Or from within the route component:
const { postId } = Route.useParams()
useLocation — Common Pitfall
- Replace
useLocationwith specific hooks
React Router's useLocation is heavily used, and TanStack Router has a hook with the same name — but they are NOT equivalent. TanStack Router's useLocation() returns the router's current location, which during pending navigations may differ from what's currently rendered. Most React Router useLocation usage should be replaced with more specific hooks. See #3110.
Replace based on what you actually need:
// React Router
import { useLocation } from 'react-router'
const location = useLocation()
// ❌ DON'T just swap to TanStack Router's useLocation — it's the "live" URL
import { useLocation } from '@tanstack/react-router'
// ✅ DO use the specific hook for what you need:
import {
useMatch,
useMatches,
useParams,
useSearch,
} from '@tanstack/react-router'
// Current route match (replaces most useLocation().pathname usage)
const match = useMatch({ from: '/posts/$postId' })
// All active matches (replaces useLocation for breadcrumbs/analytics)
const matches = useMatches()
// Path params (replaces useLocation + manual parsing)
const { postId } = useParams({ from: '/posts/$postId' })
// Search params (replaces useLocation().search parsing)
const { page } = useSearch({ from: '/posts' })
Outlet
- Replace React Router
Outletwith TanStack RouterOutlet
The API is identical — just change the import:
// Before
import { Outlet } from 'react-router'
// After
import { Outlet } from '@tanstack/react-router'
Loaders
- Convert React Router loaders
React Router (v7):
export async function loader({ params }) {
const post = await fetchPost(params.postId)
return { post }
}
export default function Post() {
const { post } = useLoaderData()
return <div>{post.title}</div>
}
TanStack Router:
export const Route = createFileRoute('/posts/$postId')({
loader: async ({ params }) => {
const post = await fetchPost(params.postId)
return { post }
},
component: Post,
})
function Post() {
const { post } = Route.useLoaderData()
return <div>{post.title}</div>
}
Key differences:
- Loader is a route option, not a separate export
useLoaderData()is called viaRoute.useLoaderData()(oruseLoaderData({ from }))- TanStack Router loaders run on the CLIENT by default (not server-only)
- No
json()wrapper needed — return plain objects
Code Splitting
- Convert lazy route imports — with
autoCodeSplitting: truein the plugin config, this is automatic. For manual splitting, use.lazy.tsxfiles:
// src/routes/lazy-page.lazy.tsx
import { createLazyFileRoute } from '@tanstack/react-router'
export const Route = createLazyFileRoute('/lazy-page')({
component: () => <div>Lazy loaded</div>,
})
Cleanup
- Remove React Router and verify
npm uninstall react-router react-router-dom
grep -r "from 'react-router" src/ # find stale imports
npx tsc --noEmit # verify clean build
- Test all routes — verify rendering, navigation (incl. back/forward), search params, dynamic params, and loaders
Common Mistakes
1. HIGH: Leaving React Router imports alongside TanStack Router
Both libraries export Link, useNavigate, Outlet, etc. Leftover React Router imports cause "cannot use useNavigate outside of context" errors because the wrong context provider is used.
// WRONG — mixed imports
import { Link } from '@tanstack/react-router'
import { useNavigate } from 'react-router' // <- still React Router!
// CORRECT — all from TanStack Router
import { Link, useNavigate } from '@tanstack/react-router'
Fix: Uninstall react-router/react-router-dom completely. TypeScript will flag every stale import.
2. HIGH: Using React Router useSearchParams pattern
// WRONG — React Router pattern, returns URLSearchParams
const [searchParams, setSearchParams] = useSearchParams()
const page = Number(searchParams.get('page'))
// CORRECT — TanStack Router pattern, returns typed object
// Route definition:
validateSearch:
z.object({
page: z.number().default(1).catch(1),
}),
// Component:
const { page } = Route.useSearch()
// page is already typed as number — no casting needed
3. HIGH: Interpolating params into to string
// WRONG — React Router habit
<Link to={`/posts/${postId}`}>Post</Link>
// CORRECT — TanStack Router: path pattern + params prop
<Link to="/posts/$postId" params={{ postId }}>Post</Link>
4. MEDIUM: Using :param syntax instead of $param
React Router: /posts/:postId
TanStack Router: /posts/$postId
File naming also uses $: src/routes/posts/$postId.tsx
Quick Reference: API Mapping
| React Router v7 | TanStack Router |
|---|---|
<BrowserRouter> | <RouterProvider router={router} /> |
<Routes> / <Route> | File-based: src/routes/*.tsx |
<Link to="/path"> | <Link to="/path"> |
<Link to={/posts/${id}}> | <Link to="/posts/$postId" params={{ postId: id }}> |
useNavigate()('/path') | navigate({ to: '/path' }) |
useParams() | useParams({ from: '/route/$param' }) |
useSearchParams() | validateSearch + useSearch({ from }) |
useLoaderData() | Route.useLoaderData() |
useLocation() | useMatch, useMatches, useParams, useSearch |
<Outlet /> | <Outlet /> |
loader({ params }) | loader: ({ params }) => ... (route option) |
action({ request }) | Use mutations / form libraries |
lazy(() => import(...)) | autoCodeSplitting or .lazy.tsx files |
:paramName | $paramName |
* (splat) | $ (splat, accessed via _splat) |
FAQ
What does the migrate-from-react-router skill do?
Step-by-step migration from React Router v7 to TanStack Router: route definition conversion, Link/useNavigate API differences, useSearchParams to validateSearch + useSearch, useParams with from, Outlet replacement, loader conversion, code splitting differences.
How do I install migrate-from-react-router?
Run npx skills add https://github.com/tanstack/router --skill migrate-from-react-router in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/migrate-from-react-router/ (personal) or .claude/skills/migrate-from-react-router/ (project).
Which AI agents can use migrate-from-react-router?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is migrate-from-react-router safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains migrate-from-react-router?
It is published by tanstack in tanstack/router. It has 181 recorded installs.
More from tanstack/router
router-core
tanstack/router
Framework-agnostic core concepts for TanStack Router: route trees, createRouter, createRoute, createRootRoute, createRootRouteWithContext, addChildren, Register type declaration, route matching, route sorting, file naming conventions. Entry point for all router skills.
react-router
tanstack/router
React bindings for TanStack Router: RouterProvider, useRouter, useRouterState, useMatch, useMatches, useLocation, useSearch, useParams, useNavigate, useLoaderData, useLoaderDeps, useRouteContext, useBlocker, useCanGoBack, Link, Navigate, Outlet, CatchBoundary, ErrorComponent. React-specific patterns for hooks, providers, SSR hydration, and createLink with forwardRef.
react-start
tanstack/router
React bindings for TanStack Start: createStart, StartClient, StartServer, React-specific imports, re-exports from @tanstack/react-router, full project setup with React, useServerFn hook.
start-core
tanstack/router
Core overview for TanStack Start: tanstackStart() Vite plugin, getRouter() factory, root route document shell (HeadContent, Scripts, Outlet), client/server entry points, routeTree.gen.ts, tsconfig configuration. Entry point for all Start skills.
router-query
tanstack/router
Integrating TanStack Router with TanStack Query: queryClient in router context, static queries and fire-and-forget queries in loaders, useSuspenseQuery in components, defaultPreloadStaleTime: 0, setupRouterSsrQueryIntegration for SSR dehydration/hydration and streaming, per-request QueryClient isolation.
start-server-core
tanstack/router
Server-side runtime for TanStack Start: createStartHandler, request/response utilities (getRequest, setResponseHeader, setCookie, getCookie, appendResponseHeader), three-phase request handling, AsyncLocalStorage context.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance 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.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.