Recordsnpm@vitest/expect3.2.7
Change the conditions
Current conditions
@vitest/expect @3.2.7alpine musl · x64 · node 22 · npm · node
package-level total, not an API
1 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 came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @types/chai | 5.2.3 | contract passed | 6 project-days |
| @vitest/spy | 3.2.7 | contract passed | 4 project-days |
| @vitest/utils | 3.2.7 | contract passed | 4 project-days |
| chai | 5.3.3 | contract passed | 2 project-days |
| tinyrainbow | 2.0.0 | 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 | 4.1.11 | 3.2.7 | 2.1.9 |
|---|---|---|---|
| @vitest/spy | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/utils | 4.1.11 | 3.2.7 | 2.1.9 |
| chai | 6.2.2 | 5.3.3 | 5.3.3 |
| tinyrainbow | 3.1.1 | 2.0.0 | 1.2.0 |
| @standard-schema/spec | 1.1.0 | — | — |
| @types/chai | 5.2.3 | 5.2.3 | — |
Moved: 4 · unchanged at every release: 2
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_PROCESS ERR_ASSERTION Evidence gap ×5 3.2.7 → 4.1.10 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate