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 🙏

© 2020 – Pkg Stats / Ryan Hefner




Simple Choo routing framework, WIP!









This is a small route handling framework on top of Choo. Beware it's a work in progress and likely to change!!

The core feature of this framework is that it provides a function for wrapping your route handlers, mitigating the need for writing boilerplate code. It requires three arguments: view, loader and layout. You can also pass an options object as the fourth argument.

Route Rendering

The route handler wrapper renders the view for your route inside a container element, #route-container, possessing an attribute called data-route, which encodes the current route and query string. It also registers a callback via a MutationObserver that triggers when said attribute changes, in order to react as the rendered route changes. The reaction is implemented as a Choo effect handleRouteLoadedIntoDom, which gets defined in the model part of the framework.

The behaviour of the route handler is to, once it detects that the currently rendered route changes (including its query string), go through a standard procedure in order to render the corresponding view, depending on whether or not there is a data loading hook for the route:

With a Data Loading Hook

  1. Invoke the loadData hook and render the loading view.
  2. Once the loadData promise resolves, merge the resulting state subgraph into the Choo state graph. Then call the render hook in order to render the view corresponding to the route.

Without a Data Loading Hook

Just render the view corresponding to the route.

The Model

The model, defined in the model.js file of the package (import as e.g. require('@arve.knudsen/choo-routehandler/model')), defines state/effects/reducers required by the framework.


const routeHandler = require('@arve.knudsen/choo-routehandler')
const routeHandlerModel = require('@arve.knudsen/choo-routehandler/model')
const app = require('choo')

const loading = require('./loading')
const layout = require('./layout')

  state: {...}

app.router({default: '/404',}, [
  ['/404', routeHandler(notFoundView, loading, layout),],
  ['/', routeHandler(mainView, loading, layout),],