npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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




Base preset for Shaara





Expose base services and behaviour to the Kernel. The main tools when developing a JS app are a Channel (to allow pub-sub management over the application) and an EventDispatcher that decouple the UI from the logic. The mind behind the EventDispatcher is that every time the user does an action that should have effects on the model layer (like fetching data) the UI should simply dispatch such an action with parameters and let handlers take care of it on the "model" side of the application. It helps a lot keep UI classes clear and it provides a pure way of handling actions, as dependencies are injected explicitly.


  • channel : Pub-sub pattern
  • event.dispatcher : allows to dispatch event in a 1-1 way
  • logger : provide a way to hold logs with a limit to avoid exceeding memory usage


  • fetch : if provided, the request sender will use this function instead of the global fetch. Indeed this preset rely on the fetch method. If you want to use Axios or Frisbee or example, you can easily write an adapter that follows the same API as fetch. One day we will provide a function "requestImplementation" to allow changing it easily.


bindEvents : (eventDispatcher) => void

This is where you should bind your events to the dispatcher, using eventDispatcher.set(name, callback).