npm / @vitejs/devtools
@vitejs/devtools
What changed in @vitejs/devtools 0.7 to 0.8, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-28.
1 breaking2 behavior and defaults12 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@vitejs/devtools 0.89 changes
Breaking changes 1
json-render moves to @vitejs/devtools, a breaking change for developers using it.
Fixes and other changes 8
Uses auto-loaded DevTools in UI dev servers.
Adds missing types for DevTools() config options.
Filtered-out importers no longer hide modules in the module graph.
Includes no-result transform hooks, no-result load hooks, and same-ID resolutions in module timings.
Prevents Rolldown builds from inheriting the development NODE_ENV.
Preserves successful formatting when stderr contains notices.
Records sessions and exits cleanly when running a build.
Includes asset and package data in static reports.
@vitejs/devtools 0.76 changes
Behavior and default changes 2
Devtools injection is supported in builds.
Forwards onTrusted from DevToolsConfig to the interactive auth handler.
Fixes and other changes 4
Client module resolution is declared before plugin setup.
Project paths and Vite+ build commands are respected.
Vite DevTools is registered for devframe discovery.
The tokenized Vitest UI URL is embedded.