CodSpeedHQ
codspeed-node
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
CLI run
by
GuillaumeLagrange
12 days ago
CLI run
by
GuillaumeLagrange
12 days ago
CLI run
by
GuillaumeLagrange
12 days ago
test(vitest-plugin): add with-vitest-v4 example Now that the plugin's own dev dependency tracks Vitest 5, add a dedicated Vitest 4 example so the legacy (v3/4) benchmark seam keeps explicit coverage alongside the existing with-vitest-v3 example. Mirrors that example, pinning vitest ^4.1.9. Refs COD-2931 Co-Authored-By: Claude <noreply@anthropic.com>
cod-2931-prepare-compatibility-with-vitest-5
12 days ago
feat(vitest-plugin): support vitest 5 alongside 3 and 4 Vitest 5 reworked the benchmark backend: the dedicated `NodeBenchmarkRunner` and the `vitest/runners` / `vitest/suite` entrypoints are gone, benchmarks now run inside `test()` through the unified `TestRunner`, and tinybench moved to v6 (stats moved from `result.benchmark` to `task.result.latency`, `includeSamples` became `retainSamples`). Detect the installed Vitest generation and select the integration seam behind a `VitestBackend` abstraction so the rest of the plugin never inspects the version: - v3/4 keep the custom benchmark runner per instrument mode (analysis/walltime). - v5 installs instrumentation from a setup file that patches the shared `TestRunner.runBenchmarks` static. A setup file (rather than a custom `test.runner`) leaves the runner untouched for non-benchmark tests and also applies to the browser pool.
cod-2931-prepare-compatibility-with-vitest-5
12 days ago
build: pin -std=c11 for instrument-hooks core.c The Zig-generated dist/core.c is rejected under C23 (GCC 15's default), so pin C11 via cflags_c (C-only, so the C++ sources are unaffected).
main
19 days ago
build: pin -std=c11 for instrument-hooks core.c The Zig-generated dist/core.c is rejected under C23 (GCC 15's default), so pin C11 via cflags_c (C-only, so the C++ sources are unaffected).
cod-2953-use-stdc11-for-instrument-hooks-in-integrations
19 days ago
v5.7.1
main
19 days ago
Latest Branches
CodSpeed Performance Gauge
-59%
Support vitest 5
#86
12 days ago
6791750
cod-2931-prepare-compatibility-with-vitest-5
CodSpeed Performance Gauge
-10%
build: pin -std=c11 for instrument-hooks core.c
#84
21 days ago
1999ec9
cod-2953-use-stdc11-for-instrument-hooks-in-integrations
CodSpeed Performance Gauge
+58%
fix: emit perf maps when not parsing the full inlining logs from V8
#85
19 days ago
c88994c
cod-2987-e2e-tests-show-no-flamegraph-for-vitest
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs
×
Advertisement