Recordsnpmjs-yamlfailure issue
Failure signature
PROJECT_COMPILE exit 2 TS2305 ×2
app/factcheck/[id]/layout.tsx(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …
Evidence quality: complete · typescript/tsc · compiler-diagnostic · outer npm · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:4c6770254770…
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.
- 4.3.2 PASS 8 passing observations
- 4.3.1 PASS 172 passing observations
- 4.3.0 PASS 8 passing observations
- 4.1.1 FAIL
- 4.1.0 not measured
- 3.15.2 not measured
- 3.15.1 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×2 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 4.1.1 → first passing release 4.3.0
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 | 4.3.2 | 4.3.1 | 4.3.0 | 4.1.1 | 4.1.0 | 3.15.2 | 3.15.1 |
|---|---|---|---|---|---|---|---|
| argparse | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 | 1.0.10 | 1.0.10 |
| esprima | — | — | — | — | — | 4.0.1 | 4.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: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.