Recordsnpmprosemirror-modelfailure issue
Failure signature
UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×2
node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · Error [ERR_MODULE_NOT_FOUND]: Cannot find module <str> imported from <path>
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-09-13 · Last seen: 2026-09-14
sha256:a4c16095efc0…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-09-13 → 2026-09-14
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.25.11 | 1.25.4 |
|---|---|---|
| orderedmap | 2.1.1 | 2.1.1 |
Moved: 0 · unchanged at every release: 1
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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.