Grunt task to compile CoffeeScript to Javascript with JSCoverage-compatible instrumentation for code coverage
Last updated 2 years ago by mazerte .
ISC · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install grunt-coffeecov 
SYNC missed versions from official npm registry.

Grunt CoffeeCov

Build Status Dependency Status devDependency Status peerDependencies Status Coverage Status Code Climate Gitter Built with Grunt

Grunt CoffeeCov is a Grunt task wrapper for CoffeeCoverage. CoffeeCoverage compiles .coffee files to .js files and adds JSCoverage style instrumentation for the original CoffeeScript.

For more information, I recommend consulting the CoffeeCoverage README.



$ npm install grunt-coffeecov --save-dev


Create a coffeecov section in your Gruntfile.

      src: 'src/coffee'
      dest: 'lib-cov'


      path: 'relative'
        initfile: 'lib-cov/coverage.js'
      src: 'src/coffee'
      dest: 'lib-cov'

You can find a real example in Footguard, a Yeoman generator for creating a single page application with CoffeeScript, Sass, Backbone and Require. Test-footguard is an "out of the box" project generated with Footguard; you can read the Gruntfile and try the project.

If you use Mocha for your tests, I recommend using grunt-phantom-coverage-reporter. It's fully compatible with this task and Coveralls.




type: String

Path to source folder


type: String

Path to destination folder



type: String - default: '_$jscoverage'

By default, CoffeeCoverage will instrument source files with the global variable _$jscoverage. This is done to mimic JSCoverage. You can rename the variable using this option.


type: String

Specifies an "initfile" which all global initalization is written to. This is handy for testing with Mocha. If you require the initfile, then Mocha reports will show coverage of all files in your project, even files which were never required anywhere.


type: Array - default: ['node_modules', '.git']

Specifies a comma-delimited list of files and directories to exclude from processing. This defaults to ['node_modules', '.git'], since neither of these are directories you probably want to be instrumenting. If you want to also exclude your "test" directory, you might run CoffeeCoverage with ['node_modules', '.git', 'test'].


type: String - default: 'none'

Path can be given one of three different parameters:

  • none is the default - if CoffeeCoverage reads a file from "src/models/", then the instrumented code will use the filename "". This works well provided you don't reuse filenames elsewhere in your code. Note that if there is a name collision between two files in different subdirectories, CoffeeCoverage will append a something to the end of one to make it unique, otherwise coverage data from one file would interfere with data from another.
  • abbr will use abbreviated path names; a file from "src/models/" will be instrumented as "s/m/".
  • relative will use the full relative pathname; "src/models/".

Paths are always relative to the src directory provided on Grunt task.


Thanks to Benbria for CoffeeCoverage.

Current Tags

  • 1.0.0                                ...           latest (2 years ago)

10 Versions

  • 1.0.0                                ...           2 years ago
  • 1.0.0-beta                                ...           2 years ago
  • 0.1.5                                ...           6 years ago
  • 0.1.3                                ...           6 years ago
  • 0.1.2                                ...           6 years ago
  • 0.1.1                                ...           6 years ago
  • 0.1.0                                ...           6 years ago
  • 0.0.4                                ...           6 years ago
  • 0.0.3                                ...           6 years ago
  • 0.0.2                                ...           6 years ago
Maintainers (1)
Today 0
This Week 0
This Month 1
Last Day 0
Last Week 0
Last Month 10
Dependencies (2)
Dev Dependencies (9)
Dependents (1)

Copyright 2014 - 2017 © |