devtools

[!IMPORTANT] Please take a moment to read this. Thank you! I should include a brief explanation of the problem in my own words in every PR. If that explanation is missing, please @mention me and do not merge this PR until I have added it. You may also leave this PR unaddressed (because this means I have not fulfilled my responsibilities as the author). If my explanation is unclear or difficult to follow, please ask me to clarify or provide reproduction steps or supporting evidence. I welcome suggestions and counterarguments, especially questions about anything I may have overlooked. (Your feedback helps me learn and improve. 🙏) I hold myself to this standard for every PR, regardless of its size. Summary When I run Format Inspector without an Oxfmt config, Oxfmt 0.70.0 prints a defaults notice to stderr. A clean check or successful write exits with code 0, but DevTools throws and discards the result. In write mode, the file has already been formatted even though the UI reports failure. Classify the command result using its exit code and parsed status before saving it. Successful runs and check-mode formatting findings are saved even when stderr contains a notice. Execution failures still produce , using stderr or an exit-code fallback when stderr is empty. Evidence With real Oxfmt 0.70.0 and no config, the unchanged upstream handler rejects clean checks, checks with formatting findings, and successful writes. The patched handler saves all three results; write mode also produces the expected file contents. Browser verification against the rebuilt package: no-config write saves a result, and a clean check saves a result. Regression tests: 6 fail against the original handler; all 16 pass after the fix. Coverage includes notices, formatting findings, execution errors, missing exit codes, and process startup failures. , , and pass (351 tests passed, 2 skipped). reports 8 existing Vite plugin type errors in the Oxc, Rolldown, and Vite RPC modules. Re-running with both changed files restored to the upstream baseline produces identical errors. Merge Danger Door: Two-way. No persisted result schema changes. Blast Radius: Oxfmt. Changes command-result classification in Format Inspector.

Description Switching between large Rolldown traces retains up to 32 readers regardless of trace size. This can keep multiple multi-GiB sessions' parsed data alive after their requests finish. Add a 256 MiB source-log-size budget alongside the existing reader count limit, evicting the least recently used idle readers. Account for source size even when restoring disk caches, and prune again when reads settle. Readers in the current session directory and pending reads remain available, so oversized or concurrent sessions can exceed the budget; source size is a cache weight, not a heap measurement. Eviction drops cache ownership without clearing data that RPC handlers may still use. Disposing an evicted reader also checks its identity before removing the cache entry, preserving any replacement for the same path. Linked Issues None. Additional context Adds 10 regression cases covering LRU eviction, oversized sessions, count limits, retained caller data, replacement disposal, disk-cache restoration, and pending reads across all three read modes. All 10 fail on the previous implementation and pass with this change. Three additional regressions exercise , , and with separate metadata files: loading metadata preserves the oversized log reader, repeated requests reuse it, and switching sessions still evicts it. These three cases fail with reader-only protection and pass with session-level protection. Validation: , , and passed (355 passed, 2 skipped). reports the same eight existing Nuxt/Vite plugin type errors as unmodified . This is independent of #592, which bounds bulk reads during plugin detail hydration.

Description Opening plugin details on a large Rolldown trace can exhaust the heap: hydration reads every plugin's hook events before filtering, then resolves all transform contents together. Read indexed hooks in batches of up to 128 calls and 1 MiB of source event bytes, retaining only the requested plugin's metrics. Compare transform contents in groups of up to 128 calls so event payloads and resolved strings can be released between groups. An oversized hook is read alone; this bounds bulk reads rather than imposing a total heap limit. Linked Issues None. Additional context Adds five regression cases covering call and byte limits, oversized hooks, filtering and ordering across modules, transform equality, and string references with missing index entries. All five fail on the previous implementation and pass with this change. Reader cache eviction is unchanged. Validation: , , and passed (347 passed, 2 skipped). reports the same eight existing Nuxt/Vite plugin type errors as unmodified , in the Oxc, Rolldown, and Vite files.