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-not-constantinople

v1.0.0

Published

Grunt task to easily add Istanbul code coverage using any unit-testing framework.

Downloads

22

Readme

grunt-not-constantinople Build Status

Grunt task to easily add Istanbul code coverage using any unit-testing framework.

Getting Started

This plugin requires Grunt ~0.4.4 -- Learn to use Grunt

Install the plugin with this command:

npm install grunt-not-constantinople --save-dev

Enable in your Gruntfile with:

grunt.loadNpmTasks('grunt-not-constantinople');

Quick setup

grunt.initConfig({
  not_constantinople: {
    coverage: {
      options: {
        unitTestTask: 'mochaTest'
      }
    }
  },
  mochaTest: {
    test: {
      options: {
        reporter: 'spec'
      },
      src: ['tests/**/*.js']
    }
  },
});

This uses mochaTest as an example unit testing framework, but you can use any other framework instead. You just have to specify the task to be run as a string value for the unitTestTask option.

The "not_constantinople" task

Overview

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

grunt.initConfig({
  not_constantinople: {
    customized_coverage: {
      options: {
        // REQUIRED OPTION - This should be the task that runs your unit tests (e.g. 'mochaTest', 'nodeunit:myTests', etc.)
        unitTestTask: 'myUnitTestingTask',
        // directory names to be used for your tests and coverage
        directories: {
          root: 'test',
          coverage: 'coverage',
          sourceFiles: 'app/*.js'
        },
        // Coverage thresholds. Set to false to ignore thresholds
        thresholds: {
          statements: 90,
          branches: 90,
          lines: 90,
          functions: 90
        },
        // The format of the coverage reports
        report: {
          type: 'lcov',
          print: 'detail'
        },
        // removes the contents of the coverage folder before running Istanbul
        cleanup: true
      }
    }
  },
});

All values in this example represent the default values that will be used if they are not specified.

Options

options.unitTestTask

Type: String

The string value for the Grunt task to be called to run your unit tests.

options.directories

Type: object

  • root - directory that will contain your coverage directory
  • coverage - directory that will contain all coverage files
  • sourceFiles - The source files that are used by your unit tests

options.thresholds

Type: object

  • statements - Percent coverage of statements that is considered passing
  • branches - Percent coverage of logical branches that is considered passing
  • lines - Percent coverage of lines that is considered passing
  • functions - Percent coverage of functions that is considered passing

options.report

Type: object

  • type - type of coverage report (e.g. lcov, html, etc.)
  • print

options.cleanup

Type: boolean

If true, will remove the contents of the coverage folder before running Istanbul.

options.instrumentationOptions

Type: object

Use this to pass additional Istanbul instrumentation configuration along (some values may be overridden by this task). See the "instrumentation" section of the command output from istanbul help config.

options.reportingOptions

Type: object

Use this to pass additional Istanbul reporting configuration along (some values may be overridden by this task). See the "reporting" section of the command output from istanbul help config.

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.