@jsenv/test 1.2.4 → 1.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2,7 +2,10 @@
2
2
  const originalEmit = process.emit;
3
3
  process.emit = (event, error) => {
4
4
  if (event === "warning" && error.name === "ExperimentalWarning") {
5
- if (error.message.includes("--experimental-loader") || error.message.includes("Custom ESM Loaders is an experimental")) {
5
+ if (
6
+ error.message.includes("--experimental-loader") ||
7
+ error.message.includes("Custom ESM Loaders is an experimental")
8
+ ) {
6
9
  return false;
7
10
  }
8
11
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jsenv/test",
3
- "version": "1.2.4",
3
+ "version": "1.3.1",
4
4
  "license": "MIT",
5
5
  "repository": {
6
6
  "type": "git",
@@ -34,10 +34,10 @@
34
34
  },
35
35
  "dependencies": {
36
36
  "@jsenv/abort": "4.2.4",
37
- "@jsenv/ast": "4.0.3",
37
+ "@jsenv/ast": "4.1.0",
38
38
  "@jsenv/filesystem": "4.2.3",
39
- "@jsenv/log": "3.3.5",
40
- "@jsenv/plugin-supervisor": "1.1.0",
39
+ "@jsenv/log": "3.4.0",
40
+ "@jsenv/plugin-supervisor": "1.1.1",
41
41
  "@jsenv/urls": "2.0.0",
42
42
  "@jsenv/url-meta": "8.1.0",
43
43
  "@jsenv/uneval": "1.6.0",
@@ -47,7 +47,7 @@
47
47
  "istanbul-lib-instrument": "5.2.1",
48
48
  "istanbul-lib-report": "3.0.0",
49
49
  "istanbul-reports": "3.1.5",
50
- "@paralleldrive/cuid2": "2.2.0",
50
+ "@paralleldrive/cuid2": "2.2.1",
51
51
  "@c88/v8-coverage": "0.1.1",
52
52
  "strip-ansi": "7.1.0",
53
53
  "wrap-ansi": "8.1.0",
@@ -21,7 +21,7 @@ export const relativeUrlToEmptyCoverage = async (
21
21
  const { metadata } = await applyBabelPlugins({
22
22
  babelPlugins: [babelPluginInstrument],
23
23
  input: content,
24
- inputIsJsModule: false,
24
+ inputIsJsModule: true,
25
25
  inputUrl: fileUrl,
26
26
  });
27
27
  const { coverage } = metadata;
@@ -104,7 +104,7 @@ export const executeSteps = async (
104
104
  rootDirectoryUrl,
105
105
  coverageConfig,
106
106
  coverageIncludeMissing,
107
- coverageMethodForBrowsers,
107
+ coverageMethodForNodeJs,
108
108
  coverageV8ConflictWarning,
109
109
  });
110
110
  executePlanReturnValue.planCoverage = planCoverage;
@@ -4,7 +4,7 @@
4
4
  * So the best solution remains NODE_V8_COVERAGE
5
5
  * This profiler strategy remains useful when:
6
6
  * - As fallback when NODE_V8_COVERAGE is not configured
7
- * - If explicitely enabled with coverageMethodForNodeJs: 'Profiler'
7
+ * - If explicitely enabled with coverageMethodForNodeJs: "Profiler"
8
8
  * - Used by jsenv during automated tests about coverage
9
9
  * - Anyone prefering this approach over NODE_V8_COVERAGE and assuming
10
10
  * it will not fork subprocess or don't care if coverage is missed for this code