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 🙏

© 2021 – Pkg Stats / Ryan Hefner




Invisible Project Template





Invisible Project Template


npm install -g @invisible/project-template
# or
yarn global add @invisible/project-template

You can also install this straight from your local repo: (Useful for testing)

yarn global add file:/path/to/@invisible/project-template


Create a new repo in github.

Make sure the name of your repo matches the directory you will create for your new project.

mkdir new-project-name
cd new-project-name


If you installed the package using yarn and when you try to run the binary init-inv-project an error is raised, the problem is probably that you don't have the real yarn global bin folder added to your PATH. To do that, simply run one of the following commands:

export PATH="$PATH:$HOME/.config/yarn/global/node_modules/.bin" # (Works only for this terminal)
# or append to your PATH on zsh config file the following (permanent):

For more information, click on the link to read the issue on Github!


  1. Create the github repo from the script
  2. Copy over our github labels
  3. Provide more options and allow for upgrading .eslint configs etc without killing package.json.