CodeSampleX

Recordsnpm@tiptap/pm3.11.0@tiptap/pm.NodeSelection

Change the conditions
Fixed
OSdebian glibc Symbol@tiptap/pm.NodeSelection
Filter Runtimenode 22 Package version3.11.0 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@tiptap/pm.NodeSelection @3.11.0debian glibc · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 16

First observed break

3.11.0

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:37e6355fb7d371e1d91c409ce419aa00df3f3d37074d1f10edb63b767578f0be

Library Version Health Measured there Projects
prosemirror-changeset 2.4.2 CANDIDATE Correlated change; unproven combination contract passed 40 project-days
prosemirror-changeset 2.4.3 CANDIDATE Correlated change; unproven combination nothing measured 2 project-days
prosemirror-model 1.25.11 CANDIDATE Correlated change; unproven combination contract passed 42 project-days
prosemirror-collab 1.3.1 PASS All observations passed 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 43 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-markdown 1.13.7 PASS All observations passed contract passed 42 project-days
prosemirror-menu 1.3.2 PASS All observations passed contract passed 42 project-days
prosemirror-schema-basic 1.2.4 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 43 project-days
prosemirror-tables 1.8.5 PASS All observations passed contract passed 42 project-days
prosemirror-trailing-node 3.0.0 PASS All observations passed contract passed 43 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.

Recent failure clusters