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

farlc

v0.0.6

Published

This is the javascript for our marketing site; when built in production, an npm package is published, which is then hosted on jsDelivr. Our webflow project can then include the script from jsDeliver.

Readme

Overview

This is the javascript for our marketing site; when built in production, an npm package is published, which is then hosted on jsDelivr. Our webflow project can then include the script from jsDeliver.

Publishing New Version

In Your Feature Branch

  • Edit version in package.json
  • Run yarn build:prod
  • Commit, push, open a PR to main branch

Merge PR

  • Check to ensure version got bumped in package.json
  • Check to ensure main.js got edited
  • Merge the PR

Automated Build Steps Occur Next

After merging to main, CI/CD takes over and does things like:

  • Publish the package to npm
  • Wait for the new package version to be available on CDN (jsdelivr)
  • Run e2e tests on dev site

Create Version In Github

This is optional, in the sense that if you fail to do it, the package will still be published. Create a new version in Github and write some notes on what was changed, just for future reference.