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-require-all

v1.0.0

Published

Grunt plugin to require code in order to generate accurate code coverage reports

Downloads

6

Readme

Build Status downloads npm Code Climate Test Coverage dependencies

grunt-require-all

Grunt plugin to require code in order to generate accurate code coverage reports

Getting Started

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-require-all --save-dev

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

grunt.loadNpmTasks('grunt-require-all');

Alternatively, install task-master and let it manage this for you.

The "require" task

Some code coverage libraries don't account for modules that have no test at all (and are therefore not required). This task requires any file passed via the various grunt file formats allowing you to generate accurate code coverage metrics even when some of your modules have no test at all. Often, this is a single entry-point (because of the way the node require tree works), but you can also pass multiple file patterns if necessary.

Overview

In your project's Gruntfile, add a section named require to the data object passed into grunt.initConfig(), along with one of the grunt file mechanisms. Note that dest has no meaning for this library, so you probably want to use the simpler src format.

grunt.initConfig({
  require: {
    app: {
      src: ['lib/app.js']
    },
    mutlipleFiles: {
      src: ['lib/**/*.js', '!lib/app.js']
    }
  }
});

Options

The only option currently supported is clearCache, which removes any entries added to the cache by the require task.

grunt.initConfig({
  require: {
    app: {
      options: {
        clearCache: true
      }
      src: ['lib/app.js']
    }
  }
});

Contributing

Please see the contribution guidelines.