Recordsnpm@typescript-eslint/tsconfig-utilsfailure issue
Failure signature
PROJECT_TEST exit 1 EOF ×1
[31m[1mAssertionError[22m: expected [ <str>, <str>, <str>, <str> ] to deeply equal [ <str>, <str>, <str>, <str> ][39m · [32m- Expected[39m …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:d757efcbaf88…
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.68.0 not measured
- 8.67.0 PASS 1 passing observations
- 8.66.0 PASS 183 passing observations
- 8.65.0 FAIL
- 8.59.3 not measured
- 8.46.4 PASS 1 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-14 → 2026-09-14
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.46.4 → first failing release 8.65.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 8.65.0 → first passing release 8.66.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 resolved dependency tree for 8.46.4 or for 8.65.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
- @typescript-eslint/tsconfig-utils 8.65.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-27