Workaround inaccurate Jest coverage reporting

package.json

@@ -43,7 +43,6 @@
     "cron:report-lighthouse-results": "node dist/scripts/cronjobs/reportLighthouseResults.js",
     "db:migrate": "node -r dotenv-flow/config node_modules/knex/bin/cli.js migrate:latest --knexfile src/db/knexfile.js",
     "db:rollback": "node -r dotenv-flow/config node_modules/knex/bin/cli.js migrate:rollback --knexfile src/db/knexfile.js",
-    "prepare": "husky",
     "storybook": "storybook dev -p 6006",
     "build-storybook": "npm run build-glean && npm run build-nimbus && storybook build",
     "create-location-data": "node src/scripts/build/uploadAutoCompleteLocations.js",
@@ -59,7 +58,9 @@
     "build-glean-backend-docs": "glean translate src/telemetry/backend-metrics.yaml --format markdown --output docs/telemetry/backend",
     "loadtest:hbibp-webhook": "echo 'Ensure k6 is installed; see:\n\thttps://grafana.com/docs/k6/latest/set-up/install-k6/\n' && k6 run src/scripts/loadtest/hibp.js",
     "validate-nimbus": "sh src/scripts/build/validate-nimbus-file.sh",
-    "lighthouse": "lhci autorun"
+    "lighthouse": "lhci autorun",
+    "prepare": "husky",
+    "postinstall": "patch-package"
   },
   "repository": {
     "type": "git",
@@ -162,6 +163,7 @@
     "jest-fail-on-console": "^3.3.1",
     "lint-staged": "^15.4.3",
     "mjml-browser": "^4.15.3",
+    "patch-package": "^8.0.0",
     "prettier": "3.5.0",
     "sass": "^1.84.0",
     "storybook": "^8.4.6",

patches/collect-v8-coverage+1.0.2.patch

@@ -0,0 +1,22 @@
+diff --git a/node_modules/collect-v8-coverage/index.js b/node_modules/collect-v8-coverage/index.js
+index 08b7853..db9ea66 100644
+--- a/node_modules/collect-v8-coverage/index.js
++++ b/node_modules/collect-v8-coverage/index.js
+@@ -13,6 +13,8 @@ class CoverageInstrumenter {
+   async startInstrumenting() {
+     this.session.connect();
+
++    await this.postSession('Debugger.enable');
++
+     await this.postSession('Profiler.enable');
+
+     await this.postSession('Profiler.startPreciseCoverage', {
+@@ -30,6 +32,8 @@ class CoverageInstrumenter {
+
+     await this.postSession('Profiler.disable');
+
++    await this.postSession('Debugger.disable');
++
+     // When using networked filesystems on Windows, v8 sometimes returns URLs
+     // of the form file:////<host>/path. These URLs are not well understood
+     // by NodeJS (see https://github.com/nodejs/node/issues/48530).

src/app/(proper_react)/(redesign)/(authenticated)/user/(dashboard)/dashboard/filterExposures.ts

@@ -14,9 +14,6 @@ export function filterExposures(
   filters: FilterState,
 ): Exposure[] {
   return exposures.filter((exposure) => {
-    /* c8 ignore start */
-    // Since the Node 20.10 upgrade, it's been marking this  as uncovered, even
-    // though it's covered by tests.
     if (filters.exposureType === "data-breach" && isScanResult(exposure)) {
       return false;
     }
@@ -46,7 +43,6 @@ export function filterExposures(
     ) {
       return false;
     }
-    /* c8 ignore stop */
 
     return true;
   });

src/app/(proper_react)/(redesign)/(authenticated)/user/(dashboard)/dashboard/fix/FixView.tsx

@@ -76,13 +76,7 @@ export const FixView = (props: FixViewProps) => {
       {props.showConfetti && <Confetti />}
       <div
         className={`${styles.fixWrapper} ${
-          isResolutionLayout
-            ? styles.highRiskDataBreachContentBg
-            : /* c8 ignore next 4 */
-              // Since the Node 20.10 upgrade, it's been intermittently marking
-              // this (and this comment) as uncovered, even though I think it's
-              // covered by tests.
-              ""
+          isResolutionLayout ? styles.highRiskDataBreachContentBg : ""
         }`}
       >
         {!props.hideProgressIndicator && (

src/app/(proper_react)/(redesign)/(authenticated)/user/(dashboard)/dashboard/fix/ResolutionContainer.tsx

@@ -32,9 +32,6 @@ type ResolutionContainerProps = {
 export const ResolutionContainer = (props: ResolutionContainerProps) => {
   const l10n = useL10n();
   const estimatedTimeString =
-    /* c8 ignore next 8 */
-    // Since the Node 20.10 upgrade, it's been intermittently marking this (and
-    // this comment) as uncovered, even though I think it's covered by tests.
     props.type === "leakedPasswords"
       ? "leaked-passwords-estimated-time"
       : "high-risk-breach-estimated-time";

src/app/(proper_react)/(redesign)/(authenticated)/user/(dashboard)/dashboard/fix/ResolutionContent.tsx

@@ -28,9 +28,6 @@ export const ResolutionContent = ({
   });
 
   const listOfBreaches =
-    /* c8 ignore next 4 */
-    // Since the Node 20.10 upgrade, it's been intermittently marking this (and
-    // this comment) as uncovered, even though I think it's covered by tests.
     exposedData &&
     exposedData.map(({ id, title, breachDate }) => (
       <li key={id} className={styles.breachItem}>

src/app/components/client/Button.tsx

@@ -69,9 +69,6 @@ export const Button = (props: ButtonProps) => {
   // If `props.isLoading` is not undefined, the contents of the link is going to
   // change into a loading indicator, which needs to be read by a screen reader:
   const ariaLiveValue: AriaAttributes["aria-live"] =
-    /* c8 ignore next 3 */
-    // Since the Node 20.10 upgrade, it's been intermittently marking this (and
-    // this comment) as uncovered, even though I think it's covered by tests.
     typeof isLoading === "boolean" ? "polite" : undefined;
 
   return typeof href === "string" ? (
@@ -83,12 +80,7 @@ export const Button = (props: ButtonProps) => {
       target={target}
       className={classes}
     >
-      {
-        /* c8 ignore next 3 */
-        // Since the Node 20.10 upgrade, it's been intermittently marking this (and
-        // this comment) as uncovered, even though I think it's covered by tests.
-        isLoading ? <Loader /> : children
-      }
+      {isLoading ? <Loader /> : children}
     </Link>
   ) : (
     <button