Recordsnpmelectron43.4.1electron.BrowserWindow
Change the conditions
Current conditions
electron.BrowserWindow @43.4.1windows 11 · x64 · node 24 · npm 11 · node
0 of 16 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 148 / 201
- Contract verifications
- 0 / 16
- Independent reporting peers
- 1
- Last recorded
- 2026-09-13
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 2 ·
Steady 1
First observed break
43.4.1
executionContext=node
8 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @electron/get | 5.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| @types/node | 24.13.3 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| @electron-internal/extract-zip | 1.0.5 | PASS All observations passed | contract passed | 5 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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 | 43.4.1 | 43.2.0 | 38.8.6 | 38.0.0 | 33.4.11 |
|---|---|---|---|---|---|
| @electron/get | 5.1.0 | 5.1.0 | 2.0.3 | 2.0.3 | 2.0.3 |
| @types/node | 24.13.3 | 24.13.3 | 22.20.1 | 22.20.1 | 20.19.43 |
| @electron-internal/extract-zip | 1.0.5 | 1.0.5 | — | — | — |
| extract-zip | — | — | 2.0.1 | 2.0.1 | 2.0.1 |
Moved: 2 · unchanged at every release: 2
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.
Recent failure clusters
-
observed PROCESS_START process start failed Evidence gap ×8 38.8.6 → 43.4.1 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ×4 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:87a2d9024768…[31m[1mAssertionError[22m: expected [ { kind: <str>, …(2) } ] to deeply equal [][39m · [32m- Expected[39m · [31m+ Received[39m · [32m- [][39mjavascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed UNKNOWN exit 1 Evidence gap ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:3e5f03903e29…<str> is not recognized as an internal or external command, · operable program or batch file. · > prism@0.1.0 test · > vitest runnpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 TS6133 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:45b167de0100…<token>.test.ts(<n>,<n>): error TS6133: <str> is declared but its value is never read.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS2554 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:4ae5785d6b8c…src/main/sources/runtime/sourceRuntime.test.ts(<n>,<n>): error TS2554: Expected 3 arguments, but got 4.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS6133 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:7739724d6077…src/renderer/src/components/blocks/ArticleListBlock.tsx(<n>,<n>): error TS6133: <str> is declared but its value is never read.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS2353 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:a08194196005…src/main/sources/orchestrator.test.ts(<n>,<n>): error TS2353: Object literal may only specify known properties, and <str> does not exist in type <str>.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS6133 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:d8ea1c73763a…src/main/sources/runtime/sourceRuntime.test.ts(<n>,<n>): error TS6133: <str> is declared but its value is never read. …typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS2304 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:db8d319f7f77…src/renderer/src/components/blocks/ArticleListBlock.tsx(<n>,<n>): error TS2304: Cannot find name <str>. …typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS2345 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:f5121f3e3d0c…src/main/sources/runtime/sourceRuntime.test.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_TEST exit 1 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:578ec71372b1…[31m[1mAssertionError[22m: expected { plannerModel: <str>, …(3) } to deeply equal { plannerModel: <str>, …(2) }[39m · [32m- Expected[39m …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_TEST exit 1 ×3 43.4.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.BrowserWindow sha256:77545ab83bf9…[31m[1mAssertionError[22m: expected <str> to match <path>:prism-source-news-ycombinato…/[39m · [32m- Expected:[39m …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
Showing the 12 most-reported of 20 recorded failure clusters. The rest are single reports.