Recordsnpm@vitest/runner4.1.11
Change the conditions
Current conditions
@vitest/runner @4.1.11alpine 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
Evidence you can open
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @vitest/utils | 4.1.11 | contract passed | 3 project-days |
| pathe | 2.0.3 | contract passed | 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.
Recent failure clusters
-
observed PROJECT_TEST exit 1 ERR_LOAD_URL ×1 4.1.11 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:a60e7101af87…Contract test failed: Error: Failed to load custom Reporter from basic · at loadCustomReporterModule (fil<path>:<n>:<n>) · at fil<path>:<n>:<n> …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31