Recordsnpm@vitest/pretty-format4.0.16
Change the conditions
Current conditions
@vitest/pretty-format @4.0.16windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
0 of 9 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
- 20 / 68
- Contract verifications
- 0 / 9
- Usage records
- 45
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| tinyrainbow | 3.0.3 | CHANGED Version changed, no linked failure | 3 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 |
|---|---|---|---|---|---|---|---|---|---|
| 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 |
Moved: 1 · unchanged at every release: 0
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.