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

grunt-build-number

v1.0.0

Published

Grunt plugin for maintaining a build number in package.json (or other files)

Downloads

560

Readme

grunt-build-number

Grunt plugin for maintaining a build number in package.json (or another file)

Getting Started

This plugin requires Grunt.

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-build-number --save-dev

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

grunt.loadNpmTasks('grunt-build-number');

The "build_number" task

Overview

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

grunt.initConfig({
  buildnumber: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
})

(due to how grunt handles tasks this buildnumber object has to be present in the grunt configuration and has to have at least one target defined, even when using the default options. Just leave the object empty, e.g. buildnumber: { package:{} })

Options

options.field

Type: String Default value: build

A string value that is used as the name of the field in the json file to store the build number.

Usage Examples

Default Options

//Gruntfile.js
grunt.initConfig({
  buildnumber: {
    package : {}
  }
})
$ grunt buildnumber

The task will search for the package.json file in your project, load it and bump/create the build field. Output will be similar to:

Running "buildnumber:package" (buildnumber) task
>> Build number set to "463" in "package.json".

Done, without errors.

Custom Options

grunt.initConfig({
  buildnumber: {
    options: {
      field: 'buildnum',
    },
    files: ['package.json', 'bower.json']
  }
})

This will update a buildnum field inside package.json and bower.json.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Lint and test your code using Grunt.

Release History

  • v1.0.0: initial release

License

Copyright (c) 2014 Camille Reynders. Licensed under the MIT license.