@hiogawa.bsky.social
π€ 1099
π₯ 70
π 50
https://github.com/hi-ogawa
@vitest.dev
@vite.dev
contributor
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...
.
3 days ago
1
5
0
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/...
add a skeleton here at some point
12 days ago
0
5
1
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!
add a skeleton here at some point
12 days ago
0
14
3
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`. π
add a skeleton here at some point
17 days ago
1
17
2
First time speaking at a conference!
add a skeleton here at some point
21 days ago
3
21
2
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/...
loading . . .
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...
https://github.com/vitejs/vite/discussions/20913
24 days ago
1
11
3
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!
about 1 month ago
1
20
0
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.
about 1 month ago
1
1
0
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...
add a skeleton here at some point
about 1 month ago
1
34
7
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".
about 2 months ago
1
3
0
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...
about 2 months ago
1
4
0
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 π
add a skeleton here at some point
2 months ago
1
4
0
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-...
loading . . .
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...
https://github.com/vitejs/vite-plugin-react/pull/767
2 months ago
1
3
0
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! π
2 months ago
0
20
1
After I saw Qwik team's Rollup PR for merging merging `this.emitFile` chunks
github.com/rollup/rollu...
, I was interested to try out the same idea for optimizing `"use client"` chunks and it looks like this works beautifully!
github.com/hi-ogawa/vit...
5 months ago
0
6
0
reposted by
Vue Fes Japan
6 months ago
οΌ π’ Vue Fes Japan 2025 β First Speakers Announced! π₯ οΌΌ We're thrilled to welcome an amazing speaker lineup for Vue Fes Japan 2025! β‘οΈ Website:
vuefes.jp/2025/en/spea...
π More speakers coming soon! π’ CFP opens Mon, June 2 at 12:00 PM JST π Stay tuned! π₯
#vuefes
#vuejs
loading . . .
Vue Fes Japan 2025 - Speaker
This is one of the largest Vue.js conferences in Japan, taking place on Saturday, October 25, 2025. In addition to sessions by renowned speakers from Japan and abroad, we are planning various events s...
https://vuefes.jp/2025/en/speaker
2
18
8
Setting up Windows CI for the first time on my own repo
github.com/hi-ogawa/vit...
Someone reported React router demo is broken on Windows but it's now fixed! I was afraid this might become a nightmare CI debugging session, but it turned out it's just a usual path issue π
loading . . .
fix(rsc): support Windows by hi-ogawa Β· Pull Request #884 Β· hi-ogawa/vite-plugins
Closes @hiogawa/vite-rsc doesn't work on WindowsΒ #883
https://github.com/hi-ogawa/vite-plugins/pull/884
6 months ago
0
7
0
vite-plugin-inspect works great on RSC app! Here is a screenshot of "use client/server" transform in React Router demo
github.com/hi-ogawa/rsc...
This is so convenience and I've also added it to `react-server-dom-vite` PR's `fixtures/flight-vite`
github.com/facebook/rea...
6 months ago
2
21
4
At this point, I'm just copying all the demos by React router team π , but I think this is a cool part of RSC. As long as React router API is aligned with RSC convention and Bundlers support the convention, the same demo should work. Thanks React Router and Parcel for opening up this opportunity!
6 months ago
1
30
3
I ported React Router RSC Movies demo to Vite.
github.com/hi-ogawa/rsc...
RSC bundler feature is encapsulated in the package `@hiogawa/vite-rsc` and React Router RSC API integration is found in `./react-router-vite`. The latter part is mostly a copy of `parcel-plugin-react-router`.
add a skeleton here at some point
6 months ago
1
15
3
This is very exciting! React router and Parcel has shown the proper boundary of RSC support between application layer and as bundler layer. Jacob shared their work with me early and that has been guiding me better for RSC support on Vite. Thanks for the shout out in the post!π
add a skeleton here at some point
6 months ago
1
27
5
I just updated `react-server-dom-vite` PR with css import support
github.com/facebook/rea...
. I'm not sure if this is a right direction, but this seems to nicely handle css code split at each client reference level and it might potentially work as "framework-less" abstraction for Vite RSC.
loading . . .
feat: add react-server-dom-vite by hi-ogawa Β· Pull Request #33152 Β· facebook/react
Summary As a continuation from the discussion on Jacob's PR #31768, this is a new PR to add the react-server-dom-vite package and fixtures/flight-vite. To begin with, thank you to the React tea...
https://github.com/facebook/react/pull/33152#issuecomment-2868294151
6 months ago
0
44
9
This was due to Vite module factory function's +2 lines offset, which is handled internally for SSR by adding `;;` , but we need to do the same in `findSourceMapURL`. `registerServerReference` and console replay positions are now right on the spot on devtools!
github.com/hi-ogawa/vit...
add a skeleton here at some point
6 months ago
0
10
1
Testing a nice little RSC feature `findSourceMapURL` on Vite. It looks like this allows jumping to server actions on React dev tools. `createServerReference` is right on the spot, but `registerServerReference` seems off a few lines. I wonder if this is due to `Error.stack` behavior on Vite SSR π€
loading . . .
6 months ago
0
24
3
Sneaking in Vitest browser mode on Oxc repo π
github.com/oxc-project/...
The PR added a test for napi-rs wasi build of oxc parser, which involves wasm, shared memory, and web workers.
loading . . .
test(napi/parser): test wasi browser by hi-ogawa Β· Pull Request #9793 Β· oxc-project/oxc
This adds (almost) e2e testing of oxc-parser on browser using Vitest browser mode. How to test locally: cd napi/parser pnpm build-wasi pnpm build-npm-dir pnpm test-browser # before this, you'l...
https://github.com/oxc-project/oxc/pull/9793
8 months ago
0
17
2
I've been curious about how type bundling is done by rollup-plugin-dts
github.com/Swatinem/rol...
. Just to see a glimpse of the idea, I made a quick playground to dump their internal estree ast
github.com/hi-ogawa/rep...
. I didn't expect invalid js code coming out π
8 months ago
0
4
0
Huge improvement for Vitest development workflow, thanks to isolated declaration! I didn't think the migration was possible until I see PRs by
@sxzz.dev
. Just started to sponsor Kevin for the amazing work!
add a skeleton here at some point
8 months ago
2
28
7
you reached the end!!
feeds!
log in