You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,7 @@ Here is a list of common options. Run `c8 --help` for the full list and document
43
43
|`--per-file`| check thresholds per file |`boolean`|`false`|
44
44
|`--temp-directory`| directory V8 coverage data is written to and read from |`string`|`process.env.NODE_V8_COVERAGE`|
45
45
|`--clean`| should temp files be deleted before script execution |`boolean`|`true`|
46
+
|`--experimental-monocart`| see [section below](#using-monocart-coverage-reports-experimental) for more info |`boolean`|`false`|
46
47
47
48
## Checking for "full" source coverage using `--all`
48
49
@@ -119,6 +120,23 @@ The `--100` flag can be set for the `check-coverage` as well:
119
120
c8 check-coverage --100
120
121
```
121
122
123
+
## Using Monocart coverage reports (experimental)
124
+
Monocart is an alternate library for outputting [v8 code coverage](https://v8.dev/blog/javascript-code-coverage) data as Istanbul reports.
125
+
126
+
Monocart also provides reporters based directly on v8's byte-offset-based output. Such as, `console-details` and `v8`. This removes a complex transformation step and may be less bug prone for some environments.
0 commit comments