taichi grunt-istanbul issues

taichi / grunt-istanbul

JavaScript codecoverage tool for Grunt

https://www.npmjs.com/package/grunt-istanbul

MIT License

107 stars 36 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Add newer node versions to engines, CI

#57 AndrewADev opened 1 year ago
0
Update readme.md

#56 jdoose closed 6 years ago
1
{prod} --> npm publish

#55 caseygoodhew closed 7 years ago
2
updated package.json

#54 EsrefDurna closed 7 years ago
0
Added multi-task support to instrumentation

#53 caseygoodhew closed 7 years ago
1
Is there a way to generate multiple types of test reports?

#52 scheibinger closed 7 years ago
2
Update readme

#51 shuhblam closed 7 years ago
1
Confusion with coverage numbers

#50 monikadhok opened 7 years ago
0
Avoid duplicate paths in coverage.json on Windows when using include-all-sources

#49 mgiles closed 7 years ago
1
Please upgrade your "istanbul" dependency version

#48 JamesMGreene closed 8 years ago
2
plugin config is not namespaced

#47 yomed opened 8 years ago
2
Exclude files for coverage

#46 supritashankar closed 8 years ago
1
Update peerDependencies to support Grunt 1.0

#45 gruntjs-updater closed 8 years ago
0
upgrade dependencies + support for include-all-sources

#44 yeahoffline closed 8 years ago
1
ISSUE: experimental & extensions options in instrument task throw errors

#43 reefath opened 8 years ago
0
upgrade to node 4.2

#42 ccorcos opened 8 years ago
1
Instrument task includes relative paths to source files in instrumented files instead of absolute paths

#41 epoberezkin opened 9 years ago
6
Istanbul with nightwatch.js

#40 vinitasher opened 9 years ago
5
Fix skipped files

#39 ThomasCrevoisier closed 9 years ago
1
Avoid to reinstrument every file each time

#38 ThomasCrevoisier closed 9 years ago
0
Feature : cwd option

#37 ThomasCrevoisier closed 9 years ago
2
Add a cwd option

#36 ThomasCrevoisier closed 9 years ago
0
Updated READme.md

#35 wettowelreactor closed 9 years ago
1
add optional instrumenter argument

#34 sethpollack closed 9 years ago
4
Set nue to use version 0.6.0, fixes #32

#33 mrfelton closed 9 years ago
1
grunt-istanbul 0.4.0 install failure

#32 nishantmc closed 9 years ago
10
looks like 'instrument' is broken

#31 miranda820 closed 9 years ago
5
Standardize output and use standard FS functions

#30 mgeisler closed 9 years ago
3
Removal of multiple OK messages

#29 madfiles closed 9 years ago
1
3rd party integration

#28 stevepeak opened 9 years ago
1
FATAL ERROR: JS Allocation failed - process out of memory

#27 RASRID opened 9 years ago
1
Reporting on files that are not touched at all by tests

#26 abelnation closed 10 years ago
1
Bump istanbul?

#25 dominykas closed 9 years ago
0
excludes ignored

#24 Stewartarmbrecht closed 10 years ago
1
Fatal error when running store coverage task

#23 thgil opened 10 years ago
1
Error: EMFILE, too many open files

#22 linusthe3rd opened 10 years ago
3
Allow arrays of coverage types to be generated

#21 JHunz closed 10 years ago
1
Test files in different folder, not stored at common location

#20 vkadam opened 10 years ago
2
Fixes nue dependancy

#19 weavermj closed 10 years ago
1
Add documentation for how to use grunt-istanbul

#18 gregjopa closed 10 years ago
3
Updated istanbul semver

#17 wheresrhys closed 10 years ago
1
What does reloadTasks do with regard to __coverage__?

#16 wheresrhys closed 1 month ago
7
Better usage documentation in README

#15 paazmaya closed 10 years ago
4
Giving results for files that does not have corresponding test

#14 athieriot opened 11 years ago
5
Fix "lazy: true" option sometimes not calling flowEnd

#13 rowanbeentje closed 11 years ago
2
Provide an option lazily instrument javascript files (if the file hasn't been modified, don't reinstrument)

#12 matthew-andrews closed 11 years ago
3
README.md !

#11 davidlinse closed 11 years ago
2
functions are not covered

#10 4kochi closed 11 years ago
2
Create the JSON report file + the HTML report in a single task

#9 mathiasbynens closed 11 years ago
6
Best practice to configure test cases to run against instrumented code

#8 jalateras closed 11 years ago
5