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

kanpai

v0.11.0

Published

🍻 Use Kanpai to publish a new version of your module!

Readme

How it works

No black magic. In semantic-release you don't have full control of project publish, semantic-release smartly analyze your commits and publish the corresponding new version.

While using kanpai (shortened to kp), you specify the version to publish instead. By running kp [patch|minor|major|x.y.z], it does following things:

  • Check git status, see if you have committed the changes and if the remote history differs.
  • Run tests, npm test by default.
  • Update package version, CHANGELOG.md, create git tag as well.
  • Push to remote git server

After that, you can publish the npm package and create GitHub Release with the kp release command. And this step can be automated via CI like GitHub Actions and CircleCI.

Install

$ npm install -g kanpai

# or use yarn
$ yarn global add kanpai

Usage

$ kp [patch|minor|major|$version|pre$type]

# custom test command, equal to npm run test:other
$ kp --test test:other

# skip test script
$ kp --skip-test

# more usages
$ kp -h

A common workflow:

# after hack something...
$ git commit -am "change the world"
$ kp

# On CI
$ kp release

Config

Some CLI flags can be configured via kanpai.json file:

{
  "test": "lint", // custom test script => npm run lint
    "commitMessage": "Release version %s"
}

Keep a CHANGELOG.md

Running kp will also generate a CHANGELOG.md file, which will include the changes since last release:

## Unreleased

No unreleased changes.

## 0.1.0

- Some commit message

As you can see this file also includes an "Unreleased" section, and upon running kp the content will be automatically replaced by the commit messages since last release, and the heading ## Unreleased will be updated to the actual version number.

You can also write the "Unreleased" section manually, the content will only be replaced by commit messages if the heading is followed by nothing or another h2 heading. In this case only the heading will be replaced.

FAQ

fatal: no upstream configured for branch 'master'

Two options:

a) git branch --set-upstream-to=origin/master master and then run git push b) git push -u origin master

License

MIT © EGOIST