@jsenv/test 1.3.0 → 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.
Files changed (6) hide show
  1. package/dist/js/execute_using_dynamic_import.js +1 -1
  2. package/dist/jsenv_test.js +2 -2
  3. package/package.json +2 -2
  4. package/src/coverage/empty_coverage_factory.js +1 -1
  5. package/src/execution/execute_steps.js +1 -1
  6. package/src/runtime_node/profiler_v8_coverage.js +1 -1
package/dist/js/execute_using_dynamic_import.js CHANGED
@@ -799,7 +799,7 @@ function safeDefineProperty(object, propertyNameOrSymbol, descriptor) {
799
799
  * So the best solution remains NODE_V8_COVERAGE
800
800
  * This profiler strategy remains useful when:
801
801
  * - As fallback when NODE_V8_COVERAGE is not configured
802
- * - If explicitely enabled with coverageMethodForNodeJs: 'Profiler'
802
+ * - If explicitely enabled with coverageMethodForNodeJs: "Profiler"
803
803
  * - Used by jsenv during automated tests about coverage
804
804
  * - Anyone prefering this approach over NODE_V8_COVERAGE and assuming
805
805
  * it will not fork subprocess or don't care if coverage is missed for this code
package/dist/jsenv_test.js CHANGED
@@ -3361,7 +3361,7 @@ const relativeUrlToEmptyCoverage = async (
3361
3361
  const { metadata } = await applyBabelPlugins({
3362
3362
  babelPlugins: [babelPluginInstrument],
3363
3363
  input: content,
3364
- inputIsJsModule: false,
3364
+ inputIsJsModule: true,
3365
3365
  inputUrl: fileUrl,
3366
3366
  });
3367
3367
  const { coverage } = metadata;
@@ -4297,7 +4297,7 @@ const executeSteps = async (
4297
4297
  rootDirectoryUrl,
4298
4298
  coverageConfig,
4299
4299
  coverageIncludeMissing,
4300
- coverageMethodForBrowsers,
4300
+ coverageMethodForNodeJs,
4301
4301
  coverageV8ConflictWarning,
4302
4302
  });
4303
4303
  executePlanReturnValue.planCoverage = planCoverage;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jsenv/test",
3
- "version": "1.3.0",
3
+ "version": "1.3.1",
4
4
  "license": "MIT",
5
5
  "repository": {
6
6
  "type": "git",
@@ -36,7 +36,7 @@
36
36
  "@jsenv/abort": "4.2.4",
37
37
  "@jsenv/ast": "4.1.0",
38
38
  "@jsenv/filesystem": "4.2.3",
39
- "@jsenv/log": "3.3.5",
39
+ "@jsenv/log": "3.4.0",
40
40
  "@jsenv/plugin-supervisor": "1.1.1",
41
41
  "@jsenv/urls": "2.0.0",
42
42
  "@jsenv/url-meta": "8.1.0",
package/src/coverage/empty_coverage_factory.js CHANGED
@@ -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;
package/src/execution/execute_steps.js CHANGED
@@ -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;
package/src/runtime_node/profiler_v8_coverage.js CHANGED
@@ -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