Recordsnpm@electron/rebuild
there is a sample for this release and API (1)
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.2.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
25 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| node-abi | 4.33.0 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| node-abi | 4.34.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| node-abi | 4.35.0 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| node-gyp | 12.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 15 project-days |
| @malept/cross-spawn-promise | 2.0.0 | PASS All observations passed | contract passed | 16 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 16 project-days |
| node-api-version | 0.2.1 | PASS All observations passed | contract passed | 15 project-days |
| read-binary-file-arch | 1.0.6 | PASS All observations passed | contract passed | 15 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 | 4.2.0 | 3.6.1 |
|---|---|---|
| node-abi | 4.34.0 | 3.94.0 |
| node-gyp | 12.4.0 | 9.4.1 |
| @malept/cross-spawn-promise | 2.0.0 | 2.0.0 |
| chalk | — | 4.1.2 |
| debug | 4.4.3 | 4.4.3 |
| detect-libc | — | 2.1.2 |
| fs-extra | — | 10.1.0 |
| got | — | 11.8.6 |
| node-api-version | 0.2.1 | 0.2.1 |
| ora | — | 5.4.1 |
| read-binary-file-arch | 1.0.6 | 1.0.6 |
| semver | — | 7.8.5 |
| tar | — | 6.2.1 |
| yargs | — | 17.7.3 |
Moved: 2 · unchanged at every release: 12
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.