fix: parse errors in coverage command (#156837)

Fixes #155615
microsoft · Aug 5, 2022 · 39e77d7 · 39e77d7
1 parent 31cc3b8
commit 39e77d7
Show file tree

Hide file tree

Showing 3 changed files with 277 additions and 135 deletions.
diff --git a/package.json b/package.json
@@ -170,11 +170,11 @@
     "husky": "^0.13.1",
     "innosetup": "6.0.5",
     "is": "^3.1.0",
-    "istanbul-lib-coverage": "^3.0.0",
-    "istanbul-lib-instrument": "^4.0.0",
+    "istanbul-lib-coverage": "^3.2.0",
+    "istanbul-lib-instrument": "^5.2.0",
     "istanbul-lib-report": "^3.0.0",
-    "istanbul-lib-source-maps": "^4.0.0",
-    "istanbul-reports": "^3.0.0",
+    "istanbul-lib-source-maps": "^4.0.1",
+    "istanbul-reports": "^3.1.5",
     "lazy.js": "^0.4.2",
     "merge-options": "^1.0.1",
     "mime": "^1.4.1",

diff --git a/test/unit/coverage.js b/test/unit/coverage.js
@@ -28,7 +28,12 @@ exports.initialize = function (loaderConfig) {
 		} catch (err) {
 			// missing source map...
 		}
-		return instrumenter.instrumentSync(contents, source, map);
+		try {
+			return instrumenter.instrumentSync(contents, source, map);
+		} catch (e) {
+			console.error(`Error instrumenting ${source}: ${e}`);
+			throw e;
+		}
 	};
 };