npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

bencha

v0.0.2

Published

A simple mocha-esque ui for benchmark.js

Readme

Bencha

Mocha-esque UI for the excellent benchmark.js JavaScript benchmarking library. Records benchmark history and flags performance improvements and regressions.

Installation

npm install bencha -g

Writing Benchmarks

Create a bench directory in your project. In the bench directory, create an index.js (or index.coffee), e.g.

compare("RegExp vs String::indexOf", function(){
  var input = "demo.string"
  benchmark("RegExp", function(){
    /(\.)/.test(input);
  });
  benchmark("String::indexOf", function(){
    input.indexOf(".") > -1;
  });
});

suite("My Feature", function(){
  benchmark("foo() no arguments", function(){
    foo();
  });
  benchmark("foo() with arguments", function(){
    foo(true, false);
  });
  benchmark("bar()", function(){
    bar()
  });
});

The above defines two benchmark suites, the first is a comparison suite, comparison suites compare the results of each benchmark within the suite, declaring one the winner. The second declaration defines a suite containing three separate benchmarks that are related but not explicitly compared with each other.

To split your benchmarks into seperate files, simply require() them from the main index.js file.

Running Benchmarks

From your project root (or the directory containing the bench folder), run:

bencha

This will run the benchmarks with the default spec reporter, recording the results in bench/history.json

Run bencha --help for more options.

Licence

MIT