Excellent work on Rari! I don't want to spoil the fun and take away the achievement, but your benchmark is not a fair comparison. Rari is not using SSR. It is fetching the RSC components from the client-side, while the benchmark is measuring load times for the initial HTML.

Also, this might be a seriously wrong approach, that @owoce.bsky.social can surely validate. It works for the use cases I tested, but there might be others where this breaks.

This is a nasty hack/tech to inject opaque client references into cached RSC payloads, allowing them to be resolved when rendering the cached RSCs under "react-server" conditions. The serialized RSC contains only opaque client references, and everything starts at github.com/lazarv/react...

🚀 Living on the edge! @lazarv/react-server might be the first framework using Vite 6.1 in it's latest published version? Awesome work Vite team! 👏

It's already in the oven and baking! ⏳🚀⚡

oh yes please! how much of Vite could be dropped in an ideal native ESM-only world? maybe more than 50%?

The updated React 19 experimental version now supports the experimental ViewTransition API! 🎬✨ Exciting to see how this evolves and what new possibilities it unlocks for seamless UI transitions. 🚀

This alias setup is necessary because @lazarv/react-server can be used via `npx` without requiring React to be installed in the developer's project. In this case, the framework lives in a completely different location, making precise module resolution essential. 🌍🔗

The environment-dependent alias plugin is needed because React is used in two versions: one for RSC rendering with the react-server Node.js module resolution condition and another for SSR & client rendering. 🔄🎭

Upgrading from Vite 6 alpha 18 to the latest required completely different workarounds! 🔄 It was interesting to see how things changed, but in the end, the update made everything feel more refined. Loving the progress! 🚀