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

gulp-release-easy

v1.0.5

Published

Simpliest gulp plugin for automated releasing and publishing to NPM ever

Readme

NPM

gulp-release-easy

A gulp plugin that helps you automate releasing and publishing to NPM easy than ever! All you need to do is issue gulp release. I've used it in my pet project as well as used it to publish itself!

Usage

npm install gulp-release-easy --save-dev

var gulp = require('gulp');
require('gulp-release-easy')(gulp);

You can also pass along a config object where you can define your chosen release branch (by default, it will be 'master');

// Set 'develop' as the release branch
require('gulp-release-easy')(gulp,{releaseBranch:'develop'});

See more about what you can pass in the config object below.

All you need to know is just simply issue:

gulp release

Instead of manually: pull changes from release branch -> bump version -> commit -> tag -> push to release branch -> publish to NPM

or a full version:

gulp release -b my-release-branch --minor --bower

Options

Instead of typing parameters every time you issue gulp release, you can set them by default by passing the config object and then simply gulp release:


// all the properties below are optional
require('gulp-release-easy')(gulp,{
	releaseBranch:'develop', // Set 'develop' as the release branch 'master' is default
	releaseType: 'minor', // or 'marjor' or 'patch' (which is default)
	excludeTask: 'publish', // this will do all the tasks but NOT publishing to NPM
	origin: 'origin', //origin branch, default is 'origin'. Command line equivelence is `-o origin-branch-name`
	pkg: 'package.json'
});

If you want instead want to type in the verbose version of your gulp release, you can pass along some parameters, this will override the config options you passed in gulpfile.js:

option | meaning -----------------|------------------------------------- gulp-release -b branch-name | your release branch gulp-release --minor (or -v minor) | release minor (the same thing with patch and major, default is patch) gulp-release --bower (or --npm or --node) | choose the package file that you want to update (either npm or bower, default is npm) gulp-release -x taskName | exclude the task during the releasing process, currently only 'publish' can be exceluded

run gulp -T for a list of available commands