Recordsnpm@tiptap/pm3.11.0@tiptap/pm.Selection
OS × runtime at a glance
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.
Published samples
- @tiptap/pm 3.11.0: Selection This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW@tiptap/pm.Selectionnode 22.23.2 MIT-0 · 2026-09-17
Compatibility matrix
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 · JS · npm · linux glibc · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 1✓
|
LOW | 1 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 3✓
|
LOW | 3 | 0 | 100% | 1 | 2026-09-17 |
snapshot · 2026-09-17
Failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 3.11.0 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 3.11.0 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 3.11.0 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