Remix 3 Beta: heading toward zero dependencies 🧩
Remix 3 moves toward small packages and server-driven state: more control, but still limited documentation.
The Remix team has unveiled the Remix 3 beta. The framework is moving away from a monolith: instead of React and large dependencies, you get a collection of small packages. Want to work with cookies? Install a package. Need headers? There is a separate package. Middleware, proxying and auth are all separate too. How you make all of this work together is up to you.
Remix continues to promote server-driven state: forms, loaders/actions and Web APIs instead of client-side state managers.
That said, everything still looks quite rough: documentation is scarce, and in places you literally have to piece an application together from demos and examples in the repository.
The approach has become noticeably more complex, but gives you more control and predictability: less magic, more understanding of what actually happens under the hood.
Do you think this path for Remix has a future?