Recordsnpmwhatwg-url
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.
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
17.1.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:f0ffff252e3f94518ed1f8821bf9fcf877e30b2d5cf79818540559f03f269589
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| tr46 | 6.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| webidl-conversions | 8.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| @exodus/bytes | 1.15.1 | PASS All observations passed | contract passed | 2 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 | 17.1.0 | 16.0.1 | 15.1.0 | 14.2.0 | 5.0.0 |
|---|---|---|---|---|---|
| tr46 | 6.0.0 | 6.0.0 | 6.0.0 | 5.1.1 | 0.0.3 |
| webidl-conversions | 8.0.1 | 8.0.1 | 8.0.0 | 7.0.0 | 3.0.1 |
| @exodus/bytes | 1.15.1 | 1.15.1 | — | — | — |
Moved: 2 · unchanged at every release: 1
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.