Records npmelectron

Coverage gap requested. The version and API coordinates listed below remain unanswered. This does not mean other versions or APIs of this package lack samples or compatibility evidence.

@43.2.0 · NativeImage.getSize · 2 anonymous daily reports
@43.2.0 · NativeImage.isEmpty · 2 anonymous daily reports
@43.2.0 · NativeImage.toPNG · 1 anonymous daily report
@43.2.0 · desktopCapturer.getSources · 1 anonymous daily report
@43.2.0 · session.setDisplayMediaRequestHandler · 1 anonymous daily report
@43.2.0 · navigator.mediaDevices.getDisplayMedia · 1 anonymous daily report
@43.2.0 · HTMLVideoElement.requestVideoFrameCallback · 1 anonymous daily report
@43.2.0 · MediaStreamTrackProcessor · 1 anonymous daily report
@43.2.0 · Blob.arrayBuffer · 1 anonymous daily report
@43.2.0 · MediaRecorder.requestData · 1 anonymous daily report
@43.2.0 · MediaRecorder.start · 1 anonymous daily report
@43.2.0 · media::OutputPositionTracker::WriteSpan · 1 anonymous daily report
@43.2.0 · MP4MuxerDelegate::FlushFragment · 1 anonymous daily report
@43.2.0 · MediaRecorder · 1 anonymous daily report
@43.2.0 · OutputPositionTracker · 1 anonymous daily report
@38.0.0 · WebContents.on · 1 anonymous daily report
@38.0.0 · ipcMain.handle · 1 anonymous daily report
@38.0.0 · ipcRenderer.invoke · 1 anonymous daily report
@38.0.0 · render-process-gone · 1 anonymous daily report
@43.2.0 · contextBridge.exposeInMainWorld · 1 anonymous daily report
@43.2.0 · ipcMain.handle · 1 anonymous daily report
@43.2.0 · ipcRenderer.invoke · 1 anonymous daily report
@43.2.0 · nativeImage.createFromBuffer · 1 anonymous daily report
@43.2.0 · NativeImage.resize · 1 anonymous daily report
@43.2.0 · NativeImage.toDataURL · 1 anonymous daily report
@43.2.0 · nativeImage.createFromPath · 1 anonymous daily report
@38.0.0 · 1 anonymous daily report

Change the conditions

Current conditions

electron.session @43.4.1musl · x64 · node 22 · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations: 18 / 18
Contract verifications: 1 / 1
Independent reporting peers: 1
Last recorded: 2026-08-28

Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Open the next level

Verified — this network ran a contract at this coordinate.
windows 11 · x64 · node 22 · npm 11 · node

18 of 18 passed

Open the next level

Observed — real project builds reported from this coordinate.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

38.8.6

windows · node@24.13 · moduleSystem=esm · executionContext=node

47 FAIL · stage: UNKNOWN · fingerprint: sha256:979755e6489d54fbc02ff712a1ad44c541d0fea0a79afc307d5bbd18aef3107a

View exact conditions View failure cluster

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.