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-gitinfo

v0.1.9

Published

Get Git info from a working copy and populate grunt.config with the data

Downloads

21,290

Readme

grunt-gitinfo

Get Git info from a working copy and populate grunt.config with the data

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-gitinfo --save-dev

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

grunt.loadNpmTasks('grunt-gitinfo');

The "gitinfo" task

Overview

Inspired by grunt-svninfo. In your project's Gruntfile, add a section named gitinfo to the data object passed into grunt.initConfig(). Executing the task will populate grunt.config.gitinfo with repository data described below. You can use gitinfo object in your build as e.g. <%= gitinfo.local.branch.current.SHA %>. The resulting gitinfo object has the following structure:

{
    local : {
        branch : {
            current : {
                SHA               : "Current HEAD SHA",
                shortSHA          : "Current HEAD short SHA",
                name              : "Current branch name",
                currentUser       : "Current git user",
                lastCommitTime    : "Last commit time",
                lastCommitMessage : "Last commit message",
                lastCommitAuthor  : "Last commit author",
                lastCommitNumber  : "Last commit number"
            }
        }
    },
    remote : {
        origin : {
            url : "Branch Url"
        }
    },
    (custom command values)
}

Options

cwd

Type: String

Allows to specify a cwd (current working directory) path repository. The default directory is the where you run grunt from ('.').

Example:

gitinfo: {
    options: {
        cwd: './myproject/ishere'
    },
    ...
}

Custom commands

Type: Object

Allows to specify a custom git command.

Example:

gitinfo: {
    commands: {
        'my.custom.command' : ['arg1', 'arg2', (...)] // git arg1 arg2 (...)
    }
}

This will populate <%= gitinfo.my.custom.command %> with git arg1 arg2 output.

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

0.1.9

  • #35 Update peerDependencies

0.1.8

  • #30 Update peerDependencies to support Grunt 1.0

0.1.7

  • #19 Added the command lastCommitMessage
  • #18 Update dependencies
  • #17 Fix JSHint warnings about if-else braces

0.1.6

  • Removed tag from commands list
  • #13 Adding lastCommitNumber command
  • #12 Logging through grunt.log API
  • #9 Extend existing gitinfo config