How Remix v2 migrated into React Router, what Remix 3’s beta changes mean, Shopify’s role, and practical migration…
Comprehensive guides covering Remix patterns, optimization techniques, and developer shortcuts. Plus code snippets and prompts to speed up your workflow.
No spam. Unsubscribe anytime.
If you last used Remix in 2023, visiting the project again in 2026 can feel like you missed a fork in its history.
The Remix you probably remember was a React framework built around nested routing, server-side data loading, and progressively enhanced forms. Remix v2 is now end-of-life. The framework capabilities that were once expected to become Remix v3 instead became part of React Router. At the same time, the Remix name is active again through Remix 3, a beta full-stack JavaScript framework that is building its own component model and no longer treats React as a critical dependency.
So, is Remix still React?
For Remix v1 and v2, yes. For Remix 3, no. Developers looking for the continuation of the original React-based Remix framework should look at React Router.
The easiest map:
Remix v1 / v2
↓
React Router v7 / v8
↓
React framework lineage continues
Remix name
↓
Remix 3
↓
New full-stack JavaScript direction
Own component model
That split explains most of the confusion.
This article covers how that split happened, what each project means today, and where Shopify fits into the history. Remix 3 is still pre-release software. Its eventual adoption, and how it will compare to React, Vue, Next.js, or other frameworks, is too early to judge reliably — the Remix team itself still describes the current beta as not production-ready.
React Router existed long before Remix.
When the Remix team announced the merger in May 2024, it described React Router as Remix's largest dependency after React itself. Over the years before that, the two projects had grown increasingly intertwined. React Router had adopted Remix's data-loading patterns, and Remix had been rewritten to depend more directly on React Router.
Remix provided a framework around concepts such as routing, data loading, form actions, pending states, optimistic UI, server rendering, and static pre-rendering. Most of those capabilities increasingly lived inside the same underlying architecture as React Router itself.
By 2024, the separation between the two projects had shrunk to the point where the team decided to eliminate the remaining framework layer rather than keep maintaining it separately.
The release the team had originally planned to call Remix v3 became React Router v7 instead.
The lineage looks roughly like this:
React Router
↓
Remix v1 / v2
↓
Framework capabilities converge
↓
React Router v7
The team had already described Remix as effectively "React Router: The Framework." Once React Router absorbed the missing framework capabilities, maintaining Remix as a separate layer stopped adding architectural value.
The migration path that followed reinforced that reading. React Router v7 shipped in November 2024, and by December the team's original announcement had been updated to recommend React Router v7 for all new projects, with existing Remix applications pointed toward the upgrade path. For applications that had already adopted the relevant future flags and Vite tooling, most of that migration came down to changing imports from @remix-run/* packages to react-router.
The transition became final on June 17, 2026, when React Router v8 shipped and Remix v2 was officially marked end-of-life alongside React Router v6.
The original Remix framework lineage remains active inside the React ecosystem today. React Router carries it forward.
The short answer sits in the opening. The more useful answer depends on which specific question someone is actually asking.
Someone asking "did Remix get discontinued" is really asking about Remix v2. It reached end-of-life alongside React Router v6 on June 17, 2026, with its framework ideas already living inside React Router.
Someone asking "is Remix still a React framework" is really asking about Remix 3. The answer there is no — the team has been explicit that Remix 3 treats React as optional rather than foundational, and is building its own component model in its place.
Someone asking "what's the Remix approach to building React apps now" is best pointed toward React Router's Framework Mode, since that's where the original Remix patterns — nested routing, loaders, actions, progressive enhancement — currently live.
Those three questions tend to get bundled together in search results and in casual conversation, which is most of why Remix feels harder to place in 2026 than it did in 2023. Separating them by generation, rather than treating "Remix" as one continuous project, resolves nearly all of the confusion at once.
Part of the confusion comes from the React Router name itself.
For years, many developers encountered React Router as a library installed inside an existing React application: you defined routes, rendered components, and let React Router handle navigation. That usage still exists and remains fully supported.
React Router now also explicitly supports three modes: Declarative, Data, and Framework. Its documentation describes the project as usable minimally, as a router, or maximally, as a complete React framework.
Framework Mode is what carries the old Remix territory: route loaders and actions, automatic data revalidation, type-safe route modules, automatic code splitting, and optional static pre-rendering or server rendering.
React Router now spans a wider architectural range than its name alone suggests:
React Router
Declarative routing
↓
Data APIs
↓
Framework Mode
↓
Full React application architecture
That range changes how React Router fits into the wider React ecosystem. A developer starting a new React application today can reasonably compare it alongside other application frameworks:
React
├── Next.js
├── TanStack Start
└── React Router
A detailed comparison between those three deserves its own article. The relevant point here is simpler: React Router now occupies the framework role developers used to associate with Remix, in addition to its original role as a routing library.
React Router v8 continued in that direction. Its baseline requirements moved to React 19.2.7+, Node 22.22+, and Vite 7+, and its ongoing work spans server rendering, pre-rendering, middleware, and route modules — the same territory Remix once covered on its own.
For developers who liked Remix for its approach to React application architecture, React Router is the project to follow today.
The Remix name did not disappear when the framework lineage moved into React Router.
The 2024 merger announcement said explicitly that the Remix brand would continue, and hinted that the team had ideas extending beyond React Router. Those ideas became public in May 2025, in a post titled "Wake up, Remix!"
The team described Remix 3 as a new direction with a much broader scope than either previous version. Remix v1 and v2 had concentrated on routing and rendering. Remix 3 aims to own considerably more of the application stack.
The April 2026 beta preview shows how far that ambition has gone. The project currently describes a stack covering routes, request handlers, responses, middleware, sessions, authentication, forms, uploads, asset delivery, data management, database management, UI components, theming, networking, and testing, developed together under one Remix package rather than assembled from separate dependencies.
The component model is the most consequential piece of that stack. The team said in 2025 that Remix 3 would remove critical dependencies it did not control, including React, and would build its own component model in its place. That decision puts Remix 3 in a different category from Next.js, TanStack Start, and React Router, all of which build directly on React.
The architecture being explored looks closer to this:
Remix 3
├── UI / component model
├── routing
├── server
├── middleware
├── sessions and auth
├── forms
├── data
├── database tooling
└── testing
Treating "Remix 3" as a normal major-version upgrade from Remix v2 undersells how different the underlying architecture has become: the team and much of the underlying philosophy carried over into a rebuilt technical foundation.
There's a sourcing detail worth knowing if you're researching Remix 3 independently.
The team's May 2025 announcement originally said Remix 3 would begin with a fork of Preact. That specific plan was later struck through in the same post and replaced with a statement that the team is building its own component model instead.
Some secondary articles written before that correction still describe Remix 3 as Preact-based. The corrected primary source is the one to trust: Remix 3's component model is being built independently, not forked from an existing library.
The Shopify connection predates this split.
Shopify announced on October 31, 2022 that Remix and its team were joining the company, positioning itself as a long-term sponsor of the open-source framework and connecting Remix's web-platform approach with its own commerce engineering work.
That relationship gives the React Router side of this story a real production-scale anchor. In the 2024 merger announcement, the Remix team said a five-million-line application central to Shopify's business was already running on React Router, alongside other Shopify applications. That detail matters less as a headline number and more as evidence that the framework capabilities moving into React Router had already been tested well beyond demo-sized projects.
Shopify's backing explains why the React Router side of this lineage has been tested at scale. Remix 3's eventual adoption is a separate question, one that its own beta releases and future production use will still have to answer.
The terminology gets easier once each name is tied to a specific generation.
Remix v2 is the previous React-based, full-stack framework. It reached end-of-life on June 17, 2026 and no longer receives security updates. Existing applications should follow the React Router upgrade path.
React Router remains a routing library and now also provides a full Framework Mode for React applications. It carries forward the architectural lineage that developed through Remix v1 and v2. For a new React application influenced by the original Remix model, React Router is the current continuation.
Remix 3 is a new full-stack JavaScript framework. It is developing its own component model and a larger set of first-party application primitives, and its April 2026 release remains a beta preview that the team itself describes as pre-release and not production-ready.
Treating these three as points on one continuous version sequence creates the confusion this article set out to resolve. Their histories overlap even though their current technical roles are distinct.
Remix 3 is unusual because it's trying to control more of the application stack than most mainstream JavaScript frameworks attempt.
A typical modern framework starts from an already-established component ecosystem:
React
↓
Next.js / TanStack Start / React Router
Vue
↓
Nuxt
From there, the framework concentrates on routing, server rendering, data handling, bundling, and application structure, while the component layer underneath is somebody else's project to maintain.
Remix 3 is testing a wider boundary. Its component model, server architecture, routing, sessions, authentication, data handling, and supporting primitives are all being designed inside the same project, by the same team, at the same time. That gives the team room to coordinate decisions across layers that are normally split between separate maintainers with separate release schedules and separate priorities.
Owning that much of the stack also means Remix 3 has to build the surrounding ecosystem that React and Vue already have: the libraries, the integrations, the accumulated developer familiarity, the production track record. React Router inherited a decade of exactly that kind of accumulated trust. Remix 3 is starting closer to zero.
Early reaction to the beta already reflects that gap. Some developers have been curious enough to try it against real prototypes; others have questioned publicly whether a framework needs its own bundler-free component model, router, and type system to compete with tooling that already works well together. Both reactions are reasonable responses to a project this early.
That team dynamic — a decade of React Router and Remix experience choosing to re-examine assumptions that shaped both projects, backed by Shopify's production environment, and now testable through a real beta — is what makes Remix 3 worth following regardless of where it eventually lands in the framework landscape.
For developers looking for the continuation of Remix v2 today, React Router remains the relevant project. Remix 3 is a separate, earlier-stage experiment in how much of a modern JavaScript stack one framework should own, and it's currently too early in that experiment to say where it lands.