Recordsnpmjsdom26.1.0jsdom.JSDOM
shared with 3 packages — this evidence cannot say whose API it is
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
- jsdom 26.1.0: Intercept and customize subresource loading in JSDOM using ResourceLoader 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. HOWJSDOMResourceLoadernode 22.23.2 MIT-0 · 2026-08-28
- jsdom 26.1.0: Control script execution scope and capture uncaught script exceptions using JSDOM runScripts modes and VirtualConsole event routing 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. HOWJSDOMVirtualConsolenode MIT-0 · 2026-08-17
- jsdom 26.1.0: Configure JSDOM with a valid url to enable Web Storage APIs and prevent opaque origin SecurityError exceptions on about:blank 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. HOWJSDOMnode MIT-0 · 2026-08-17
- jsdom 26.1.0: Show that two sequential setState calls with stale state are not both applied in concurrent mode 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. HOWjsdom.JSDOMreact.useStatereact-dom/client.createRootreact-dom/test-utils.actnode MIT-0 · 2026-08-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 musl · docker
Verified: CONTRACT 2✓
|
MEDIUM | 0 | 2 | 100% | 0 · 2✓ | 2026-08-18 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_TEST 1✓ 1✕
|
LOW | 2 | 0 | 50% | 1 | 2026-08-17 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_TEST Evidence gap ×2 25.0.1 → 26.1.0 executionContext=node · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-17 · Last seen: 2026-08-21Diagnostic re-verification candidate
-
observed PROJECT_TEST Evidence gap ×1 26.1.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 jsdom.JSDOMEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-17 · Last seen: 2026-08-17