Recordsnpmelectronfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×5
node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>
Evidence quality: complete · npm · unclassified-diagnostic · outer npm run · gap stage-unknown · First recorded: 2026-09-13 · Last seen: 2026-09-15
sha256:bc4d7ddc5bcd…
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.safeStorage electron.screen electron.session electron.shell electron.webContents
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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 not measured
- 43.3.0 not measured
- 43.2.0 FAIL
- 38.8.6 not measured
- 38.0.0 not measured
- 33.4.11 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×5 2026-09-13 → 2026-09-15
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 | 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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 5
- 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