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

@sethvincent/example-github-actions-node

v0.0.5

Published

This example explores using the new Github actions CI functionality for continuous testing & release

Readme

Github Actions node example

This example explores using the new Github actions CI functionality for continuous testing & release.

Overview

  • tests and linter are run on every push event
  • tests and linter are also run on every release event
  • if the release action is published and the tests and linter step passes, the module is published to npm

Release process

  • Create a git tag on the master branch using npm version major|minor|patch
  • Push the tag and the version commit to the repo with git push && git push --tags
  • Create a release for that tag through the Github UI
  • Github Actions will then run the release workflow and publish the module at that tag

Ideas for improvements

  • Creating a git tag could be triggered by an external event, such as an event created by a chat bot
  • Automatically put together release notes based on the contents of a CHANGELOG.md file

Configuration

Secret npm token

Create a secret env var called NPM_AUTH_TOKEN that has an authentication token from npm.

Follow Github's instructions for creating and using secrets to add NPM_AUTH_TOKEN.