Recordsnpm@vitest/expect4.1.11@vitest/expect.Any
Change the conditions
Current conditions
@vitest/expect.Any @4.1.11ubuntu glibc · x64 · node 22 · npm 10 · node
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
- 2 / 2
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.1.11
windows · node@24.13 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d
| 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.
| Library | 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 |
|---|---|---|---|---|---|---|---|---|---|
| @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
-
observed UNKNOWN exit 1 Evidence gap ×1 4.1.11 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 @vitest/expect.Any sha256:994722463fe8…fil<path>:<n> · throw Error( · ^ · Error: Invalid Chai property: toSatisfy. Did you mean <str>?node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_LOAD_URL ×1 4.1.11 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:a60e7101af87…Contract test failed: Error: Failed to load custom Reporter from basic · at loadCustomReporterModule (fil<path>:<n>:<n>) · at fil<path>:<n>:<n> …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31