Phoenix streams server logs to browser console
phoenix_live_reload now ships server logs to the browser's web console via Phoenix channels, collapsing the debug workflow from terminal-hopping to a single pane.
June 5, 2026
Summary
Eliminates context-switching between browser devtools and terminal when debugging UI/server interactions. Server logs appear collocated with client logs and JS errors, reducing time spent scrolling through terminal backlog.
Why it matters
Eliminates context-switching between browser devtools and terminal when debugging UI/server interactions. Server logs appear collocated with client logs and JS errors, reducing time spent scrolling through terminal backlog.
Implementation verdict
Replaces the manual terminal-monitoring pattern for development debugging. Requires Phoenix ~1.5+, a one-line config addition, and a single JavaScript enabler call. Ship it now—this is zero-friction quality-of-life for any Phoenix app.
Sources
- 1.the entire meat of the live reload log shipping mechanism is less than 30 LOC
- 2.This has been released with {:phoenix_live_reload, "~> 1.5"}
- 3.Interlace your server logs there, and it becomes a one-stop-shop of useful info
- 4.We dog-food Phoenix's built-in bidirectional cli/server communication layer to make this happen
Dev Signal
Get briefs like this in your inbox — free, 3x a week.
100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.