Exploring agent-friendly runtime diagnostics for Vite

[MapleCity1314]

I have been exploring a problem that feels under-served in the current Vite ecosystem:

debugging a running Vite app from an agent loop is a different problem from browser automation, and a different problem from human DevTools usage.

Most tools seem to fall into two buckets:

• browser automation tools, which can drive the page but are not Vite-aware
• GUI devtools, which are useful to humans but not built for structured, repeatable runtime inspection

That leaves a gap:

a Vite-focused runtime diagnostics layer designed for agent workflows from the start

I built a small project around that idea: vite-browser

The point is not to be another browser wrapper. The point is to expose Vite-aware runtime signals and framework state as structured CLI output:

• Vite runtime status
• HMR summary and trace
• module graph snapshot and diff
• mapped errors with optional inline source
• Vue / React / Svelte runtime inspection
• framework-specific state such as Pinia and Vue Router where available

There are also supporting utilities like logs, network inspection, screenshots, and page eval, but those are secondary. The main idea is making runtime diagnostics queryable in a way that fits an agent loop.

The command model matters too.

Each CLI call is a one-shot request against a long-lived browser daemon. That gives agents a simple command surface while avoiding the cost of rebuilding browser lifecycle management on every step.

In practice, that means an agent can:

• inspect runtime state
• compare HMR behavior across changes
• query mapped errors
• re-run inspection without resetting the whole browser session

What I am interested in is whether this framing resonates:

• does "agent-friendly runtime diagnostics for Vite" feel like a real missing category?
• which Vite-aware signals would be most valuable in this kind of workflow?
• what is hardest to surface today in a structured, repeatable way when debugging Vite apps?

Project:
https://github.com/MapleCity1314/vite-browser

[aniruddhaadak80]

Hey @MapleCity1314,

Vite is usually blazingly fast, but issues like this often crop up around dependency pre-bundling or rollup configurations.

1. Pre-bundling: Try deleting your node_modules/.vite cache and running npm run dev -- --force to make Vite rebuild the dependencies.
2. Externalizing Modules: If you are seeing issues where built-in node modules (like "stream" or "path") are breaking, it is because Vite is primarily a frontend build tool. You might need to add polyfills via vite-plugin-node-polyfills or explicitly externalize it in build.rollupOptions.external.

Let me know if clearing the Vite cache or tweaking the Rollup config gets you past this hurdle.

Hope this points you in the right direction! Let me know how it goes. Happy coding!

[MapleCity1314]

Thanks for the reply! I think I may have framed the post poorly — this is actually a project showcase, not a debugging question.

vite-browser is a CLI tool I built for exposing Vite runtime diagnostics as structured output, specifically designed to fit into agent loops. The goal is making things like HMR state, module graph, and mapped errors queryable in a repeatable, machine-friendly way.

No build issues on my end — happy to clarify anything about the project if you're curious!