chore(deps): update vitest monorepo to ^3.0.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/coverage-v8 (source)	^3.0.7 -> ^3.0.8
@vitest/expect (source)	^3.0.7 -> ^3.0.8
vitest (source)	^3.0.7 -> ^3.0.8

---

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v3.0.8

Compare Source

   🐞 Bug Fixes

• Fix fetch cache multiple writes  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7546 (1a8b4)
• Use browser.isolate instead of config.isolate  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7560 (4b5ed)
• Remove vestigial spy stub, import directly from @vitest/spy  -  by @​mrginglymus in https://github.com/vitest-dev/vitest/issues/7575 (7f7ff)
• Correctly split the argv string  -  by @​btea in https://github.com/vitest-dev/vitest/issues/7533 (4325a)
• browser:
  • Remove @​testing-library/dom from dependencies  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7555 (5387a)
  • Improve source map handling for bundled files  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7534 (e2c57)
  • Print related test file and potential test in unhandled errors  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7564 (fee90)
• runner:
  • Fix beforeEach/All cleanup callback timeout  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7500 (0c292)
  • Fix and simplify Task.suite initialization  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7414 (ca9ff)
• snapshot:
  • Allow inline snapshot calls on same location with same snapshot  -  by @​jycouet and @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7464 (d5cb8)
• vite-node:
  • Fix buildStart on Vite 6  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7480 (c0f47)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
page-building-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 11, 2025 7:43pm
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 11, 2025 7:43pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 11, 2025 7:43pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Mar 11, 2025 7:43pm
test-next-studio	⬜️ Ignored (Inspect)			Mar 11, 2025 7:43pm

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vitest/coverage-v8@3.0.7 ➜ 3.0.8	Transitive: environment, filesystem, shell	+34	5.95 MB	antfu, oreanno, patak, ...1 more
npm/@vitest/expect@3.0.7 ➜ 3.0.8	Transitive: environment	+11	842 kB	antfu, oreanno, patak, ...1 more
npm/vitest@3.0.7 ➜ 3.0.8	Transitive: environment, filesystem, network, shell, unsafe	+85	9.53 MB	antfu, oreanno, patak, ...1 more

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42%	54407 / 129513
🔵	Statements	42%	54407 / 129513
🔵	Functions	46.88%	2728 / 5819
🔵	Branches	79.36%	10193 / 12843

File Coverage

No changed files found.

Generated in workflow #32093 for commit 802ec6f by the Vitest Coverage Report Action

[github-actions]

⚡️ Editor Performance Report

Updated Tue, 11 Mar 2025 19:57:50 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	19.8 efps (51ms)	19.6 efps (51ms)	+1ms (+1.0%)	✅
article (body)	75.5 efps (13ms)	78.4 efps (13ms)	-1ms (-/-%)	✅
article (string inside object)	20.4 efps (49ms)	19.6 efps (51ms)	+2ms (+4.1%)	✅
article (string inside array)	19.2 efps (52ms)	18.5 efps (54ms)	+2ms (+3.8%)	✅
recipe (name)	47.6 efps (21ms)	31.3 efps (32ms)	+11ms (+52.4%)	🔴
recipe (description)	47.6 efps (21ms)	34.5 efps (29ms)	+8ms (+38.1%)	🔴
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (5ms)	+0ms (-/-%)	✅
synthetic (title)	18.3 efps (55ms)	17.5 efps (57ms)	+3ms (+4.6%)	✅
synthetic (string inside object)	18.3 efps (55ms)	18.2 efps (55ms)	+1ms (+0.9%)	✅

efps — editor "frames per second". The number of updates assumed to be possible within a second.

Derived from input latency. efps = 1000 / input_latency

Detailed information

🏠 Reference result

The performance result of sanity@latest

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	51ms	54ms	64ms	243ms	1235ms	11.9s
article (body)	13ms	16ms	23ms	146ms	212ms	5.0s
article (string inside object)	49ms	51ms	53ms	63ms	515ms	8.1s
article (string inside array)	52ms	54ms	57ms	74ms	844ms	8.2s
recipe (name)	21ms	23ms	28ms	48ms	2ms	7.1s
recipe (description)	21ms	24ms	29ms	35ms	0ms	5.0s
recipe (instructions)	5ms	7ms	8ms	8ms	0ms	3.0s
synthetic (title)	55ms	59ms	63ms	346ms	1265ms	14.8s
synthetic (string inside object)	55ms	57ms	64ms	242ms	1047ms	8.2s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	51ms	58ms	76ms	280ms	1294ms	11.8s
article (body)	13ms	14ms	18ms	51ms	63ms	4.9s
article (string inside object)	51ms	53ms	55ms	152ms	779ms	8.3s
article (string inside array)	54ms	56ms	61ms	234ms	1286ms	8.8s
recipe (name)	32ms	33ms	35ms	42ms	69ms	8.6s
recipe (description)	29ms	30ms	31ms	48ms	10ms	6.1s
recipe (instructions)	5ms	7ms	7ms	9ms	0ms	3.1s
synthetic (title)	57ms	66ms	102ms	425ms	1449ms	14.6s
synthetic (string inside object)	55ms	61ms	76ms	413ms	1601ms	9.1s

📚 Glossary

column definitions

• benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
• latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
• p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
• p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
• p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
• blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
• test duration — how long the test run took to complete.