v2.0.0

🎉 What's Changed

• Flame graph generation is now supported with Node 16+, allowing more granularity in the performance reports. More details can be found in the documentation.
• Each benchmark is now warmed up a single time before each run to reduce the flakiness and the side effects related to the order in which the benchmarks are run.
• The uri of the benchmarks now contains the exact path of the file where they are added, either with bench.add(...) (with @codspeed/tinybench-plugin) or suite.add(...) (with @codspeed/benchmark.js-plugin). Before, they were all defined under the file where the bench or suite variable was instantiated. This feature enables better code splitting of your different benchmarks, read more on this in our documentation about bigger projects. This means that your existing benchmarks might be dropped in favor of new ones with correct URIs. Just acknowledge the dropping in the CodSpeed app, and you are good to go!

🚀 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

Features

• feat: expose the v8 flags from @codspeed/core by @art049 in PR #13
• feat/callgraph generation by @art049 in PR #12
• feat/support node 18 by @adriencaccia in PR #11
• feat: enable stack trampoline with v8 flags by @art049 in PR #14
• perf: warmup V8 symbols generation of the performance map by @adriencaccia in PR #15
• feat: custom perf map generation by @art049 in PR #16

Fixes

• fix: fix file path when running in ESM by @art049 in PR #10

Internals

• ci: disable benchmarks concurrency by @art049 in PR #17

---

Full Changelog: v1.1.0...v2.0.0