karma-coverage
karma-coverage copied to clipboard
karma-runner
HTML reporter now no longer works with browserify-istanbul in v4.0
HTML reporter now no longer works with browserify-istanbul in v4.0
I was having issues with the html reporter not outputting anything in v3.1 where the index.html would be written, but no reports would be contained inside (while the text reporter was working fine) so after seeing issue #123 I jumped to 4.0. Now I am getting the following issue:
ERROR [coverage]: [TypeError: Cannot read property 'text' of undefined]
TypeError: Cannot read property 'text' of undefined
at /home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:203:51
at Array.forEach (native)
at annotateStatements (/home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:188:33)
at HtmlReport.Report.mix.writeDetailPage (/home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:427:9)
at /home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:488:26
at SyncFileWriter.extend.writeFile (/home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/util/file-writer.js:57:9)
at FileWriter.extend.writeFile (/home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/util/file-writer.js:147:23)
at /home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:487:24
at Array.forEach (native)
at HtmlReport.Report.mix.writeFiles (/home/notnarb/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:481:23)
I made a temporary fix which now has the html reporter working properly (as far as I can tell, but certainly better than 0.3.1) - but I'm sure this isn't the proper solution
# node_modules/* - old, ~/tmp/html.js - new
diff ~/Workspace/snip/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js ~/tmp/html.js
200a201
> if (structuredText[startLine]) {
209a211
> }
231a234
> if (structuredText[startLine]) {
240a244
> }
Sorry that I can't be of too much more help than this -- I don't really understand the inner-workings of instanbul and karma-coverage, all I can determine is that for some reason a faulty startline is being communicated occasionally causing istanbul to crash and burn.
karma.conf.js
// Karma configuration
// Generated on Fri May 29 2015 17:32:24 GMT-0700 (PDT)
module.exports = function(config) {
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '',
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: ['browserify', 'mocha'],
// list of files / patterns to load in the browser
files: [
'test/**/*.js',
'src/js/vendor/**/*.js'
],
// list of files to exclude
exclude: [
],
// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: {
'test/**/*.js' : ['browserify']
},
browserify: {
debug: true,
transform: ['hbsfy', 'browserify-istanbul']
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['progress', 'coverage'],
coverageReporter: {
reporters : [
{"type": "text"},
{"type": "html", dir: 'coverages'}
]
},
// web server port
port: 9876,
// enable / disable colors in the output (reporters and logs)
colors: true,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_DEBUG,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: true,
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: ['Firefox'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: false
});
};
package.json
{
"browserify": "^10.2.1",
"browserify-istanbul": "^0.2.1",
"karma": "^0.12.35",
"karma-browserify": "^4.2.1",
"karma-chrome-launcher": "^0.1.12",
"karma-coverage": "^0.4.0",
"karma-firefox-launcher": "^0.1.6",
"karma-mocha": "^0.1.10",
}
One thing worth reiterating: I couldn't get html reports to work at all in 3.1 and now they work great with my hacky patch
Thanks for the detailed report, but I think something went wrong when you inserted the diff for the change you made, or I just don't understand what it's trying to say :(
Sorry, a vanilla diff may have not been the best choice I added a check for 'structuredText[startLine]' being true that encapsulates:
https://github.com/gotwarlost/istanbul/blob/v0.3.15/lib/report/html.js#L200 to https://github.com/gotwarlost/istanbul/blob/v0.3.15/lib/report/html.js#L209
and
https://github.com/gotwarlost/istanbul/blob/v0.3.15/lib/report/html.js#L231 to https://github.com/gotwarlost/istanbul/blob/v0.3.15/lib/report/html.js#L240
to cause it to no longer throw
ERROR [coverage]: [TypeError: Cannot read property 'text' of undefined]
where 'undefined' in this error is structuredText[startLine]
This was just a cheat to prevent istanbul from throwing an error when given an invalid start time and help isolate the issue.
I see, so the fix is actually inside the istanbul code. To be honest I have no idea how or why this is happening, maybe @gotwarlost or @davglass have an idea how this can happen and if this an issue from Istanbul or from our side
We pushed out 0.3.15 today, what version of istanbul is this erring with? And how can I reproduce it?
From the diff above it looks like he is using 0.3.15 already, but I remember that he mentioned having this issue before.
TWO different projects' collaborators responding in 2 hours? Well now I feel obligated to better reproduce the issue.
Yes, 0.3.15 (in both browserify-istanbul and karma-coverage).
cat node_modules/*/node_modules/istanbul/package.json | grep '"version"'
"version": "0.3.15",
"version": "0.3.15",
I reproduced the issue here: https://github.com/notnarb/karma-coverage-issue-157
So it appears that the issue stems from me using the 'hbsfy' browserify transform leaving me with absolutely no idea who's issue this really is haha.
So the pieces involved so far are:
- karma-coverage (which for some reason started introducing the issue when I switched to 4.0)
- istanbul
- browserify-istanbul
- hbsfy
... where do I go from here?
Switched Istanbul to 0.3.14: https://github.com/notnarb/karma-coverage-issue-157/tree/istanbul-0.3.14 got a different issue:
DEBUG [coverage]: Writing coverage to /home/notnarb/Workspace/karma-coverage-157/coverages/Firefox 38.0.0 (Ubuntu 0.0.0)
ERROR [coverage]: [TypeError: Cannot set property 'covered' of undefined]
TypeError: Cannot set property 'covered' of undefined
at /home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:174:66
at Array.forEach (native)
at annotateLines (/home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:172:28)
at HtmlReport.Report.mix.writeDetailPage (/home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:406:9)
at /home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:472:26
at SyncFileWriter.extend.writeFile (/home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/util/file-writer.js:57:9)
at FileWriter.extend.writeFile (/home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/util/file-writer.js:147:23)
at /home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:471:24
at Array.forEach (native)
at HtmlReport.Report.mix.writeFiles (/home/notnarb/Workspace/karma-coverage-157/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:465:23)
which matches what is reported by this comment https://github.com/karma-runner/karma-coverage/issues/123#issuecomment-110363547
have same error with
Cannot read property 'text' of undefined
As temp solution, I wrapped all places in istanbul/lib/report/html.js with errors Ex: old:
if (type === 'no') {
if (endLine !== startLine) {
endLine = startLine;
endCol = structuredText[startLine].text.originalLength();
}
text = structuredText[startLine].text; //<------HERE is the error!!!
text.wrap(startCol,
openSpan,
startLine === endLine ? endCol : text.originalLength(),
closeSpan);
}
wrapped:
if (type === 'no') {
if(structuredText[startLine]) {
if (endLine !== startLine) {
endLine = startLine;
endCol = structuredText[startLine].text.originalLength();
}
text = structuredText[startLine].text;
text.wrap(startCol,
openSpan,
startLine === endLine ? endCol : text.originalLength(),
closeSpan);
}
}
At least I have some html report
I was able to work-around this issue by setting karma's logLevel to config.LOG_DISABLE if that offers any insight. I have two projects with the exact same karma config and dependency versions. One fails while the other succeeds. I just noticed that one of the projects outputs 404 warnings from stray http requests while the other is silent.
Just tried that
~/Workspace/karma-coverage-157$ karma start
LOG: 'a'
LOG: 'b'
Firefox 38.0.0 (Ubuntu 0.0.0) LOG: 'a'
Firefox 38.0.0 (Ubuntu 0.0.0) LOG: 'b'
Chromium 43.0.2357 (Ubuntu 0.0.0): Executed 2 of 2 SUCCESS (0.125 secs / 0.115 secs)
Firefox 38.0.0 (Ubuntu 0.0.0): Executed 2 of 2 SUCCESS (0.051 secs / 0.003 secs)
TOTAL: 4 SUCCESS
BUT
~/Workspace/karma-coverage-157$ ls
karma.conf.js node_modules npm-shrinkwrap.json package.json README.md src test
no html reports get made at all (I assume it just fails silently?)
My project uses browserify with babelify to convert es6 to es5, karma-coverage 0.2.7 and babel-istanbul 0.2.10 for coverage reporting. I get the same error (although at a different line):
TypeError: Cannot read property 'text' of undefined
at /home/ubuntu/workspace/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:236:45
at Array.forEach (native)
I used the @akoval 's fix, but then I get incorrect coverage report - it sais that there is uncovered code at a nonexisting line.
Investigated a bit and found out that babel in order to convert the code introduces an extra function:
function factory() {
return {
method: args => method(args)
}
}
function method() {}
is converted to
function factory() {
return {
method: (function (_method) {
function method(_x) {
return _method.apply(this, arguments);
}
method.toString = function () {
return _method.toString();
};
return method;
})(function (args) {
return method(args);
})
};
}
function method() {}
I guess karma-coverage wants to mark method.toString as uncovered by the unit tests but fails because it doesn't exist in the original code.
The workaround, for my progect, was to change the name of the method function
function factory() {
return {
method: args => methodFunc(args)
}
}
function methodFunc() {}
so that babel won't generate it's weird wrapper function and add .toString method.
I think the problem is with the environment 'NODE_ENV' when i set it to 'test' it give me the text error. When i change it to 'testing' it works fine. Hope this helps in fixing the issue
@blazzy -- +1 -- worked for me. here is my karma.conf + package.json
// Karma configuration
// Generated on Thu Jul 23 2015 23:21:04 GMT-0400 (EDT)
module.exports = function (config) {
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '',
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: ['browserify', 'tap'],
// list of files / patterns to load in the browser test runner
files: [
{pattern: './test/**/*.js', included: true},
{pattern: './lib/**/*.js', included: false}
],
// list of files to exclude
exclude: [],
// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: {
// create the ES5 equivalents of these ES6 modules (these are loaded asynchronously)
'./lib/**/*.js': ['browserify', 'coverage'],
// create the ES5 versions of the tests written in ES6 (these are included in the test runner page)
'./test/**/*.js': ['browserify', 'coverage']
},
browserify: {
debug: true,
transform: ['babelify', 'browserify-istanbul']
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['tape', 'coverage'],
coverageReporter: {
dir: './reports/coverage',
reporters: [
// reporters not supporting the `file` property
{type: 'html', subdir: 'html'},
{type: 'lcov', subdir: '.'},
{type: 'text', subdir: '.', file: 'text.txt'},
{type: 'text-summary', subdir: '.', file: 'text-summary.txt'}
]
},
// web server port
port: 9876,
// enable / disable colors in the output (reporters and logs)
colors: true,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_INFO,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: false,
customLaunchers: {
'ChromeES6': {
base: 'Chrome',
flags: ['--enable-javascript-harmony']
},
'ChromeCanaryES6': {
base: 'ChromeCanary',
flags: ['--enable-javascript-harmony']
}
},
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
//browsers: ['ChromeES6', 'Chrome', 'ChromeCanaryES6', 'ChromeCanary', 'Firefox', 'Safari', 'PhantomJS'],
browsers: ['Chrome'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: true
});
};
{
"name": "",
"version": "0.0.0",
"description": "7",
"main": "lib/cli/main.js",
"dependencies": {
"babel": "^5.5.5",
"core-js": "^0.9.8",
"rsvp": "^3.0.18",
"templeton": "^2.1.1",
"xhttp": "^0.0.6",
"cookie-parser": "^1.3.5",
"body-parser": "^1.12.4",
"express": "^4.12.4",
"pem": "^1.7.2",
"request-promise": "^0.4.2"
},
"devDependencies": {
"babel-eslint": "^3.1.26",
"babel-istanbul": "^0.2.10",
"babelify": "^6.1.0",
"browserify": "^10.1.3",
"browserify-istanbul": "^0.2.1",
"eslint": "^0.21.0",
"isparta": "^3.0.3",
"karma": "^0.13.3",
"karma-browserify": "^4.2.1",
"karma-chrome-launcher": "^0.2.0",
"karma-coverage": "douglasduteil/karma-coverage#next",
"karma-firefox-launcher": "^0.1.6",
"karma-phantomjs-launcher": "^0.2.0",
"karma-safari-launcher": "^0.1.1",
"karma-sourcemap-loader": "^0.3.5",
"karma-tap": "^1.0.3",
"karma-tape-reporter": "^1.0.3",
"minifyify": "^7.0.3",
"phantomjs": "^1.9.17",
"plato": "^1.5.0",
"tape": "^4.0.1"
},
"scripts": {
"lint": "eslint -c ./.eslintrc ./lib/**/*.js",
"test": "karma start",
"start": "babel-node ./lib/server/main.js",
"metrics:compile_source": "./node_modules/.bin/babel --optional runtime lib/ --out-dir ./build/metrics/lib",
"metrics": "npm run metrics:compile_source && ./node_modules/.bin/plato -r -l .eslintrc -d ./reports/metrics ./build/metrics/lib"
},
}
Realized that the LOG_DISABLE hack, just hides the error. The full report is never generated. What you wind up with is a report that looks complete, but if you drill down to each of the files, you will hit 404's on any of them that were not parsed due to the error. minal2709's NODE_ENV patch did not work either. here is the output of the error:
05 08 2015 01:46:55.407:ERROR [coverage]: [TypeError: Cannot read property 'text' of undefined] TypeError: Cannot read property 'text' of undefined at /myproj/node_modules/istanbul/lib/report/html.js:203:51 at Array.forEach (native) at annotateStatements (/myproj/node_modules/istanbul/lib/report/html.js:188:33) at HtmlReport.Report.mix.writeDetailPage (/myproj/node_modules/istanbul/lib/report/html.js:423:9) at /myproj/node_modules/istanbul/lib/report/html.js:484:26 at SyncFileWriter.extend.writeFile (/myproj/node_modules/istanbul/lib/util/file-writer.js:57:9) at FileWriter.extend.writeFile (/myproj/node_modules/istanbul/lib/util/file-writer.js:147:23) at /myproj/node_modules/istanbul/lib/report/html.js:483:24 at Array.forEach (native) at HtmlReport.Report.mix.writeFiles (/myproj/node_modules/istanbul/lib/report/html.js:477:23) at /myproj/node_modules/istanbul/lib/report/html.js:479:22 at Array.forEach (native) at HtmlReport.Report.mix.writeFiles (/myproj/node_modules/istanbul/lib/report/html.js:477:23) at HtmlReport.Report.mix.writeReport (/myproj/node_modules/istanbul/lib/report/html.js:561:14) at /myproj/node_modules/karma-coverage/lib/reporter.js:141:24 at /myproj/node_modules/karma/lib/helper.js:82:7
Any ideas on what sort of a fix this needs -- is it actually an issue with karma-coverage, or is it with istanbul/isparta?
Are there any news on this? My work-around is to switch to the text-reporter, but i'd love to have the html-reporter working again.
@blazzy's workaround simply hides the error message. The error still occurs and execution still short-circuits, resulting in an incomplete, erroneous coverage report.
The issue appears to be a result of the way Istanbul handles (or doesn't) source maps. There is a fix implemented in the Istanbul repo, but it hasn't been merged into the master branch yet. I explicitly installed Istanbul directly from that GitHub branch (source-map) and it worked like a charm.
For now, you can install the fixed Istanbul branch via npm install --save-dev gotwarlost/istanbul#source-map. You'll then need to reinstall karma-coverage (and any other package that utilizes Istanbul as a dependency) to ensure it utilizes the fixed version of Istanbul rather than a locally installed dependency.
@SpenceDiNicolantonio is correct. The reason the HTML reporter is failing is most probably due to the fact that it is being given the transformed version of the source and the original source file name and it can't find the lines there. The source map branch has support for handling this correctly via source maps.
The problem is that the source map implementation is a proof of concept which muddies the istanbul APIs and makes them unmaintainable. And I have deadlines in my day job that I need to handle. Will get to it as soon as I can.
Thanks for the solution branch for this @SpenceDiNicolantonio. That helps a lot. :+1:
@SpenceDiNicolantonio -- i am not able to get it to work, even with the modified gotwarlost/istanbul#source-map package. Are you/anyone able to share working karma.conf with this setup?
Sure, we're doing this with the fix branch installed:
const istanbul = require( 'browserify-istanbul' ),
isparta = require( 'isparta' );
module.exports = function( config ) {
config.set( {
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '',
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: [
'browserify',
'mocha',
'chai',
'sinon',
'phantomjs-shim'
],
// list of files / patterns to load in the browser
files: [
'spec/**/*.js'
],
// list of files to exclude
exclude: [
],
// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: {
'app/**/*.js': [ 'browserify' ],
'spec/**/*.js': [ 'browserify' ]
},
// https://github.com/Nikku/karma-browserify
browserify: {
debug: true,
bundleDelay: 1000,
extensions: [ '.js', '.jsx' ],
transform: [
'babelify',
istanbul( {
ignore: [ '**/spec/**', '**/fixture/**' ]
} )
]
},
client: {
mocha: {
args: '--debug-brk'
}
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: [
'coverage',
'junit',
'mocha'
],
// reporter options - full, autowatch, minimal
mochaReporter: {
output: 'full'
},
// unit tests JUNIT reporter for Bamboo
junitReporter: {
outputFile: 'test-results.xml',
suite: ''
},
// coverage reporter
coverageReporter: {
instrumenters: { 'istanbul-react': require( 'istanbul-react' ) },
instrumenter: {
'app/**/*.{js,jsx}': [ 'istanbul-react', isparta ]
},
reporters: [
{ type: 'text' },
{ type: 'html', dir: 'coverage', subdir: 'reports' }
]
},
// web server port
port: 9876,
// enable / disable colors in the output (reporters and logs)
colors: true,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_INFO,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: false,
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: [ 'PhantomJS' ],
// browsers: [ 'Chrome' ],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: true
} );
};
Also, there is an issue in the instanbul repo too: https://github.com/gotwarlost/istanbul/issues/429
Hi,
I use the gotwarlost/istanbul#source-map trick with babelify 7.2.0 but with this setup the error appear:
ERROR [coverage]: [TypeError: Cannot read property 'text' of undefined]
TypeError: Cannot read property 'text' of undefined
at /Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:288:53
at Array.forEach (native)
at annotateBranches (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:255:30)
at HtmlReport.Report.mix.writeDetailPage (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:426:9)
at /Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:489:26
at SyncFileWriter.extend.writeFile (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/util/file-writer.js:57:9)
at FileWriter.extend.writeFile (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/util/file-writer.js:147:23)
at /Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:488:24
at Array.forEach (native)
at HtmlReport.Report.mix.writeFiles (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:482:23)
at /Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:484:22
at Array.forEach (native)
at HtmlReport.Report.mix.writeFiles (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:482:23)
at HtmlReport.Report.mix.writeReport (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/node_modules/istanbul/lib/report/html.js:566:14)
at writeReport (/Users/cs/workspace/access-control-center/node_modules/karma-coverage/lib/reporter.js:62:16)
at /Users/cs/workspace/access-control-center/node_modules/karma-coverage/lib/reporter.js:288:11
Does anybody the newest babelify running with karma-coverage?
Thanks, Chris
As this labeled "PR please", is there a pointer to where the problem might lie, so me of someone else can take a stab at actually creating a PR? This bug pretty much breaks my workflow so I'd at least try if to fix it if I knew where to start.
I am having the same problem using Browserify and Babel along with istanbul and as far as I can see the line numbers of the coverage is off of about 6 lines. it would make sense that istanbul is having a problem with the lines if the source it is looking at is not correct. But what I don't know right now is if the sourcemap is working or not.
This worked before Babel 6 though.
Personally I am using these modules:
{
"babel-cli": "^6.1.1",
"babel-core": "^6.0.20",
"babel-istanbul": "^0.4.1",
"babelify": "^7.2.0",
"browserify": "^12.0.1",
"browserify-istanbul": "^0.2.1",
"browserify-shim": "^3.8.11",
"istanbul": "gotwarlost/istanbul.git#source-map",
"karma": "^0.13.15",
"karma-browserify": "^4.4.0",
"karma-coverage": "douglasduteil/karma-coverage#next",
"karma-sourcemap-loader": "^0.3.6",
... And mocha and friends ...
}
