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 🙏

© 2024 – Pkg Stats / Ryan Hefner

npmbench

v0.0.4

Published

benchmark each release of a node module published on npm against each other release using a small command line tool

Downloads

8

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

dtrejodtrejo

Keywords

Readme

npmbench

A command line tool to examine your code's performance over various releases.

  • Downloads all releases
  • runs the specified js file against all versions
  • shows you a graph of your module's performance (Note: this may or may not work depending on how your javascript file prints its results to stdout).

Gotchas

  • specialized to read ops/sec from stdout
  • releases with incompatible APIs will likely throw errors when the js file is run, and will be omitted aka set to 0. If the error is more serious, things may just crash and I'm sorry.

Usage

Example usage for testing the redis package, and running the file multi_bench.js against each release:

npmbench redis multi_bench.js

Ops/sec
*****      ( XX ops/sec ) v0.0.1
*******    ( XX ops/sec ) v0.0.2
********   ( XX ops/sec ) v0.0.3
****       ( XX ops/sec ) v0.0.4
********** ( XX ops/sec ) v0.0.5

Niceties of npmbench's approach

  • Output from each run of your js file will be put into a file named [email protected].
  • These are then parsed into json files which are put at [email protected]
  • makes it easy to run your own analysis of the numbers after all the benches have been run, or just grep through it :)

Why is this nice? Makes it easy to write your own parser for the output.

TODO:

  • skip running a given bench if there is already a .txt file there for it
  • graph the graph with something fancier than asterisks on the command line.
  • split out the parsing stage so people can supply their own output parser (too much work?)
  • actually write the thing that aggregates all the json blobs into one graphable json blob