Recordsnpmcall-bindfailure 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.
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
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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 | 1.0.9 | 1.0.8 |
|---|---|---|
| call-bind-apply-helpers | 1.0.2 | 1.0.2 |
| es-define-property | 1.0.1 | 1.0.1 |
| get-intrinsic | 1.3.0 | 1.3.0 |
| set-function-length | 1.2.2 | 1.2.2 |
Moved: 0 · unchanged at every release: 4
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.