Recordsnpmjsdom
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
26.0.0
linux · node@22.23 · moduleSystem=esm · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:529aac3b1da710068c9dcfe93d0864269e86bebfbe110ca5beeed398860460e7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cssstyle | 4.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| data-urls | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| html-encoding-sniffer | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| nwsapi | 2.2.24 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| nwsapi | 2.2.27 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| parse5 | 7.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| rrweb-cssom | 0.8.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| tough-cookie | 5.1.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| webidl-conversions | 7.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| whatwg-mimetype | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| whatwg-url | 14.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| ws | 8.21.3 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| decimal.js | 10.6.0 | PASS All observations passed | contract passed | 2 project-days |
| form-data | 4.0.6 | PASS All observations passed | contract passed | 2 project-days |
| http-proxy-agent | 7.0.2 | PASS All observations passed | contract passed | 2 project-days |
| https-proxy-agent | 7.0.6 | PASS All observations passed | contract passed | 2 project-days |
| is-potential-custom-element-name | 1.0.1 | PASS All observations passed | contract passed | 2 project-days |
| saxes | 6.0.0 | PASS All observations passed | contract passed | 2 project-days |
| symbol-tree | 3.2.4 | PASS All observations passed | contract passed | 2 project-days |
| w3c-xmlserializer | 5.0.0 | PASS All observations passed | contract passed | 1 project-day |
| whatwg-encoding | 3.1.1 | PASS All observations passed | contract passed | 1 project-day |
| xml-name-validator | 5.0.0 | PASS All observations passed | contract passed | 1 project-day |
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: 15 · unchanged at every release: 15
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.