Corey Farrell

I think this would be a neat option. Probably needs to be opt-in (disabled by default), otherwise it could cause output to scroll. I'd think that maybe when that option...

> @coreyfarrell Where did the `packages/istanbul-reports/lib/html/assets/vendor/prettify.css` file come from? I'm assuming that came from an external source or something? It was of external source but I'm not sure where it...

The option of dark vs light is set by the system, exposed by the browser. I don't support creating an option to bypass prefers-color-scheme.

For cinnamon and I assume gnome you just have to set the system theme to a dark theme. Firefox can override the system setting by switching to the dark theme...

I had not thought of this as an accessibility feature. Changes to the report are reviewed to ensure we don't reduce the contrast, and for colors used we try to...

For my own projects which do browser testing I retrieve the coverage variable from the browser before navigating to the next page, then my node.js testing helpers merge the coverage...

To merge multiple coverage objects into one you should use [istanbul-lib-coverage](https://github.com/istanbuljs/istanbuljs/tree/master/packages/istanbul-lib-coverage#readme). When NYC is used for node.js testing it uses `istanbul-lib-coverage` to merge the coverage data from multiple processes to...

Can you help me understand the use case / why you would want to do this?

When there is nothing to cover the reports display 0%. Really the coverage percentage is a divide by zero error (0 out of 0 statements covered). Does this `foo.ts` decrease...

I think N/A would be better, 100% indicates that code was found, instrumented and covered. N/A shows that no code was found and could be something different from 100%. This...