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-github-fetch

v0.1.2

Published

Fetch assets from github repositories releases using Github cool API

Readme

grunt-github-fetch

Fetch assets from github repositories releases using Github cool API

Getting Started

This plugin requires Grunt ~0.4.4

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-github-fetch --save-dev

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

grunt.loadNpmTasks('grunt-github-fetch');

The "github_fetch" task

Why

Let's say divided one big monolithic piece of code into cool services in different repositories (private or not). You might need to be able to maintain the "link" between the services or part of services concording to the right tags and version. Github provides a nice API to deal with assets (files you uploaded when you released), but humanly, it's kind of annoying to do some curl or whatever etc... Here is one possible way to do it.

Overview

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

grunt.initConfig({
  github_fetch: {
    repo_1: {
        options: {
        // Task-specific options go here.
        }
    },
    repo_2: {
        options: {
        // Task-specific options go here.
        }
    }
  },
});

Options

Consider a classic github repository URL : //github.com/:owner/:repository

options.repository

Type: String REQUIRED

The targeted repository name

options.owner

Type: String REQUIRED

The owner of the targeted repository

options.tag

Type: String REQUIRED

The tag of the targeted release (example tag : "v1.0")

options.filename

Type: String REQUIRED

The name of the file you want to retrieve from the target

options.tokenFile

Type: String OPTIONAL (but RECOMMENDED)

Path to a json file that contains your Github Application token It should contain { "token" : "XXXX" } See below for more explanation about Github token.

options.output

Type: String OPTIONAL

Path. When specified, the retrieve asset is stored as output

About Github Application Token

Where?

https://github.com/settings/applications -> Personal Access Token

Why?

Github API requests are limited to 60 per hour for user without access token. It could be bothersome. This limit is 5000 when using a token. Moreover, if you intend to fetch assets from a private repository, this becomes REQUIRED

Tips

Gitignore your tokenFile but let the other contributors know that one is required by adding a tokenFile.json.dist file containing:

{
    "token" : "XXXXXXXXXXXXX"
}

They will then need to transform it into a valid tokenFile.json file

Some Behavior precision

If output option is not specified, the asset is downloaded as it is in your root directory (where your Gruntfile.js probably is)

** Classic example **

grunt.initConfig({
  github_fetch: {
    repo_1: { // this is important
        options: {
            tokenFile : 'token.json'
            repository : 'cool-app',
            owner: 'John',
            tag: 'v1.0',
            filename: 'script.js',
            output: 'external/script.js'
            // Fetching script.js from the tagged v1.0 release on John's cool-app repository using the github token stored in token.json
        }
    },
  },
});

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)