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 🙏

© 2024 – Pkg Stats / Ryan Hefner

releasr

v1.3.6

Published

Releasr is a tool to help you push releases using Git.

Downloads

10

Readme

Releasr!

Releasr is a tool to help you push releases using Git.

Install

npm install -[D|g] releasr.js

Usage

npx releasr.js <major|minor|patch>

Usage: releasr.js [options] <release-type>

Options:
  -V, --version                      output the version number
  -b, --trunk-branch <trunk-branch>  The branch that you must contain the current HEAD commit to make a release (default: "master")
  -G, --no-gitlab                    if specified, do not attempt to merge versioning branch with trunk branch
  -r, --remote <remote>              Name of remote (default: "origin")
  -c, --changelogFile <filename>     Changelog filename (default: "CHANGELOG.md")
  -d, --debug                        Debug mode
  -h, --help                         display help for command

If installed globally the releasr.js command will become available to the port. If installed locally then you can run npx run releasr.js from your project root.

Releasr will look for a .releasrrc file in your home folder, and current directory. There is an example .releasrrc included in the repository root.

Releasr will

  • Make sure we have the latest tags available to us
  • Check to see if the current commit is available in the trunk branch
  • Creates a versioning branch, from the current HEAD
  • Generate a changelog (using generate-changelog)
  • Bump the version as appropriate (major, minor or patch) (See npm version)
  • Push the versioning branch to the remote
  • If Gitlab credentials supplied Merge the remote versioning branch with the remote trunk branch
  • If a Dockerfile is present and image / container repository is defined Build and push the docker image to the remote container
  • Clean up (remove versioning branches, pull down newly merged trunk branch)