Recordsnpm@tiptap/core3.31.3
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 3✓ · PROJECT_TEST 3✓ — Usage: USED 29✓ — Verified: UNKNOWN 0✓ 2✕
|
ELEVATED FAILURE | 6 +29 | 2 | 75% | 3 | 2026-09-14 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 6✓ · PROJECT_TEST 2✓ — Usage: USED 1✓
|
LOW | 8 +1 | 0 | 100% | 1 | 2026-09-14 |
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×2 3.11.0 → 3.31.3 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:a4c16095efc0…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · Error [ERR_MODULE_NOT_FOUND]: Cannot find module <str> imported from <path>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 3.31.3 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 @tiptap/core.Editor sha256:bb3c97a18248…node:assert:<n> · throw new AssertionError(obj); · ^ · AssertionError [ERR_ASSERTION]: Values have same structure but are not reference-equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate
Symbols
- @tiptap/core.Editor 0 of 1 runs passed
- @tiptap/core.Node 0 of 1 runs passed