Updated

React Router

Routing library for React with data loading, mutations, and an optional full-stack "framework mode".

443 open-source projects declare React Router in their code; 1 maker's product we track uses it. What makers like most: Framework mode gives Remix-style loaders, server rendering and middleware on top of Vite with little overhead. Their most common complaint: Repeated breaking changes across major versions leave teams with large upgrade work, and some have left for alternatives. On GitHub, 35 public pull requests moved projects to React Router from tools we list, and 61 moved them away.

Open sourceSelf-hostableFree tier

Profile checked

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

How makers use React Router

Makers' products we track use React Router for frontend framework (1).

What React Router is used for

Frontend Framework · React full-stack →React apps built around web standards — loaders, actions and forms — in the lineage of Remix.Trade-off: Smaller ecosystem of starters than Next.js, and the project has changed names and APIs over its history.
Next.js1,731Astro270React235Vue.js67Svelte43React Router1Makers' products on each, for frontend framework

React Router vs the alternatives makers chose

For frontend framework, 1 of the 2,289 makers' products we know the choice of picked React Router (0%), behind Next.js (76%).

OptionMakers' products2026 launchesOpen source
Next.js1,731 76%78%Yes
Astro270 12%13%Yes
React235 10%8%Yes
Vue.js67 3%2%Yes
Svelte43 2%1%Yes
Nuxt28 1%1%Yes
React Router1 0%0%Yes

For frontend framework: how many of the 2,289 makers' products we know the frontend framework of chose each option, and the share among the 452 launched in 2026, since a tool that came first has products from every year.

When to use React Router, and when not

Pick React Router if

Something else fits better if

  • Your app lives behind a login and doesn't need search traffic: React.
  • You already know Vue, or Svelte, and need server rendering: Nuxt or SvelteKit.
  • You're building a marketing site, docs or a blog: Astro.
From each decision's guide, written from what makers' products chose and why.

React Router is the routing library for React, and since version 7 it is also a full-stack framework: Remix was merged into it, so the Remix framework continues under the React Router name. You can use as little or as much of it as you want.

More about React Router

It has three modes, each adding to the previous one. Declarative mode maps URLs to components with links and navigation hooks. Data mode moves route definitions outside of rendering and adds loaders, actions and pending states. Framework mode wraps that in a Vite plugin with a routes file, type-safe route modules, code splitting and a choice of rendering strategy. Loaders and actions work on standard Request, Response and FormData objects.

In framework mode you can server-render, pre-render chosen paths at build time, or ship a single-page app with server rendering turned off, and change your mind later without rewriting routes. Official templates cover Node with Docker (including a Postgres variant), and Vercel, Cloudflare and Netlify maintain their own. Middleware is part of the current major version.

The limits: React Server Components support is still experimental and can break in minor releases. Major upgrades depend on adopting future flags in advance, and v8 requires recent Node, React 19.2 and Vite 7, which may force other upgrades in an older codebase.

How React Router itself is built

6 tools, from its own code, website and Product Hunt page.

React Router pros and cons

What makers like most: Framework mode gives Remix-style loaders, server rendering and middleware on top of Vite with little overhead. Their most common complaint: Repeated breaking changes across major versions leave teams with large upgrade work, and some have left for alternatives.

Pros

  • Framework mode gives Remix-style loaders, server rendering and middleware on top of Vite with little overhead. HNHN 2HN 3
  • For client-only apps, Vite plus React Router just works with sane defaults. HNHN 2
  • Moving from Next.js cut one developer's deploy times from 7–8 minutes to 1–2. HN

Cons and watch-outs

  • Repeated breaking changes across major versions leave teams with large upgrade work, and some have left for alternatives. HNHN 2HN 3HN 4
  • The Remix and React Router renaming history confuses people about which project is which. HNHN 2HN 3HN 4
  • Mixing server and client code in framework mode adds mental overhead, and registering API routes takes ceremony. HNHN 2

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

What Hacker News says about React Router

On Hacker News, 22% of comments about React Router recommend it and 24% criticize it: net praise −1%, 10th best liked of 14 tools HN discusses for frontend framework.

By year

YearComments choosing it, per monthNet praise
20230.30%
20240.5−17%
20251.80%
2026 (8 mo)1.0+10%

In their words

  • “I migrated my Remix 2 app to react router 7 and I think it’s great.” HN, May 2026
  • “makes switching to plain Vite + React Router or TanStack Router surprisingly attractive” HN, Mar 2026
  • “React router duo would be a great example of known clowns.” HN, May 2026

Hacker News comments January 2023 to August 2026 that name React Router in a sentence like "I use" or "we moved to", Claude read a sample of 53 and the counts scale it to all of them; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. How it's counted, and how HN compares with makers.

Reliability and open issues

The most wanted open issue on GitHub has 82 👍.

Most wanted on GitHub

Open on 2026-10-04 in remix-run/react-router, with activity in the last year — issues and feature requests by 👍.

