Recordsnpmes-module-lexerfailure issue
Failure signature
PROJECT_TEST exit 1 ×2
FAIL src/main/sources/runtime/sourceActions.test.ts [ src/main/sources/runtime/sourceActions.test.ts ] …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:e3ee590485ca…
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.
- 2.3.2 FAIL
- 2.3.1 PASS 7 passing observations
- 2.0.0 PASS 1 passing observations
- 1.7.0 PASS 216 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×2 2026-09-13 → 2026-09-13
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 2.3.1 → first failing release 2.3.2
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- es-module-lexer 2.3.2 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWnode 22.23.2 MIT-0 · 2026-08-28