Recordsnpm@typescript-eslint/typesfailure issue
Failure signature
PROJECT_TEST exit 1 ELIFECYCLE ×10
ELIFECYCLE Test failed. See above for more details.
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer pnpm test · First recorded: 2026-08-29 · Last seen: 2026-09-01
sha256:7711694d48fa…
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.
- 8.69.0 PASS 9 passing observations
- 8.68.0 not measured
- 8.67.0 PASS 1 passing observations
- 8.66.0 FAIL
- 8.65.0 PASS 20 passing observations
- 8.59.3 not measured
- 8.46.4 PASS 1 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×10 2026-08-29 → 2026-09-01
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 8.65.0 → first failing release 8.66.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 8.66.0 → first passing release 8.67.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @typescript-eslint/types 8.66.0 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-21