CodeSampleX

Recordsnpmprosemirror-changeset2.4.2

Change the conditions
Fixed
OSdebian glibc Package version2.4.2 Package managernpm
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

prosemirror-changeset @2.4.2debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
9
Independent reporting peers
2
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

2.4.2

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:a4c16095efc09c0e3ff544250e938719346bc9b2cb85e02e7db0a48f7c91962a

Library Version Health Measured there Projects
prosemirror-transform 1.12.1 CANDIDATE Correlated change; unproven combination contract passed 75 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.

Library2.4.32.4.22.3.1
prosemirror-transform 1.12.1 1.12.1 1.10.5

Moved: 1 · unchanged at every release: 0

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