CodeSampleX

Recordsnpm@asamuzakjp/dom-selector8.3.2

Change the conditions
Fixed
Runtimenode 24 Package version8.3.2
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@asamuzakjp/dom-selector @8.3.2windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

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.

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.