Recordsnpm@asamuzakjp/dom-selector8.3.2
Change the conditions
Current conditions
@asamuzakjp/dom-selector @8.3.2ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 1 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
- 3 / 3
- Contract verifications
- 0 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-06
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.3.2
linux · node@22.23 · moduleSystem=cjs · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:f0ffff252e3f94518ed1f8821bf9fcf877e30b2d5cf79818540559f03f269589
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| bidi-js | 1.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| css-tree | 3.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| lru-cache | 11.5.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| is-potential-custom-element-name | 1.0.1 | PASS All observations passed | contract passed | 2 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.
| Library | 8.3.2 | 7.1.1 | 6.7.6 |
|---|---|---|---|
| bidi-js | 1.1.0 | 1.0.3 | 1.0.3 |
| css-tree | 3.2.1 | 3.2.1 | 3.1.0 |
| lru-cache | 11.5.2 | — | 11.2.4 |
| @asamuzakjp/generational-cache | — | 1.0.1 | — |
| @asamuzakjp/nwsapi | — | 2.3.9 | 2.3.9 |
| is-potential-custom-element-name | 1.0.1 | 1.0.1 | 1.0.1 |
Moved: 3 · unchanged at every release: 3
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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 8.3.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:f0ffff252e3f…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: flushSync() without args should flush pending updatesnode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate