JavaScript: Node.js only. This report covers the Node runtime; it does not execute the package in a web browser.

Node.js 24.19.0 · native V8 coverage

vanilla-test Node native V8 coverage

Coverage calculated directly from the executable ranges reported by V8.

The source ran as written—without source instrumentation, transpilation, or runtime rewriting.

Coverage gates passedEvery enabled total and per-file gate is satisfied.

Executable ranges

Measured
84.83…%

414 of 488 known ranges covered · Total gate disabled

Block ranges

Measured
81.53…%

265 of 325 known ranges covered · Total gate disabled

Function ranges

Measured
91.41…%

149 of 163 known ranges covered · Total gate disabled

Executable lines

Measured
83.37…%

1209 of 1450 known ranges covered · Total gate disabled

Thresholds

Total: not enforced · Per file: enforced

Threshold results
MetricMinimumTotalPer file
Executable ranges75%Not enforcedPass
Block ranges50%Not enforcedPass
Function ranges80%Not enforcedPass
Executable lines70%Not enforcedPass

Files

9 sources measured

Native coverage by source file
SourceV8 stateExecutable rangesBlock rangesFunction rangesExecutable lines
dao/client.jsLoaded80.19…%81 / 10174.28…%52 / 7093.54…%29 / 3180.45…%210 / 261
dao/socketServer.jsLoaded83.63…%138 / 16579.80…%83 / 10490.16…%55 / 6180.76…%357 / 442
entities/Defaults.jsLoaded100%19 / 19100%13 / 13100%6 / 6100%79 / 79
entities/EventParser.jsLoaded83.33…%70 / 8483.01…%44 / 5383.87…%26 / 3181.63…%200 / 245
entities/MessageParser.jsLoaded100%2 / 2100%0 / 0100%2 / 2100%11 / 11
entities/TLS.jsLoaded94.73…%36 / 3893.75%30 / 32100%6 / 695.18…%79 / 83
helpers/delay.jsLoaded100%3 / 3100%0 / 0100%3 / 3100%11 / 11
node-ipc.jsLoaded100%2 / 2100%0 / 0100%2 / 2100%23 / 23
services/IPC.jsLoaded85.13…%63 / 7481.13…%43 / 5395.23…%20 / 2181.01…%239 / 295

How these metrics work

Transparent range semantics

Native metric definitions
Executable rangesOne item for every executable range record emitted by V8, including function roots and nested block ranges; a positive execution count is covered. V8 may collapse equal-count ranges, so totals can vary with the execution path.
Block rangesOne item for every nested block range after a function root range; a positive execution count is covered. These are count-change regions, not parser-enumerated branch alternatives.
Function rangesOne item for the first (root) range of every V8 function record; a positive execution count is covered.
Executable linesOne item for every source line whose content intersects an effective executable range; a line is covered only when every intersecting effective range has a positive count.
Effective rangesSource is partitioned at every V8 range boundary. Each segment uses the count from its smallest enclosing range, with the lowest count winning an equal-size tie.
Output interoperabilityThe JSON and LCOV files use conventional field names and records for tool transport, but executable-range and block-range totals are native V8 measurements and are not interchangeable with parser-derived statement or branch totals. Summary pct values are truncated to two decimals; threshold gates compare the exact covered/total ratio.
Included, not loadedAn included file not emitted by V8 is represented by one zero-count whole-file range. Its internal function and block structure is unknown and cannot satisfy a positive function or block threshold.

These measurements deliberately describe V8 ranges. They do not claim parser-derived statement or branch semantics.