feat: ability to turn off import durations collection #9262
+33
−0
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
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:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.