Recordsnpm@tiptap/pm
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
3.31.3
linux · node@22.23 · moduleSystem=cjs · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:a4c16095efc09c0e3ff544250e938719346bc9b2cb85e02e7db0a48f7c91962a
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| prosemirror-changeset | 2.4.2 | CANDIDATE Correlated change; unproven combination | contract passed | 33 project-days |
| prosemirror-changeset | 2.4.3 | CANDIDATE Correlated change; unproven combination | nothing measured | 10 project-days |
| prosemirror-model | 1.25.11 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| prosemirror-commands | 1.7.2 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-dropcursor | 1.8.3 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-gapcursor | 1.4.1 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-history | 1.5.0 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-inputrules | 1.5.1 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-keymap | 1.2.3 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-schema-list | 1.5.1 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-state | 1.4.4 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-tables | 1.8.5 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-transform | 1.12.1 | PASS All observations passed | contract passed | 42 project-days |
| prosemirror-view | 1.42.3 | PASS All observations passed | contract passed | 42 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.
Moved: 2 · unchanged at every release: 16
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.