Skip to content

chore: upgrade to vitest 5 and migrate benchmarks to vitest bench - #61

Merged
alexvictoor merged 1 commit into
masterfrom
chore/vitest5-bench-migration
Oct 18, 2026
Merged

alexvictoor merged 1 commit into
masterfrom
chore/vitest5-bench-migration

Conversation

@alexvictoor

Copy link
Copy Markdown
Member

Summary

  • Bump vitest from ^4.1.4 to ^5.0.5.
  • Replace the seven benny-based scripts in src/bench/*.ts with vitest bench files (src/bench/*.bench.ts), sharing a buildFilledHistogram helper in src/bench/support.ts.
  • Add an npm run bench script (vitest bench --reporter=verbose) and a benchmark.include entry in vitest.config.ts.
  • Remove the benchmark, benny and @types/benchmark dev dependencies (the lockfile shrinks by roughly 1,100 lines).
  • Exclude src/bench/** from tsconfig.build.json so bench files stay out of dist.

Notes

  • The benchmarks no longer write chart.html reports. Results print to the terminal through the verbose reporter.
  • The Histogram add bench no longer has a WASM Packed Histogram case. The other suites keep all of their cases.

Test plan

  • npm ci
  • npm run tsc
  • npm test: 196 passed, 4 skipped
  • npm run bench (not run)

🤖 Generated with Claude Code

Replace the benny/benchmark.js suites with vitest bench files
(src/bench/*.bench.ts) runnable via `npm run bench`, drop the
benchmark, benny and @types/benchmark dev dependencies, and exclude
src/bench from the build tsconfig.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alexvictoor
alexvictoor merged commit 3546829 into master Oct 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant