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

autorelease

v1.7.1

Published

Automatically release NPM packages based on commit messages.

Downloads

27

Readme

Autorelease

npm David Build Status

This is a tool to facilitate the releasing of NPM packages based on Git commit messages. This tool is designed to handled all aspects of publishing Node modules, including:

  • Release verification to ensure the environment is configured correctly before publishing.
  • Bumping package versions using semver according to commit types.
  • Generating changelogs from commit messages.
  • Tagging the commit in Git with the new version.

This is tool is highly configurable and can be adapted using plugins for almost any environment.

This is very similar to semantic-release, but it is much less opinionated. By default, this library does not assume you are using any specific remote git repository host or continuous integration platform. You can configure this tool to work with the environment of your choosing.

Install

Install using NPM:

npm i autorelease --save-dev

You can also easily setup your package for Github or Gitlab using the autorelease-setup cli. That will take you through a series of prompts and install the correct autorelease packages, including plugins.

npm i autorelease-setup -g
autorelease-setup

Basic Usage

This CLI tool is split into two parts, a before release (pre) stage and an after release (post) stage, each with a series of steps. The before release sets up the repository for release, including release verification, bumping the version number and configuring NPM. The after release stage handles changelog generation and git tagging. The steps in these stages can be configured using the .autoreleaserc file.

To release a module using this tool, add the following to you package.json after installing.

{
	"scripts": {
		"autorelease": "autorelease pre && npm publish && autorelease post"
	}
}

You will also need to generate an NPM token, either by using npm login or with a package like get-npm-token. Set the token to the NPM_TOKEN environment variable.

export NPM_TOKEN=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Now you can release your package from the command line with:

npm run autorelease

Plugins

There are currently a handful of plugins for Autorelease to configure it for common environments.