-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
fix: optimize reporter file output #9265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
hi-ogawa
wants to merge
9
commits into
vitest-dev:main
Choose a base branch
from
hi-ogawa:12-16-fix_optimize_reporter_file_output
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
fix: optimize reporter file output #9265
hi-ogawa
wants to merge
9
commits into
vitest-dev:main
from
hi-ogawa:12-16-fix_optimize_reporter_file_output
+78
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
@vitest/browser
@vitest/browser-playwright
@vitest/browser-preview
@vitest/browser-webdriverio
@vitest/coverage-istanbul
@vitest/coverage-v8
@vitest/expect
@vitest/mocker
@vitest/pretty-format
@vitest/runner
@vitest/snapshot
@vitest/spy
@vitest/ui
@vitest/utils
vitest
@vitest/web-worker
@vitest/ws-client
commit: |
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
hi-ogawa
added a commit
to hi-ogawa/vitest-9216-repro
that referenced
this pull request
Dec 16, 2025
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This finally tries to optimize the persisted structure itself.
The raw data format is:
// files [ { id: "...", importDurations: { "imported-file-1": { seltTime: ..., totalTime: ..., external: ..., importer: ..., }, "imported-file-2": { seltTime: ..., totalTime: ..., external: ..., importer: ..., }, } }, { id: "...", importDurations: { "imported-file-1": { seltTime: ..., totalTime: ..., external: ..., importer: ..., } } }, ]This PR squeezes this into something like:
The original each key/value entry leads to about 150 bytes, but this squeezes into about 20 bytes. However, when considering the scale of the number of entries being (number of test files) x (number of source files), this approach cannot solve the inherent issues.
Result
See https://github.com/hi-ogawa/vitest-9216-repro/
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.