Recordsnpm@vitest/utils3.2.7
Change the conditions
Current conditions
@vitest/utils @3.2.7ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
10 of 15 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
- 10 / 15
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 2
- Failures with a captured fingerprint
- 0 / 5
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @vitest/pretty-format | 3.2.7 | contract passed | 4 project-days |
| loupe | 3.2.1 | contract passed | 4 project-days |
| tinyrainbow | 2.0.0 | contract passed | 4 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 | 3.2.7 | 2.1.9 |
|---|---|---|---|---|
| @vitest/pretty-format | 4.1.11 | 4.1.10 | 3.2.7 | 2.1.9 |
| tinyrainbow | 3.1.1 | 3.1.1 | 2.0.0 | 1.2.0 |
| convert-source-map | 2.0.0 | 2.0.0 | — | — |
| loupe | — | — | 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 PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 3.2.7 → 4.1.10 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate