// the find
Valian/live_vue
End-to-end reactivity for Phoenix LiveView and Vue
LiveVue embeds Vue 3 components inside Phoenix LiveView, syncing props from the server over the LiveView websocket instead of making you write imperative JS hooks. It's for Phoenix developers who've hit the ceiling of plain LiveView hooks for complex client state and want Vue's component model and ecosystem without standing up a separate SPA.
Props are diffed with JSON Patch so only what changed crosses the websocket, not a full payload every update. QuickBEAM SSR renders Vue server-side without needing a Node.js process in production, which is the usual pain point for SSR'd component frameworks bolted onto a BEAM app. useLiveForm wires directly into Ecto changesets for validation, so you're not duplicating validation rules between client and server. The Igniter-based installer actually configures Vite, assets, and config files for you instead of leaving you to copy boilerplate from a guide.
It's a fork of LiveSvelte adapted for Vue, so a chunk of the design (the installer, the diffing approach, even some guide structure) is inherited rather than independently reasoned about, and the two projects will keep needing to track each other's feature sets. You still need a full Vite/Node build pipeline for assets even though SSR itself doesn't need Node at runtime, which is a second toolchain next to whatever Phoenix already uses. The Igniter installer only works on Phoenix 1.8+, so anyone on an older app is doing manual wiring per the install guide. Credits and commit history point to essentially one maintainer, which is a real bus-factor risk for something sitting in your request path.