Skip to content

Conversation

@hi-ogawa
Copy link
Contributor

@hi-ogawa hi-ogawa commented Dec 16, 2025

Description

Resolves #9216

Trying to optimize data size #9255 is difficult since the sheer data size is huge and scale by (the number of test files) x (the number of source files), so there should be an option to disable this.

Based on the testing hi-ogawa/vitest-9216-repro#1, entirely disabling the collection itself doesn't seem to have meaning performance impact. If disabled, the blob output size almost same as v3.1.4 (before import duration is introduced).

TBD

I'm not sure how this option should be considered together with #9141 (comment).

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
  • Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 16, 2025

@vitest/browser

npm i https://pkg.pr.new/@vitest/browser@9262

@vitest/browser-playwright

npm i https://pkg.pr.new/@vitest/browser-playwright@9262

@vitest/browser-preview

npm i https://pkg.pr.new/@vitest/browser-preview@9262

@vitest/browser-webdriverio

npm i https://pkg.pr.new/@vitest/browser-webdriverio@9262

@vitest/coverage-istanbul

npm i https://pkg.pr.new/@vitest/coverage-istanbul@9262

@vitest/coverage-v8

npm i https://pkg.pr.new/@vitest/coverage-v8@9262

@vitest/expect

npm i https://pkg.pr.new/@vitest/expect@9262

@vitest/mocker

npm i https://pkg.pr.new/@vitest/mocker@9262

@vitest/pretty-format

npm i https://pkg.pr.new/@vitest/pretty-format@9262

@vitest/runner

npm i https://pkg.pr.new/@vitest/runner@9262

@vitest/snapshot

npm i https://pkg.pr.new/@vitest/snapshot@9262

@vitest/spy

npm i https://pkg.pr.new/@vitest/spy@9262

@vitest/ui

npm i https://pkg.pr.new/@vitest/ui@9262

@vitest/utils

npm i https://pkg.pr.new/@vitest/utils@9262

vitest

npm i https://pkg.pr.new/vitest@9262

@vitest/web-worker

npm i https://pkg.pr.new/@vitest/web-worker@9262

@vitest/ws-client

npm i https://pkg.pr.new/@vitest/ws-client@9262

commit: f571529

@hi-ogawa
Copy link
Contributor Author

hi-ogawa commented Jan 7, 2026

Superseded by #9401

@hi-ogawa hi-ogawa closed this Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reporters data is bloated compared to v3.1.x

1 participant