React Router, one of the most widely adopted routing libraries for React applications, has entered a new phase of development. Following its merger with the Remix framework, React Router is now evolving under a unified governance model — and it’s preparing to embrace React Server Components (RSC) in a deeper, more standardized way.
We spoke with Brooks Lybrand from Shopify — a major contributor to Remix and React Router — about the project’s future and how it adapts to the modern React ecosystem.
React Router and Remix have historically shared a codebase, but operated with slightly different priorities. React Router targeted client-side apps and SPA developers, while Remix introduced full-stack capabilities, progressive enhancements, and server rendering.
By merging their efforts, the maintainers have streamlined development, reduced duplication, and aligned the APIs and internal architecture to support more advanced patterns — including React Server Components and nested routing hierarchies.
React Router is now part of the Remix GitHub org, and the core team includes engineers from Remix, Shopify, and the open-source community. This governance model ensures that roadmap decisions are aligned with modern React usage, including:
According to Lybrand, this shift “lets us deliver features faster while ensuring React Router stays compatible with both modern SPAs and full-stack React apps.”
React Server Components (RSC) represent a major shift in how data and rendering responsibilities are divided between client and server. React Router’s upcoming versions will offer first-class support for routing between server and client components, enabling hybrid navigation flows.
Some planned improvements include:
This moves React Router closer to the model popularized by Next.js, but with more flexibility and no framework lock-in.
The core team previewed several upcoming additions to React Router:
These changes aim to improve UX and developer productivity, especially in complex apps with deeply nested navigation.
Despite the Remix alignment, Lybrand stressed that React Router will remain a library, not a full-stack framework. “Our goal is composability,” he said. “We want you to build your app your way — React Router should empower, not constrain.”
That means users can continue using React Router in lightweight SPAs, Electron apps, or integrate it with server-rendering stacks like Vite, Express, or their own server architecture.
If you’re currently using React Router v6, expect smooth migration paths. The team is focused on maintaining backward compatibility while layering in enhancements.
To prepare:
React Router is no longer just a SPA routing library — it’s becoming the foundation of routing in modern React, from client-side apps to streaming server-rendered UIs. With tighter integration into the Remix ecosystem and native support for React Server Components, it’s positioned for the next decade of React app development.
As new releases roll out, developers can look forward to cleaner routing patterns, faster UX through streaming, and more expressive APIs that bridge the gap between browser and server — all while remaining fully in control of how their app is built.