Recordsnpmelectronfailure issue
Failure signature
PROJECT_COMPILE exit 2 TS2741 ×2
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…
electron.BrowserWindow electron.Display electron.Event electron.IpcMainEvent electron.IpcMainInvokeEvent electron.Menu electron.MenuItemConstructorOptions electron.Notification electron.Rectangle electron.Tray electron.WebContents electron.app electron.clipboard electron.contextBridge electron.crashReporter electron.desktopCapturer electron.dialog electron.exe electron.globalShortcut electron.ipcMain electron.ipcRenderer electron.nativeImage electron.powerMonitor electron.screen electron.session electron.shell electron.webContents
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.
- 43.4.1 PASS 28 passing observations
- 43.3.0 not measured
- 43.2.0 FAIL
- 38.8.6 PASS 135 passing observations
- 38.0.0 not measured
- 33.4.11 PASS 8 passing observations
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 passing release 38.8.6 → first failing release 43.2.0
What differs across the boundary
- @electron-internal/extract-zip — → 1.0.5 hypothesis
- @electron/get 2.0.3 → 5.1.0 hypothesis
- @types/node 22.20.1 → 24.13.3 hypothesis
- extract-zip 2.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 43.2.0 → first passing release 43.4.1
Releases between them never measured at this stage: 1
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 | 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.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- electron 43.2.0 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