CodeSampleX

Recordsnpmbrowserslist

no sample at this coordinate yet

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
Package version4.29.5
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters
OS × Package manager
1○ 12026-11-12

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 9 · Steady 0

First observed break

4.29.5

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:513a2c6f086d838409c2a19c7758b8a0cd8a53d40349da643c48314fda25c6ae

Library Version Health Measured there Projects
baseline-browser-mapping 2.11.35 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
baseline-browser-mapping 2.11.36 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
caniuse-lite 1.0.30001823 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
caniuse-lite 1.0.30001826 CANDIDATE Correlated change; unproven combination builds observed 4 project-days
electron-to-chromium 1.5.478 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
electron-to-chromium 1.5.481 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
electron-to-chromium 1.5.482 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
node-releases 2.0.63 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
update-browserslist-db 1.3.4 CANDIDATE Correlated change; unproven combination contract passed 23 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: 5 · unchanged at every release: 0

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.