Recordsnpm@xmldom/xmldomfailure issue
Failure signature
PROJECT_COMPILE exit 1 TS6133 ×1
src/shared/planner/mixInvariants.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:055e5bd1ac52…
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.
- 0.9.12 not measured
- 0.9.10 PASS 8 passing observations
- 0.8.15 PASS 7 passing observations
- 0.8.14 FAIL
- 0.8.13 PASS 144 passing observations
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 0.8.13 → first failing release 0.8.14
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 0.8.14 → first passing release 0.8.15
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @xmldom/xmldom 0.8.14: DOMException 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. HOW@xmldom/xmldom.DOMExceptionnode 22.23.2 MIT-0 · 2026-09-01
- @xmldom/xmldom 0.8.14 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. HOW MIT-0 · 2026-08-28