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

project-bin-publish

v1.0.31

Published

Bump the version and realize steps to help you to publish your project on github, npm.

Downloads

10

Readme

project-bin-publish

Bump the version and realize steps to help you to publish your project on github, npm.

In details

  • Fetch repository.url
  • Checkout publish.branch
  • Gather version upgrade
  • Gather release log
  • Git commit with -m <%=releaseLog%>
  • Update CHANGELOG.md
  • Update version file
  • Update package.json version property
  • Ensure .gitignore is correct
  • Git commit with <%=releaseType%> v<%=newRevision%>
  • Git tag with <%=newRevision%> -m <%=releaseLog%>
  • Git push
  • Npm publish, if the package is not private
  • If github auth is provided, create a github tag

Installation

$ npm i project-bin-publish -g

Usage

    # Publish a node project.
    project-publish
    
    # Version
    project-publish -v
    
    # Help
    project-publish -h

Configuration

On Project Root directory or within your User Home directory.

Or both to override some settings.

Create a new file .local.json and adjust this content.

{
	"profileData":{
        "github":{
          "username":"TO UPDATE",
          "password":"TO UPDATE"
        },
        "publish":{
          "branch":"master"
        }
	}
}

TODO

  • add bitbucket support
  • add new-relic support
  • add automatic test validation prior to release updgrade procedure support

How to contribute

  1. File an issue in the repository, using the bug tracker, describing the contribution you'd like to make. This will help us to get you started on the right foot.
  2. Fork the project in your account and create a new branch: your-great-feature.
  3. Commit your changes in that branch.
  4. Open a pull request, and reference the initial issue in the pull request message.

License

See the LICENSE file.