Recordsnpm@inquirer/core
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
9.2.1
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:4a939d00eec492b9a03b26b042fb8a8194c85e6b0782361ef967eb9b259f03ba
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @inquirer/figures | 1.0.15 | PASS All observations passed | contract passed | 21 project-days |
| @inquirer/type | 2.0.0 | PASS All observations passed | contract passed | 21 project-days |
| @types/mute-stream | 0.0.4 | PASS All observations passed | contract passed | 21 project-days |
| @types/node | 22.20.2 | PASS All observations passed | contract passed | 11 project-days |
| @types/node | 22.20.3 | PASS All observations passed | contract passed | 10 project-days |
| @types/wrap-ansi | 3.0.0 | PASS All observations passed | contract passed | 21 project-days |
| ansi-escapes | 4.3.2 | PASS All observations passed | contract passed | 21 project-days |
| cli-width | 4.1.0 | PASS All observations passed | contract passed | 21 project-days |
| mute-stream | 1.0.0 | PASS All observations passed | contract passed | 20 project-days |
| signal-exit | 4.1.0 | PASS All observations passed | contract passed | 21 project-days |
| strip-ansi | 6.0.1 | PASS All observations passed | contract passed | 21 project-days |
| wrap-ansi | 6.2.0 | PASS All observations passed | contract passed | 20 project-days |
| yoctocolors-cjs | 2.1.3 | PASS All observations passed | contract passed | 21 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.