Recordsnpm@vitest/runner
Change the conditions
Current conditions
beforeEach @3.2.7x64 · node 22 · node
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
- 0 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-08-23
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 1 passed
Observed — real project builds reported from this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @vitest/utils | 3.2.7 | contract passed | 6 project-days |
| pathe | 2.0.3 | contract passed | 6 project-days |
| strip-literal | 3.1.0 | contract passed | 6 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/utils | 4.1.11 | 4.1.10 | 3.2.7 | 2.1.9 |
| pathe | 2.0.3 | 2.0.3 | 2.0.3 | 1.1.2 |
| strip-literal | — | — | 3.1.0 | — |
Moved: 2 · 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.