Recordsnpmprosemirror-menu1.3.2
Change the conditions
Current conditions
prosemirror-menu @1.3.2debian glibc · x64 · node 22 · npm · node
package-level total, not an API
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
- 4 / 4
- Contract verifications
- 1 / 1
- Usage records
- 7
- Independent reporting peers
- 2
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.3.2
linux · node@22.23 · executionContext=node · moduleSystem=esm
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:37e6355fb7d371e1d91c409ce419aa00df3f3d37074d1f10edb63b767578f0be
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| crelt | 1.0.7 | CANDIDATE Correlated change; unproven combination | contract passed | 45 project-days |
| prosemirror-commands | 1.7.2 | CANDIDATE Correlated change; unproven combination | contract passed | 46 project-days |
| prosemirror-history | 1.5.0 | PASS All observations passed | contract passed | 46 project-days |
| prosemirror-state | 1.4.4 | PASS All observations passed | contract passed | 46 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.
| Library | 1.3.2 | 1.2.5 |
|---|---|---|
| crelt | 1.0.7 | 1.0.6 |
| prosemirror-commands | 1.7.2 | 1.7.1 |
| prosemirror-history | 1.5.0 | 1.5.0 |
| prosemirror-state | 1.4.4 | 1.4.4 |
Moved: 2 · unchanged at every release: 2
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
-
observed UNKNOWN exit 1 Evidence gap ×1 1.3.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:37e6355fb7d3…fil<path>:<n> · throw new RangeError(<str> + pos + <str>); · ^ · RangeError: Position 100 out of rangenode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-17 · Last seen: 2026-09-17Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_PACKAGE_PATH_NOT_EXPORTED Evidence gap ×1 1.3.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:76c8bae9d497…node:internal/modules/esm/resolve:<n> · return new ERR_PACKAGE_PATH_NOT_EXPORTED( · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-17 · Last seen: 2026-09-17Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 1.3.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-17 · Last seen: 2026-09-17Diagnostic re-verification candidate