Recordsnpm@oxc-project/typesfailure issue
Failure signature
PROJECT_TEST exit 1 ERR_LOAD_URL ×1
Contract test failed: Error: Failed to load custom Reporter from basic · at loadCustomReporterModule (fil<path>:<n>:<n>) · at fil<path>:<n>:<n> …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:a60e7101af87…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 0.149.0 PASS 12 passing observations
- 0.148.0 not measured
- 0.147.0 FAIL
- 0.144.0 not measured
- 0.142.0 PASS 1 passing observations
- 0.139.0 PASS 1 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-08-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 0.142.0 → first failing release 0.147.0
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release 0.147.0 → first passing release 0.149.0
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 2
- No resolved dependency tree for 0.142.0 or for 0.147.0, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.