Recordsnpm@vitest/utils3.0.0
Change the conditions
Current conditions
@vitest/utils @3.0.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 7 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
- 4 / 4
- Contract verifications
- 0 / 7
- Usage records
- 6
- Independent reporting peers
- 2
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.0.0
executionContext=node
10 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @vitest/pretty-format | 3.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| tinyrainbow | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| loupe | 3.2.1 | PASS All observations passed | contract passed | 10 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 |
|---|---|---|---|---|---|---|---|---|---|
| @vitest/pretty-format | 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 |
| 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 |
| convert-source-map | 2.0.0 | 2.0.0 | — | — | — | — | — | — | — |
| loupe | — | — | — | — | — | 3.2.1 | 3.2.1 | 3.2.1 | 3.2.1 |
Moved: 2 · 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 PROCESS_START process start failed Evidence gap ×10 2.1.9 → 3.0.0 → 3.2.4 → 3.2.7 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 3 · First recorded: 2026-08-31 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 2.1.9 → 3.0.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:8fd30f2a6304…fil<path>:<n> · throw new Error(errorMsg); · ^ · Error: Vitest failed to access its internal state.node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-08Diagnostic re-verification candidate