Zero-Config Inspection
Point at any running Vite dev server. No plugins, no config changes, no project modifications. Works with Vue, React, and Svelte out of the box.
Runtime diagnostics for Vite, from the terminal. Connect to a running dev server, query HMR traces, mapped errors, and component state as structured output — built for developers and AI agents alike.
The debugging gap
You save a file. Vite hot-updates. The page breaks. The error overlay tells you what failed — but not which update caused it, how the change propagated through your component tree, or whether the real problem is a stale store, a broken import, or a network regression. vite-browser fills that gap.
Correlate the current error with recent hot-module updates. Get rule-based diagnoses like missing-module or hmr-websocket-closed to narrow the problem fast.
Query Vue component trees, Pinia stores, React props and hooks, or Svelte state — alongside console logs, network traces, and source-mapped errors — all from one terminal.
When a store update breaks a downstream component, trace the store → render → error path with high-confidence evidence instead of manually stepping through DevTools.
A typical debugging session
vite-browser open http://localhost:5173
vite-browser errors --mapped --inline-source
vite-browser correlate errors --mapped --window 5000
vite-browser diagnose propagation --window 5000