[_andrei_]

Hey, yes it draws a lot of inspiration from mitata, but it's much tinier and with less features. I remember I was getting some less accurate measurements in browsers when I tried it (~2 years ago) and I decided to build my own and got the results I expected.

Mitata has added a ton of things since then and it's very mature, and it's built by evan so it's definitely the right choice over benchmate. I used benchmate because I can easily extend it to support the upcoming features in BenchJS.

BenchJS is for easily building shareable benchmarks, and I want to evolve it into a nice code analysis tool. It uses Babel and esbuild to transform and bundle the code before it gets evaluated, and I want to use this to extract more useful insights like the number of operations of a given type (ex. array methods), code path analysis (coverage-like), inline indicators of how much % time a line took, etc.