Recordsnpm@asamuzakjp/dom-selector6.7.6
Change the conditions
Current conditions
@asamuzakjp/dom-selector @6.7.6windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
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 / 52
- Contract verifications
- 0 / 9
- Usage records
- 45
- Independent reporting peers
- 1
- Last recorded
- 2026-09-15
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 3 ·
Steady 2
First observed break
6.7.6
windows · node@24.13 · moduleSystem=cjs · executionContext=node
2 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0d787687eb6d91ecda01dd52049f201fdea94afc8d0ee8e9241b7bad335978fa
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| bidi-js | 1.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| css-tree | 3.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| lru-cache | 11.2.4 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| @asamuzakjp/nwsapi | 2.3.9 | 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 |
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 PROJECT_COMPILE exit 2 TS2345 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:0d787687eb6d…lib/services/sync-service.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2322 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:398ffe6fb765…lib/api/records/politician-records.ts(<n>,<n>): error TS2322: Type <str> is not assignable to type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2305 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:4c6770254770…app/factcheck/[id]/layout.tsx(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2339 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:a2b1d30276e3…lib/api/politicians/detail.ts(<n>,<n>): error TS2339: Property <str> does not exist on type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2694 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:a62486f02028…app/api/users/[id]/activities/route.ts(<n>,<n>): error TS2694: Namespace <str> has no exported member <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS7006 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:aece12f1c06e…app/api/test/users/route.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS18048 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:d7ce05b193a9…lib/utils/experience-update.ts(<n>,<n>): error TS18048: <str> is possibly <str>.typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed UNKNOWN exit 1 Evidence gap ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:f0f6ccc2d090…Error: Production validation failed: …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 2 TS2307 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:0470f88d95bb…lib/hooks/queries/index.ts(<n>,<n>): error TS2307: Cannot find module <str> or its corresponding type declarations. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS7006 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:21025cd78572…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2561 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:5f96e966539e…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2561: Object literal may only specify known properties, but <str> does not exist in type …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2345 ×2 6.7.6 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:7e077f646acc…lib/api/real-estate-statistics.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>.typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
Showing the 12 most-reported of 26 recorded failure clusters. The rest are single reports.