CodeSampleX

Recordsnpm@tiptap/pm3.14.0

Change the conditions
Fixed
OSwindows 11 Symbolwhole package
Filter Runtimenode 24 Package version3.14.0 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@tiptap/pm @3.14.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 9 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
20 / 68
Contract verifications
0 / 9
Usage records
45
Independent reporting peers
1
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 24

First observed break

3.14.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

Library Version Health Measured there Projects
prosemirror-changeset 2.3.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
prosemirror-changeset 2.4.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
prosemirror-model 1.25.11 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
prosemirror-model 1.25.4 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
prosemirror-collab 1.3.1 PASS All observations passed contract passed 5 project-days
prosemirror-commands 1.7.1 PASS All observations passed contract passed 3 project-days
prosemirror-commands 1.7.2 PASS All observations passed contract passed 2 project-days
prosemirror-dropcursor 1.8.2 PASS All observations passed contract passed 3 project-days
prosemirror-dropcursor 1.8.3 PASS All observations passed contract passed 2 project-days
prosemirror-gapcursor 1.4.0 PASS All observations passed contract passed 3 project-days
prosemirror-gapcursor 1.4.1 PASS All observations passed contract passed 2 project-days
prosemirror-history 1.5.0 PASS All observations passed contract passed 5 project-days
prosemirror-inputrules 1.5.1 PASS All observations passed contract passed 4 project-days
prosemirror-keymap 1.2.3 PASS All observations passed contract passed 4 project-days
prosemirror-markdown 1.13.2 PASS All observations passed contract passed 2 project-days
prosemirror-markdown 1.13.7 PASS All observations passed contract passed 2 project-days
prosemirror-menu 1.2.5 PASS All observations passed contract passed 2 project-days
prosemirror-menu 1.3.2 PASS All observations passed contract passed 2 project-days
prosemirror-schema-basic 1.2.4 PASS All observations passed contract passed 5 project-days
prosemirror-schema-list 1.5.1 PASS All observations passed contract passed 4 project-days
prosemirror-state 1.4.4 PASS All observations passed contract passed 3 project-days
prosemirror-tables 1.8.1 PASS All observations passed contract passed 2 project-days
prosemirror-tables 1.8.5 PASS All observations passed contract passed 2 project-days
prosemirror-trailing-node 3.0.0 PASS All observations passed contract passed 4 project-days
prosemirror-transform 1.10.5 PASS All observations passed contract passed 2 project-days
prosemirror-transform 1.12.1 PASS All observations passed contract passed 2 project-days
prosemirror-view 1.41.3 PASS All observations passed contract passed 2 project-days
prosemirror-view 1.42.3 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.

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.

Recent failure clusters

Showing the 12 most-reported of 28 recorded failure clusters. The rest are single reports.