Remix v3 replaces React with a fork of Preact to own the full stack and remove critical dependencies. The release targets simplicity, performance, composability, and closer alignment with Web APIs. The development principles emphasize model-first development, prioritizing Web APIs, favoring runtime over build steps, and avoiding external dependencies. Remix v3 also plans to optimize for LLMs, eschew traditional build processes, and demand composable abstractions. The change follows the merging of many Remix features into React Router v7, enabling a ground-up rethink. Community reactions have been mixed, ranging from criticism about the shift to praise for ambitious experimentation supported by Shopify.
Two years after shipping Remix v2, the Remix team recently announced working on Remix v3, with a new set of principles charting its path. Remix v3 will drop React for a fork of Preact as part of its effort to own most of its stack and feature only minimal, critical dependencies. Remix will also optimize for LLMs, build on Web APIs, eschew build processes, and demand composable abstractions.
This isn't just a new version - it's a new direction. One that's faster, simpler, and closer to the web itself. To do that, we need to own the full stack - without leaning on layers of abstraction we don't control. That means no critical dependencies, not even React. We're starting with a fork of Preact, a mature virtual DOM library already used heavily at Shopify, Google, and countless others.
This major shift comes after many of Remix's features were merged into React Router v7, freeing up the Remix team to rethink the framework from the ground up, focusing on simplicity, performance, composability, and a closer alignment with web standards. Remix identified a set of four principles underlying their development efforts: model-first development, prioritize Web APIs, runtime over build steps, and avoid dependencies.
Collection
[
|
...
]