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 🙏

© 2025 – Pkg Stats / Ryan Hefner

publish-dist

v1.0.8

Published

Build and publish dist

Readme

publish-dist

Build Status

Publish dist

A CLI tool that commits and pushes dist if the last commit was not made by itself. Intended to be used as part of semantic-release.

Example package.json:

{
  "name": "my-app",
  "scripts": {
    "build": "make",
    "publish-dist": "npm run build && publish-dist",
    "semantic-release": "semantic-release pre && npm run publish-dist && npm publish && semantic-release post"
  },
  "repository": {
    "url": "https://github.com/me/my-app"
  },
  "author": "Tom Vincent <[email protected]>"
}

Usage

At minimum, publish-dist expects:

  • dist to exist before it is ran
  • The environment variable CI_USER_TOKEN to be set
  • To be using the master branch

With semantic-release

Want semantic-release to build and commit dist? Here's one approach:

  1. Initialise semantic-release with your repo as normal
  2. Generate a new GitHub access token (only repo/public_repo scope is required)
  3. Run travis env set CI_USER_TOKEN [token]
  4. Add a npm build script that's suitable for your project
  5. Add publish-dist as a dev dependency
  6. Add it as an npm deploy script
  7. Add a predeploy script that runs the npm build script
  8. Call npm run deploy after semantic-release pre

That's it!

See tlvince/tlvince-semantic-release-push-dist as a working example.

Pro tip: create a machine/bot account on GitHub (generate a access token for this account) and add it as a collaborator (with push access) to your repo. Don't forget to pass --author-name and --author-email.

Options

--author-name

The commit's author name (git config user.name). Defaults to .package.json author.

--author-email

The commit's author email (git config user.email). Defaults to .package.json author.

See also

Author

© 2015 Tom Vincent https://tlvince.com/contact

License

Released under the MIT License.