Recordsnpmjsdom
Change the conditions
Current conditions
jsdom @27.3.0windows 11 · x64 · node 24 · npm 11 · node
0 of 9 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 20 / 68
- Contract verifications
- 0 / 9
- Usage records
- 45
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 9 passed
Verified — this network ran a contract at this coordinate.
-
jsdom.JSDOM
0 of 9 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
27.3.0
windows · node@24.13 · executionContext=node · moduleSystem=cjs
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @asamuzakjp/dom-selector | 6.7.6 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| cssstyle | 5.3.5 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| data-urls | 6.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| html-encoding-sniffer | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| parse5 | 8.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| tough-cookie | 6.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| webidl-conversions | 8.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| whatwg-mimetype | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| whatwg-url | 15.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| ws | 8.18.3 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| @acemir/cssom | 0.9.30 | PASS All observations passed | contract passed | 3 project-days |
| decimal.js | 10.6.0 | PASS All observations passed | contract passed | 3 project-days |
| http-proxy-agent | 7.0.2 | PASS All observations passed | contract passed | 3 project-days |
| https-proxy-agent | 7.0.6 | PASS All observations passed | contract passed | 3 project-days |
| is-potential-custom-element-name | 1.0.1 | PASS All observations passed | contract passed | 3 project-days |
| saxes | 6.0.0 | PASS All observations passed | contract passed | 3 project-days |
| symbol-tree | 3.2.4 | PASS All observations passed | contract passed | 3 project-days |
| w3c-xmlserializer | 5.0.0 | PASS All observations passed | contract passed | 3 project-days |
| whatwg-encoding | 3.1.1 | PASS All observations passed | contract passed | 3 project-days |
| xml-name-validator | 5.0.0 | PASS All observations passed | contract passed | 3 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.
Moved: 15 · unchanged at every release: 15
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.