Recordsnpm@asamuzakjp/dom-selector
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
7.1.1
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:1be69c1584909f830d69e106adb00b0cc501e3da58d75fe81bcab93528ff0b3d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| bidi-js | 1.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| bidi-js | 1.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| css-tree | 3.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| @asamuzakjp/generational-cache | 1.0.1 | PASS All observations passed | contract passed | 3 project-days |
| @asamuzakjp/nwsapi | 2.3.9 | PASS All observations passed | contract passed | 3 project-days |
| is-potential-custom-element-name | 1.0.1 | PASS All observations passed | contract passed | 3 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 | 8.3.2 | 7.1.1 | 6.7.6 |
|---|---|---|---|
| bidi-js | 1.1.0 | 1.0.3 | 1.0.3 |
| css-tree | 3.2.1 | 3.2.1 | 3.1.0 |
| lru-cache | 11.5.2 | — | 11.2.4 |
| @asamuzakjp/generational-cache | — | 1.0.1 | — |
| @asamuzakjp/nwsapi | — | 2.3.9 | 2.3.9 |
| is-potential-custom-element-name | 1.0.1 | 1.0.1 | 1.0.1 |
Moved: 3 · unchanged at every release: 3
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.