Recordsnpmbrace-expansionfailure issue
Failure signature
PROJECT_COMPILE exit 2 TS2741 ×6
src/main/historyWindow.ts(<n>,<n>): error TS2741: Property <str> is missing in type <str> but required in type <str>.
Evidence quality: complete · typescript/tsc · compiler-diagnostic · outer npm run · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:e79354dba35f…
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.
- 5.0.9 PASS 165 passing observations
- 5.0.8 FAIL
- 2.1.7 PASS 8 passing observations
- 2.1.4 PASS 165 passing observations
- 2.1.3 FAIL
- 2.0.2 not measured
- 1.1.21 PASS 8 passing observations
- 1.1.18 PASS 165 passing observations
- 1.1.17 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×6 2026-09-01 → 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 failing release 1.1.17 → first passing release 1.1.18
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 1.1.21 → first failing release 2.1.3
Releases between them never measured at this stage: 1
What differs across the boundary
- concat-map 0.0.1 → — hypothesis
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 2.1.3 → first passing release 2.1.4
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 2.1.7 → first failing release 5.0.8
What differs across the boundary
- balanced-match 1.0.2 → 4.0.4 hypothesis
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 5.0.8 → first passing release 5.0.9
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 | 5.0.9 | 5.0.8 | 2.1.7 | 2.1.4 | 2.1.3 | 2.0.2 | 1.1.21 | 1.1.18 | 1.1.17 |
|---|---|---|---|---|---|---|---|---|---|
| balanced-match | 4.0.4 | 4.0.4 | 1.0.2 | 1.0.2 | 1.0.2 | 1.0.2 | 1.0.2 | 1.0.2 | 1.0.2 |
| concat-map | — | — | — | — | — | — | 0.0.1 | 0.0.1 | 0.0.1 |
Moved: 1 · unchanged at every release: 1
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_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- brace-expansion 5.0.8 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
- brace-expansion 2.1.3 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-21
- brace-expansion 1.1.17 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-21