Waku's Cloudflare example is also updated to use this approach, which now allows accessing bindings API during SSG github.com/wakujs/waku/...

I created a package to expose `import "cloudflare:workers"` through Node custom loader and wrangler's `getPlatformProxy`.
Here is a React Router RSC framework mode example with Cloudflare KV github.com/hi-ogawa/vit....

Waku now supports custom base. Here is an example of SSG site deployed to Github Pages hi-ogawa.github.io/waku-example...
`@vitejs/plugin-rsc` takes care of base path for handling static assets, so the required change on Waku was only application routing logic github.com/wakujs/waku/...

Nice! Thanks for pinging the team 🙏

My talk slides are available here hiroshi-talks.vercel.app/2025-10-25/1 also with source code in github.com/hi-ogawa/talks It was a great experience to talk with many awesome folks in person! Thanks @vuefes.bsky.social for the opportunity!

This is possible in principle though there's some limitations github.com/hi-ogawa/vit.... It turns out React Router RSC API allows overriding internal RSC requests without patching global `fetch`, Not so obvious demo, but here "server" component is accessing `window.navigator`. 😄

First time speaking at a conference!

Okay, here is my attempt with a fun demo! github.com/jacob-ebey/v...

There's also an example / test case here github.com/vitejs/vite-... Though mine is quite a rough sketch, the important part is to use temporary references to achieve "donut pattern" (i.e. static shell + dynamic children). I've wanted Jacob to pick up this part in his library.

feat: add vue-router-ssr example with SSR assets API by hi-ogawa · Pull Request #5 · nitrojs/vite-examples Hey 👋 This is very early prototype, but I wanted to share with you to get feedback. You can find a rough documentation in https://github.com/hi-ogawa/vite-plugins/tree/main/packages/fullstack. This...

`?assets` query import is just a virtual module and it's aimed to be runtime agnostic. You can find examples with `@cloudflare/vite-plugin` github.com/hi-ogawa/vit... and Nitro vite plugin github.com/nitrojs/vite...

Also just right time, Remix 3 came out with a builtin concept of "hydrated component", so I ported Preact island demo. The plugin here implements `/islands/` and `/frames/` directories convention to auto wrap component by Remix `hydrated` and `Frame`. github.com/hi-ogawa/vit...

Here are examples for React router, Vue router, and Preact-based islands. These are super minimal examples, but eventually I'm hoping to be able to provide primitives for higher level meta-frameworks just like `@vitejs/pllugin-rsc` has provided foundation for Waku and React router.

RFC: Client assets metadata API for SSR · vitejs vite · Discussion #20913 This proposal introduces a new API that enables server code to access client runtime assets metadata required for server-side rendering in a framework agnostic way. This feature is currently protot...

I wrote a proposal for improving client assets management on Vite SSR application by introducing `?assets` query import. It includes many examples to demonstrate how it can be used in various routers and frameworks setup. Feedback is appreciated! github.com/vitejs/vite/...

fix: `React.use` inside `React.lazy`-ed component on SSR by hi-ogawa · Pull Request #33941 · facebook/react Summary Closes Bug: React.use inside React.lazy-ed component returns other React.use value on SSR #33937 As indicated by the previous issue comment #27731 (comment), it looks like legacy "th...

Here is a PR github.com/facebook/rea...

I just realized my name is on React 19.2.0 release note. Due to client reference being lazy component, it was super tricky for Vite RSC and Waku (though we ended up finding a workaround). I'm glad I was able to land my first PR on React to fix this!

For this use of `"use server"` to work, the route needs to be `ServerComponent` route.

Quick improvement to reduce potential confusion of "use server" on React Router RSC framework mode github.com/vitejs/vite-... Previously following "use server" is silently ignored, but this should be flagged as build error as React router inject `"use client"` for `export default` routes.

Forgot to mention that this means it works with Waku too (and this is actually what I tested originally) github.com/hi-ogawa/wak...

Nitro Vite Tracker · Issue #3461 · nitrojs/nitro 🎉 Nitro v3 is becoming "just" a Vite plugin! NoteYou can share feedback and ideas in 💬 Nitro Vite Feedback discusison. This issue is to track the development roadmap and related tasks. Initial PR (...

This nitro plugin is something I made based on how Tanstack Start integrates Nitro. Now I'm working on making the official Nitro Vite plugin to support RSC plugin out of the box. github.com/nitrojs/nitr... github.com/vitejs/vite-...

I've been experimenting with Nitro and made a plugin for `@vitejs/plugin-rsc`-based app
to be deployed anywhere. Here is an example with React Router RSC! github.com/hi-ogawa/rea...

Read the updated documentation for more info! github.com/vitejs/vite-...
It's good to know Next.js clarifies this as a "framework feature" and not package's own behavior, which I obviously referenced it when adding the doc 😀 nextjs.org/docs/app/get...

Improved the error message of invalid `server-only` and `client-only` imports on Vite RSC plugin! These "only" packages provide errors only during runtime on their own, but I didn't see any reason not to surface as build time error, so it has been included as a "plugin feature".

fix(rsc): keep server stylesheet link for hmr and avoid injecting css via client js by hi-ogawa · Pull Request #841 · vitejs/vite-plugin-react Description Related Avoid duplicate css during dev due to server rendered <link> and client inline <style> #677 Closes Local font double flashes during dev #836 Closes chore(rsc): test...

Actually while testing this, I found a bug in rsc plugin, which was causing a weird font flash during dev, but it's now fixed in latest release github.com/vitejs/vite-.... The demo app is found in github.com/hi-ogawa/rep...

Additionally, metric-based fallback font generation can be provided by just adding `fontaine` plugin github.com/unjs/fontaine/

Not as fancy as `next/font`, but simple font optimization (self hosted font + preload link) is super easy thanks to fontsource fontsource.org/docs/getting...

It may be possible to implement "use cache" like feature using `transformHoistInlineDirective`, which is exported from `@vitejs/plugin-rsc/transforms`. My minimal example is found here github.com/vitejs/vite-...

RSC transform utility is available from `@vitejs/plugin-rsc/transforms` since v0.4.29 (just released). github.com/vitejs/vite-... This utility was initially in `@hiogawa/transforms` but moved inside `@vitejs/plugin-rsc` for easier maintenance, and then now it became usable standalone again 😀

For example, this is how it looks before and after the change on Waku website waku.gg More info in github.com/wakujs/waku/...

feat(rsc): ability to merge client reference chunks based on server chunk usage by hi-ogawa · Pull Request #767 · vitejs/vite-plugin-react Description follow up to feat(rsc): ability to merge client reference chunks #766 It should be already possible on user land, but this PR adds pass more metadata to clientChunks option to do it e...

Inspired by Parcel, `@vitejs/plugin-rsc` recently changed `"use client"` chunking strategy and it's now optimized based on how they are imported on server. This works nicely with route created by `import.meta.glob` since it merges client components based on page usages. github.com/vitejs/vite-...

RSC support is now included in Vite documentation! vite.dev/plugins/#vit... It's mostly just a link to the plugin readme though. Any feedback on documentation is welcome! 🙂