Skip to content

Releases: CodSpeedHQ/codspeed-node

v5.0.1

02 Oct 08:40
b1e4a94

Choose a tag to compare

What's Changed

Full Changelog: v5.0.0...v5.0.1

v5.0.0

26 Sep 16:12
v5.0.0
f079976

Choose a tag to compare

🎉 What's Changed

This major release brings support for our Walltime instrument, allowing you to benchmark larger pieces of code more reliably by making use of CodSpeed's Macro Runners.

Support for newer versions of tinybench and vitest have been added. Feel free to visit our node.js documentation for more details.

Lastly, we now use our common instrument-hooks implementation to interact with our instruments.

💥 Breaking Changes

  • tinybench: Support for versions below v4 has been dropped. You must upgrade to tinybench v4 or above.
    ⚠️ Since tinybench v4 drops support for CJS, ES modules are now required to use the library.

🚀 Migration Path

This is a breaking change because we updated the compatible versions of underlying benchmarking libraries.
For example, support for tinybench v3 and below has been dropped. We recommend upgrading to tinybench v4 or above.

We recommend creating a dedicated PR to update your dependencies, and create a new performance baseline for your code.

📚 Details

Full Changelog: v4.0.1...v5.0.0

v4.0.1

24 Mar 14:53
6df11e8

Choose a tag to compare

What's Changed

  • feat: vitest-plugin - allow vite 6 in peer dependencies by @belgattitude in #43

New Contributors

Full Changelog: v4.0.0...v4.0.1

v4.0.0

11 Dec 14:53
acaf925

Choose a tag to compare

🎉 What's Changed

This major release aims to reduce variance in the measurements, by updating the V8 flags and forcing other optimizations.

🚀 Migration Path

This is a breaking change and it will affect your current performance baseline. But updating will improve result stability!

We recommend you create a standalone PR to update the @codspeed/* dependencies, acknowledge the potential regressions, and merge it to update the baseline on your default branch.

📚 Details

Full Changelog: v3.1.1...v4.0.0

v3.1.1

22 Jul 10:58
f2c6054

Choose a tag to compare

What's Changed

  • fix(vitest-plugin): ensure typings are found when using exports by @adriencaccia in #35

Full Changelog: v3.1.0...v3.1.1

v3.1.0

02 Feb 15:56
46a7a56

Choose a tag to compare

🎉 What's Changed

The inimum required version of vitest is now the 1.2.2.
@codspeed/vitest-plugin now supports the before* and after* hooks from vitest 🪝
This brings a benchmark authoring experience similar to writing unit and integration tests.
Take a look at the documentation on Database instrumentation to see it in action!

Since this feature is not available yet in the actual vitest's bench API, enabling the codspeedPlugin will now always activate the CodSpeed benchmark runner instead of the default one, even in local environments.

🚀 Migration Path

We recommend you create a standalone PR to update the @codspeed/* dependencies, acknowledge the potential regressions, and merge it to update the baseline on your default branch.

📚 Details

Full Changelog: v3.0.0...v3.1.0

v3.0.0

18 Jan 15:12
eea918d

Choose a tag to compare

🎉 What's Changed

This major release brings support for the MongoDB instrumentation beta, bringing MongoDB queries insights directly in the CodSpeed report.
Documentation is coming soon...

🚀 Migration Path

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🎉!

We recommend you create a standalone PR to update the @codspeed/* dependencies, acknowledge the potential regressions, and merge it to update the baseline on your default branch.

📚 Details

Full Changelog: v2.3.1...v3.0.0

v2.3.1

17 Nov 18:01
b22974e

Choose a tag to compare

What's changed

Full Changelog: v2.3.0...v2.3.1

v2.3.0

17 Nov 17:19
5d34938

Choose a tag to compare

What's Changed

Full Changelog: v2.2.0...v2.3.0

v2.2.0

03 Aug 12:59
7f00e39

Choose a tag to compare

🎉 What's Changed

Trace generation now works out of the box with both plugins 🚀
Find the flame graphs directly in the reports on the codspeed app.

image

@codspeed/tinybench-plugin

  • call internal setupCore and teardownCore at the right places by @adriencaccia in #23

@codspeed/benchmark.js-plugin

Internals

Full Changelog: v2.1.0...v2.2.0