Recordsnpm@babel/typesfailure 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.0.4 PASS 3 passing observations
- 8.0.0 PASS 1 passing observations
- 7.29.8 PASS 265 passing observations
- 7.29.7 FAIL
- 7.28.5 PASS 1 passing observations
- 7.24.0 not measured
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 7.28.5 → first failing release 7.29.7
What differs across the boundary
- @babel/helper-string-parser 7.27.1 → 7.29.7 evidence
- @babel/helper-validator-identifier 7.28.5 → 7.29.7 evidence
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 7.29.7 → first passing release 7.29.8
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 8.0.4 | 8.0.0 | 7.29.8 | 7.29.7 | 7.28.5 |
|---|---|---|---|---|---|
| @babel/helper-string-parser | 8.0.0 | 8.0.0 | 7.29.7 | 7.29.7 | 7.27.1 |
| @babel/helper-validator-identifier | 8.0.4 | 8.0.4 | 7.29.7 | 7.29.7 | 7.28.5 |
Moved: 2 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @babel/types 7.29.7: arrayExpression 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@babel/types.arrayExpression MIT-0 · 2026-09-05
- @babel/types 7.29.7: numericLiteral 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@babel/types.numericLiteralnode 22.23.2 MIT-0 · 2026-09-05
- @babel/types 7.29.7: memberExpression 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@babel/types.memberExpressionnode 22.23.2 MIT-0 · 2026-09-05