-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drop HTMLCov and JSONCov reporters #2356
Labels
type: chore
generally involving deps, tooling, configuration, etc.
Milestone
Comments
boneskull
added
status: waiting for author
waiting on response from OP - more information needed
type: chore
generally involving deps, tooling, configuration, etc.
labels
Jul 5, 2016
Reporter usage statistics? :) |
Well, we won't know until we break it and someone tells us, but it is a major. |
boneskull
removed
the
status: waiting for author
waiting on response from OP - more information needed
label
Jul 7, 2016
boneskull
added a commit
that referenced
this issue
Jul 7, 2016
closed via b47835b in |
A bit late, but my 2¢'s worth:
|
boneskull
added a commit
that referenced
this issue
Aug 1, 2016
mischah
added a commit
to mischah/itunes-remote
that referenced
this issue
Jul 19, 2017
The HTML coverage reporter is dropped with mocha 3.0.0 See mochajs/mocha#2356
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I mentioned this in Gitter, but both of these reporters leverage node-jscoverage, which is old and busted. It's my suspicion that these two reporters are rarely--if ever--used by anyone. Better coverage options exist in the form of istanbul, nyc, etc.
Furthermore, the only reason we have a dependency on jade/pug is these reporters.
I would like to drop them completely for v3.0.0, and remove the jade/pug dependency.
If anyone out there uses either of these reporters, please let us know!
cc @mochajs/core
The text was updated successfully, but these errors were encountered: