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

grunt-timestamp-release

v0.0.11

Published

Release a timestamped version.

Readme

grunt-timestamp-release

Release a timestamped version.

Getting Started

This plugin requires Grunt ~0.4.0

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-timestamp-release --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-timestamp-release');

The "timestamp_release" task

Overview

In your project's Gruntfile, add a section named timestampRelease to the data object passed into grunt.initConfig().

grunt.initConfig({
  timestampRelease: {
    options: {
      files: ['package.json'],
      commit: true,
      commitMessage: 'Release <%= timestamp %>',
      tag: true,
      tagFormat: 'YYYY-MM-DD--hh-mm',
      tagPrefix: '',
      tagSuffix: '',
      tagMessage: 'Release <%= timestamp %>',
      name: '',
      email: '',
      push: true,
      pushTo: 'upstream'
    }
  }
});

Options

options.files

Type: Array Default value: ['package.json']

A list of files in which to update the version.

options.commit

Type: Boolean Default value: true

Do you want the changes to be committed?

options.commitMessage

Type: String Default value: "Release <%= timestamp %>"

If options.commit, what do you want the commit message to be? <%= timestamp %> is available for reference.

options.tag

Type: Boolean Default value: true

Do you want to tag?

options.tagFormat

Type: String Default value: 'YYYY-MM-DD--hh-mm'

If options.tag, what do you want the timestamp format to be? Refer to MomentJs formats.

options.tagPrefix

Type: String Default value: ""

A string with which to prefix the tag. Example:

  timestampRelease: {
    options: {
      tagPrefix: 'beta-'
      tagFormat: 'MM-DD-YYYY'
    }
  }

  // will tag "beta-07-02-2014"

options.tagSuffix

Type: String Default value: ""

A string to add to the end of the tag. Example:

  timestampRelease: {
    options: {
      tagSuffix: '-beta'
      tagFormat: 'MM-DD-YYYY'
    }
  }

  // will tag "07-02-2014-beta"

options.tagMessage

Type: String Default value: "Release <%= timestamp %>

If options.tag, what do you want the tag message to be? <%= timestamp %>, <%= name %> and <%= email %> are available for reference. name and email can be set in the options, or through the command line.

options.name

Type: String Default value: Nothing

Set this option if you want to use name in the tagMessage without specifying it via the command line.

options.email

Type: String Default value: Nothing

Set this option if you want to use email in the tagMessage without specifying it via the command line.

options.push

Type: Boolean Default value: true

Do you want to push the changes?

options.pushTo

Type: String Default value: 'upstream'

If options.push, which repo do you want to push to?

Command Line Options

--name

Specify a name to be used in the template for commitMessage or tagMessage.
grunt timestampRelease --name "Kyrsten Kelly"

--email

Specify an email to be used in the template for commitMessage or tagMessage.
grunt timestampRelease --email "[email protected]"

--tagPrefix

Specify a string to add to the beginning of the tag.

--tagSuffix

Specify a string to add to the end of the tag.

--timestamp

Override the timestamp with a custom timestamp.
grunt timestampRelease --timestamp "2014-04-05"

--test-run

Test the release process without committing, tagging, or pushing.
grunt timestampRelease --test-run

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)