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

tagplusone

v0.1.0

Published

Helps you to generate incremental Git tags

Readme

tagplusone

Utility to assist with generating incremental git tags.

Motivation

If you are using a Continuous Integration service such as Codeship and you want to automatically create a new git tag for every build one option is to use the build number provided by the CI server. The drawback is this build number increments every time any of their customers run a build, so it won't be incremental for your specific build job. I created tagplusone so that I can easily generate incremental tags for each of my jobs.

Prerequisites

  • Git must be installed
  • The command must be run from within a git working directory

Installation

npm install -g tagplusone

Usage

# Purely numerical tags - if the last tag was 100 this will return 101
tagplusone

# Prefix tags e.g. with v, build etc - if the last tag was v100 this will return v101
tagplusone v

# Automtically create a tag
NEXT_TAG = `tagplusone v`
git tag -a $NEXT_TAG -m "Automatically tagged by Codeship"
git push --tags

Making Changes

If you wish to fork this repo and make changes you will probably want to install the Gulp task runner. This is used for running tests, linting and building the distribution files (transpiles from ES6 to ES5 using Babel).

npm install -g gulp

Running the Tests

gulp test

Linting

gulp lint

Building the Files

After you've made some changes:

# Run the build
gulp build

# Execute tagplusone
cd dist
node index.js [prefix]