CodeSampleX

Compatibilitynpm@electron/get

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Runtimenode 22 Architecturex64 Package managernpm 11
Filter Symbolwhole package Execution contextnode Clear filters
OS × Package version
22026-08-24
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 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.

Library5.1.03.1.02.0.3
debug 4.4.3 4.4.3 4.3.7
env-paths 3.0.0 2.2.1 2.2.1
semver 7.7.4 6.3.1 6.3.1
fs-extra 8.1.0 8.1.0
got 11.8.6 11.8.6
graceful-fs 4.2.11
progress 2.0.3 2.0.3 2.0.3
sumchecker 3.0.1 3.0.1 3.0.1

Moved: 3 · unchanged at every release: 5

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.