CodSpeedHQ/codspeed-node - CodSpeed

codspeed-node

Blog Docs Changelog

Performance History

Latest Results

feat(vitest-plugin): use the vitest 5 benchmark provider API Vitest 5 exposes a `benchmark.provider` option that hands a plugin the raw benchmark functions and their hooks directly. Wire the V5 backend to register a provider through `test.benchmark.provider` and add the provider itself, which runs analysis and walltime modes off the registrations it receives. Drop the previous V5 seam that patched the static `TestRunner.runBenchmarks` and `Bench.prototype.add` from a setup file, along with the `WeakMap` fn-capture it needed to work around tinybench v6's private `fn` field. The provider gets the fn and options as data, so none of that interception remains. The legacy (Vitest 3/4) runner path is untouched. Point the rollup build and the config-injection test at the new provider entry. Refs COD-2931

cod-2931-prepare-compatibility-with-vitest-5

20 days ago

by

GuillaumeLagrange

1 month ago

by

GuillaumeLagrange

1 month ago

by

GuillaumeLagrange

1 month 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

1 month 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

1 month 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

2 months 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

2 months ago

Latest Branches

+30%

Support vitest 5#86

20 days ago

eec7ec7

cod-2931-prepare-compatibility-with-vitest-5

-10%

build: pin -std=c11 for instrument-hooks core.c#84

2 months ago

1999ec9

cod-2953-use-stdc11-for-instrument-hooks-in-integrations

+58%

fix: emit perf maps when not parsing the full inlining logs from V8#85

2 months ago

c88994c

cod-2987-e2e-tests-show-no-flamegraph-for-vitest

© 2026 CodSpeed Technology

Home Terms Privacy Docs