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

v0.0.10

Published

Instruments files with Blanket.js

Readme

grunt-blanket

Instruments files with Blanket.js in the "traditional" manner of creating physical instrumented copies of the files. Ideal for situations where you'd like to use mocha or browser based test coverage, but don't want to have to use a non-JS solution to instrument your files.

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

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

grunt.loadNpmTasks('grunt-blanket');

The "blanket" task

Overview

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

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

Options

Only the data-cover-flags from Blanket are accepted as options. They may add some needed functionality, but you likely won't need them.

Usage Examples

Default Options

In this example, our source files are contained in 'src' and we want them to be instrumented and then stored in 'src-cov'.

NOTE: The src parameter MUST be a directory. Patterns like "src/*.js" will fail. Individual files can be included or excluded via the pattern option.

grunt.initConfig({
  blanket: {
    options: {
      // pattern: "**/*interesting*.js"
      pattern: "!src/some/dir/to/exclude/**/*"
    },
    files: {
      'src-cov/': ['src/'],
    },
  },
})

Test runner

Please update the path in your test runner to point to the instrumented files. This can be automated through a different grunt task, or coded manually.

Also, the coverage details are only viewable with the mocha reporter, for now. A copy of the blanket reporter may be made available at a later date.