Recordsnpmelectronfailure issue
Failure signature
PROJECT_TEST exit 1 ELIFECYCLE ×18
ELIFECYCLE Test failed. See above for more details.
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer pnpm test · First recorded: 2026-08-29 · Last seen: 2026-09-01
sha256:7711694d48fa…
electron.BrowserWindow electron.IpcMainEvent electron.IpcMainInvokeEvent electron.Menu electron.Session electron.Tray electron.WebContents electron.WebContentsView electron.app electron.contextBridge electron.dialog electron.ipcMain electron.ipcRenderer electron.nativeImage electron.net electron.protocol electron.safeStorage electron.session electron.shell
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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 62 passing observations
- 43.3.0 not measured
- 43.2.0 PASS 1 passing observations
- 38.8.6 FAIL
- 38.0.0 PASS 1 passing observations
- 33.4.11 PASS 20 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×18 2026-08-29 → 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.0.0 → first failing release 38.8.6
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 38.8.6 → first passing release 43.2.0
What differs across the boundary
- @electron-internal/extract-zip 1.0.5 → — hypothesis
- @electron/get 5.1.0 → 2.0.3 hypothesis
- @types/node 24.13.3 → 22.20.1 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.
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_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- electron 38.8.6: safeStorage 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. HOWelectron.safeStoragenode 22.23.2 MIT-0 · 2026-08-27
- electron 38.8.6: protocol 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. HOWelectron.protocolnode 22.23.2 MIT-0 · 2026-08-27
- electron 38.8.6: net 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. HOWelectron.net MIT-0 · 2026-08-27