CodeSampleX

Recordsnpmbuilder-util

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 Package version25.1.7
Filter Architecturex64 Execution contextnode Clear filters
Symbol × Package version
52026-09-07

Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

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

Observed problems 1 · Changed 3 · Steady 14

First observed break

25.1.7

moduleSystem=cjs · executionContext=node

6 FAIL · stage: UNKNOWN · fingerprint: sha256:bc4d7ddc5bcdb4d412bf4a8bb2673c786c7e3852044dc88acdc3e1dc4e6f49cb

Library Version Health Measured there Projects
builder-util-runtime 9.2.10 CANDIDATE Correlated change; unproven combination contract passed 24 project-days
js-yaml 4.3.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
js-yaml 4.3.2 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
7zip-bin 5.2.0 PASS All observations passed contract passed 24 project-days
@types/debug 4.1.13 PASS All observations passed contract passed 24 project-days
app-builder-bin 5.0.0-alpha.10 PASS All observations passed contract passed 24 project-days
bluebird-lst 1.0.9 PASS All observations passed contract passed 24 project-days
chalk 4.1.2 PASS All observations passed contract passed 24 project-days
cross-spawn 7.0.6 PASS All observations passed contract passed 24 project-days
debug 4.4.3 PASS All observations passed contract passed 24 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 24 project-days
http-proxy-agent 7.0.2 PASS All observations passed contract passed 24 project-days
https-proxy-agent 7.0.6 PASS All observations passed contract passed 24 project-days
is-ci 3.0.1 PASS All observations passed contract passed 24 project-days
source-map-support 0.5.21 PASS All observations passed contract passed 24 project-days
stat-mode 1.0.0 PASS All observations passed contract passed 23 project-days
temp-file 3.4.0 PASS All observations passed contract passed 22 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.

Moved: 2 · unchanged at every release: 16

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.