Recordsnpmes-module-lexerfailure issue
Failure signature
PROJECT_COMPILE exit 1 TS6133 ×1
<token>.test.ts(<n>,<n>): error TS6133: <str> is declared but its value is never read.
Evidence quality: complete · typescript/tsc · compiler-diagnostic · outer npm run · First recorded: 2026-09-09 · Last seen: 2026-09-09
sha256:45b167de0100…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-09 → 2026-09-09
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 1.7.0 → first failing release 2.3.2
Releases between them never measured at this stage: 2
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- 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