vite scan?

[arashsheyda]

Clear and concise description of the problem

Tools like React Scan provide valuable insights into component performance and render behaviour, making it easier to debug and optimize applications.

Suggested solution

It would be great to introduce a “Vite Scan” feature as part of Vite DevTools, or include it as an official example/integration maybe?

Screen.Recording.2026-03-19.at.1.24.32.AM.mov

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[arashsheyda]

I came up with something btw 😄

https://github.com/arashsheyda/vite-scan

[webfansplz]

We’ve noticed similar projects in the community, like the one at element-source. Recently, we’ve had some discussions with devtools authors about how to support it. Since different front-end frameworks have unique needs—like varying template syntaxes—it’s tough to say that Vite Devtools can fully support all of them. That’s why we’re thinking about creating standard proposals for the inspector on the Vite Devtools side. This way, authors and contributors from different frameworks can implement features based on a common standard. In the long run, this could even lead to a "standard devtools schema." It’s a process that will take time, starting with writing RFCs and proposals, gathering community feedback, and ultimately establishing a standard.

[arashsheyda]

ah yes makes sense, thanks for looking into it!