Who switches

More projects move away from React Router: 35 pull requests in, 61 out; the most come from Next.js and leave for Next.js.

Moving to React RouterMoving away
React Router
Next.js → React Router25 PRs
React → React Router10+ PRs
React Router → Next.js49 PRs
React Router → TanStack Start7 PRs
React Router → Astro5 PRs

Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.

Who uses it

1 makers' products, each linked to the source that shows it, and 443 open-source projects that declare it in their code. The best known on Product Hunt: Fuser (487 followers).

Job posting 1Declared in code 443How evidence is collected →
LangBot
LangBotProduction-grade platform for building agentic IM bots - 生产级多平台智能机器人开发平台/ Agent、知识库编排、插件…Frontend FrameworkIn its code · source ↗

Open source: a project that declares React Router as a dependency in its public code — verifiable, but not necessarily a live product.

What its projects tell coding agents

AGENTS.md and CLAUDE.md examples for React Router: real files, what they cover, a starting file →

What open-source projects' AGENTS.md and CLAUDE.md files say about React Router, in our words — from the 16 files that name it:

163 of the 267 open-source products built with React Router that were worked on in the last 180 days keep instruction files for coding agents — 61%, against 53% of all the projects we read. AGENTS.md is in 129, CLAUDE.md in 89.

1,022words in the median file
pnpmthe package manager most named, in 41 of 146 files
74%say how to test a change
Named more in these files than in other projects' — in how many of the 146:
What AGENTS.md files say about other tools →What open-source products tell their coding agents →

Alternatives to React Router

All alternatives by situation →

Further reading

Questions makers ask about React Router

What is React Router used for?

Routing library for React with data loading, mutations, and an optional full-stack "framework mode". Makers' products we track use it for frontend framework (1).

What are the pros and cons of React Router?

Pros makers name: Framework mode gives Remix-style loaders, server rendering and middleware on top of Vite with little overhead. For client-only apps, Vite plus React Router just works with sane defaults. Moving from Next.js cut one developer's deploy times from 7–8 minutes to 1–2. Cons: Repeated breaking changes across major versions leave teams with large upgrade work, and some have left for alternatives. The Remix and React Router renaming history confuses people about which project is which. Mixing server and client code in framework mode adds mental overhead, and registering API routes takes ceremony.

What are the alternatives to React Router?

For frontend framework, the other options makers' products we track chose most are Next.js (1,731), Astro (270), React (235), Vue.js (67), Svelte (43), Nuxt (28). Open source or self-hostable among them: Next.js, Astro, React, Vue.js, Svelte, Nuxt. Each alternative, with the situation it fits, is on the React Router alternatives page.

Do developers switch to or away from React Router?

On GitHub, 35 public pull requests moved projects to React Router from tools we list, most from Next.js (25), React (10); 61 moved them away, most to Next.js (49), TanStack Start (7), Astro (5).

When should you use React Router?

Public pages need server rendering and you want server code in the same React project (frontend framework). Something else fits better if: your app lives behind a login and doesn't need search traffic, pick React; you already know Vue, or Svelte, and need server rendering, pick Nuxt or SvelteKit.

Which mode should I use?

The modes are additive. Framework mode suits most new apps and anyone comparing it with Next.js; data mode suits teams that want loaders and actions but their own bundling and server setup; declarative mode is plain client-side routing. source ↗

I have a Remix v2 app. Is this the same thing?

Yes. React Router v7 is the next major version of Remix v2, and if you have adopted the Remix future flags, upgrading is mostly a dependency change, with a codemod for packages and imports. source ↗

Can I build a single-page app with no server?

Yes. Setting ssr to false builds an index.html you can serve statically. The root route is still rendered once at build time, so your routes must not touch browser-only APIs during the first render. source ↗

Can I pre-render some pages as static HTML?

Yes. The prerender option renders listed paths at build time using the same loaders as server rendering, either alongside a runtime server or for a fully static deploy. source ↗

Where can I deploy it?

Anywhere that runs Node or Docker, such as Fly.io, Railway or Google Cloud Run, using the official templates, or to static hosting as a single-page app. Vercel, Cloudflare and Netlify maintain their own templates. source ↗

Does it support React Server Components?

Yes, in both framework and data modes, but the support is experimental and may change in minor or patch releases. source ↗

What does upgrading from v7 to v8 involve?

If you adopted the v7 future flags, the upgrade is mostly non-breaking. v8 requires Node 22.22 or later, React 19.2.7 or later and, in framework mode, Vite 7. source ↗

Is React Router free?

Yes — it is free, open-source software.

Is React Router open source or self-hostable?

Open source, and you can self-host it. source ↗

Can AI coding agents work with React Router?

No llms.txt, official MCP server or CLI found yet.

Who uses React Router?

1 makers' products we track, each with a source, and 443 open-source projects declare it in their code. The best known of them on Product Hunt: Fuser (487 followers). source ↗