antfu/vite-dev-rpc — explained in plain English
Analysis updated 2026-07-03 · repo last pushed 2026-05-01
Build a Vite plugin with a custom dev overlay that triggers server-side actions like regenerating files.
Create a development panel that pushes live status updates from the server to the browser.
Add interactive debugging controls in the browser that communicate with the Vite dev server.
| antfu/vite-dev-rpc | redis/redis-for-vs-code | smjai/open-memory-protocol | |
|---|---|---|---|
| Stars | 75 | 76 | 66 |
| Language | TypeScript | TypeScript | TypeScript |
| Last pushed | 2026-05-01 | 2026-06-01 | — |
| Maintenance | Maintained | Maintained | — |
| Setup difficulty | moderate | easy | easy |
| Complexity | 2/5 | 2/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
The README has minimal usage docs, so you will need to read the source code or find examples to understand the API.
vite-dev-rpc lets developers building Vite plugins send messages back and forth between the browser and the dev server. In plain terms, it lets code running in your browser talk directly to code running on your local server, and vice versa, while you're developing a web app. Vite is a popular tool for building web applications, and plugins extend what it can do. Normally, the browser and the dev server don't have an easy way to chat with each other during development. This project fills that gap by providing a two-way communication channel. The browser can ask the server to do something, the server can respond, and the server can also push updates to the browser on its own. This would be useful for plugin authors who want to build interactive development tools. For example, if you're building a plugin that shows a custom overlay or panel in the browser during development, you might want that panel to trigger actions on the server, like regenerating a file or running a quick check. This package makes that kind of back-and-forth straightforward without needing to set up a separate API or WebSocket connection. The project is built on top of three things: birpc, which handles the two-way messaging, vite-hot-client, which taps into Vite's hot module replacement system at runtime, and a newer Vite API for server-client communication introduced in Vite 2.9. Because it relies on these existing pieces, it's a relatively thin layer rather than a full communication framework from scratch. The README doesn't go into much detail on usage or configuration, so you'd likely need to look at the source or examples to get started.
A small plugin that lets Vite plugins send messages back and forth between the browser and the local dev server during development, enabling interactive dev tools without a separate API.
Mainly TypeScript. The stack also includes TypeScript, Vite, birpc.
Maintained — commit in last 6 months (last push 2026-05-01).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.