CodeSampleX

Recordsnpm@vitest/expect4.1.11

Change the conditions
Fixed
Runtimenode 22 Package managernpm 11 Execution contextnode
Filter OSwindows 11 Package version4.1.11 Symbolwhole package Architecturex64 Clear filters

Current conditions

@vitest/expect @4.1.11windows 11 · x64 · node 22 · npm 11 · node

package-level total, not an API

15 of 16 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
15 / 16
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-24
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 1

First observed break

4.1.11

windows · node@24.13 · moduleSystem=cjs · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d

View exact conditions View failure cluster
Library Version Health Measured there Projects
@standard-schema/spec 1.1.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@vitest/spy 4.1.11 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@vitest/utils 4.1.11 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
chai 6.2.2 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
tinyrainbow 3.1.1 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@types/chai 5.2.3 PASS All observations passed contract passed 7 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.

Library4.1.114.1.104.0.184.0.164.0.03.2.73.2.43.0.02.1.9
@standard-schema/spec 1.1.0 1.1.0 1.1.0 1.0.0 1.1.0 — — — —
@vitest/spy 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
@vitest/utils 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
chai 6.2.2 6.2.2 6.2.2 6.2.2 6.2.2 5.3.3 5.3.3 5.3.3 5.3.3
tinyrainbow 3.1.1 3.1.1 3.1.1 3.0.3 3.1.1 2.0.0 2.0.0 2.0.0 1.2.0
@types/chai 5.2.3 5.2.3 5.2.3 5.2.3 5.2.3 5.2.3 5.2.3 — —

Moved: 5 · unchanged at every release: 1

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