One of the most significant shake-ups in the React ecosystem just landed: Remix 3 Beta Preview is here and it no longer uses React.
Released on April 29, 2026, by Remix co-founder Michael Jackson, the Remix 3 beta marks a dramatic pivot. After years as a React-based full-stack framework (and the foundation of React Router), Remix is now charting an entirely new course built directly on web platform primitives, without React at its core.
What Changed?
Remix 3 is a ground-up rewrite. The team describes it as a full-stack framework in the truest sense, not just routing and rendering, but the entire application layer:
- Routes, request handlers, responses, and middleware
- Sessions, auth, forms, and file uploads
- Asset delivery, UI components, theming, and networking
- Data and database management
- Testing infrastructure
All under one remix umbrella, but built from small, composable packages rather than a monolith.
Built for the Web, Not React
Remix 3 routes are Fetch API routes. Controllers return responses. Middleware owns the request lifecycle. Forms submit to URLs. The framework leans into durable web concepts rather than framework-specific abstractions.
One standout new concept is Frames, server-rendered UI with a src attribute. The client can load, navigate, or reload a frame independently while the server keeps rendering HTML. It is server and client communication that feels native to the web: URLs, requests, responses, and markup instead of a separate RPC layer.
Unbundling Assets
Remix 3 introduces a concept called unbundling, a deliberate departure from the bundler-centric model that has dominated modern web development. The runtime is the source of truth. Assets are compiled and served by Remix, but the app model does not depend on a big pre-runtime analysis step. There are no special semantics around import statements.
The team argues this makes the framework more predictable for both humans and AI coding agents, which benefit from clear, durable concepts like routes, controllers, middleware, and forms.
What This Means for the React Ecosystem
Remix was one of the most prominent React frameworks, and its departure from React is a notable signal. While Next.js remains the dominant React full-stack framework, Remix’s pivot highlights growing interest in web-native approaches that do not require a JavaScript framework as the foundation.
For developers currently using Remix with React, this is a significant breaking change. Remix 2.x and React Router will continue to be maintained, but the future of Remix is clearly framework-agnostic.
Try the Beta
The Remix 3 beta is available now for experimentation:
npx remix@next new my-remix-appKey Takeaway: Remix 3 is a bold bet on the web platform itself over any single JavaScript framework. Whether it succeeds or not, it is a fascinating development that every React and Next.js developer should be watching closely.
Hashtags: #Remix3 #ReactJS #WebDevelopment #JavaScript #FullStack #WebFramework #NextJS #FrontendDev
Sources and Resources: