Recordsnpmbrowserslist
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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
First observed break
4.28.7
executionContext=node
20 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| baseline-browser-mapping | 2.11.19 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| baseline-browser-mapping | 2.11.24 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| baseline-browser-mapping | 2.11.7 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| caniuse-lite | 1.0.30001806 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| caniuse-lite | 1.0.30001810 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| electron-to-chromium | 1.5.398 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| electron-to-chromium | 1.5.415 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| electron-to-chromium | 1.5.430 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| node-releases | 2.0.51 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| node-releases | 2.0.53 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| node-releases | 2.0.55 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| update-browserslist-db | 1.2.3 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| update-browserslist-db | 1.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| update-browserslist-db | 1.3.3 | CANDIDATE Correlated change; unproven combination | contract passed | 7 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.29.5 | 4.29.0 | 4.28.9 | 4.28.8 | 4.28.7 | 4.28.1 |
|---|---|---|---|---|---|---|
| baseline-browser-mapping | 2.11.36 | 2.11.28 | 2.11.23 | 2.11.15 | 2.11.19 | 2.9.11 |
| caniuse-lite | 1.0.30001826 | 1.0.30001815 | 1.0.30001810 | 1.0.30001809 | 1.0.30001806 | 1.0.30001761 |
| electron-to-chromium | 1.5.482 | 1.5.452 | 1.5.427 | 1.5.414 | 1.5.415 | 1.5.267 |
| node-releases | 2.0.63 | 2.0.58 | 2.0.55 | 2.0.53 | 2.0.53 | 2.0.27 |
| update-browserslist-db | 1.3.4 | 1.3.4 | 1.2.3 | 1.3.0 | 1.3.1 | 1.2.3 |
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.