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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mills

v1.0.0

Published

Here is a brief step by step process of setting up the project for compiling.

Readme

Template

Here is a brief step by step process of setting up the project for compiling.

  1. Install NPM

  2. After installing NPM make sure that it is in your path so you can use it in the command line. It usually works out of the bag in MAC/Linux, but sometimes the path needs to be added manually in Windows.

  3. Extract the project files and cd to the directory in your command line.

  4. Run npm install to install all the dependencies for the project. This can take several minutes.

  5. Once you have the dependencies installed, to build the project and "watch" any changes in sass, js, or html partials you will run gulp in the command line.

A browser window will open of the project and you will be able to see it edited live. Whenever you make a change to the html, sass, or js, the browser automatically refreshes.

With the project running, the command line will chirp at you if there are any issues with how your code is compiled. It's very helpful!

If you want to add new svg icons you just drop them into src/svgstore. They will be automatically compiled and turned into a spritesheet. You can see how icons are used in some of the html partials. They can also be used directly in the sass.