From decfeb61c71a93372f84b6d43893df86a1756308 Mon Sep 17 00:00:00 2001 From: Vladimir Date: Thu, 3 Sep 2026 15:15:14 +0200 Subject: [PATCH] docs: mention default diagnostics (#11135) --- docs/blog/vitest-5.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/blog/vitest-5.md b/docs/blog/vitest-5.md index 5f328d19b..1c6caed6c 100644 --- a/docs/blog/vitest-5.md +++ b/docs/blog/vitest-5.md @@ -84,14 +84,14 @@ Some of the changes behind these numbers: - **Smaller install.** Vitest now bundles its own dependencies, which reduces the number of packages in `node_modules` and the time spent resolving them. - **Faster coverage.** The `v8` provider merges reports with bounded memory and precompiled globs, both providers send less data over RPC, and `istanbul` moved to the maintained [`@vitest/istanbuljs`](https://github.com/vitest-dev/istanbuljs) packages. The [coverage tables](https://github.com/vitest-dev/benchmarks#coverage-vitest-4110-vs-500) in the benchmarks repository list every app. -Vitest 5 also introduces [`vitest doctor`](/guide/cli#vitest-doctor), a new command that runs your test suite with alternative configurations and recommends options that could make it faster. - The [duration breakdown](/guide/profiling-test-performance) in the reporter output now shows percentages, so it's easier to see where the time goes: ``` Duration 3.76s (environment 79%, import 13%, transform 6%, tests 1%, setup 1%) ``` +Vitest now also [prints performance hints by default](/config/experimental#experimental-diagnostics) when the collected timings show that a configuration change could make the run significantly faster. For a more thorough check, Vitest 5 introduces [`vitest doctor`](/guide/cli#vitest-doctor), which runs your test suite with alternative configurations and recommends options that could make it faster. + ## Trace View Vitest 5 adds a built-in [Trace View](/guide/browser/trace-view) for Browser Mode. When [`browser.traceView`](/config/browser/traceview) is enabled, Vitest records every interaction, assertion, and `page.mark` as a DOM snapshot and lets you replay the test step by step after the browser has already moved on. The viewer is available in the browser UI, in [Vitest UI](/guide/ui), and in the [HTML reporter](/guide/reporters#html-reporter), so it works for local debugging and for CI failures. -- 2.51.2