Recordsnpmvitest3.2.7vitest.vi
Change the conditions
Current conditions
vitest.vi @3.2.7windows 11 · x64 · node 24 · pnpm 10 · node
0 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 22 / 24
- Contract verifications
- 0 / 2
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 1 / 2
- Last recorded
- 2026-08-29
Evidence you can open
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @types/chai | 5.2.3 | contract passed | 5 project-days |
| @vitest/expect | 3.2.7 | contract passed | 5 project-days |
| @vitest/mocker | 3.2.7 | contract passed | 4 project-days |
| @vitest/pretty-format | 3.2.7 | contract passed | 3 project-days |
| @vitest/runner | 3.2.7 | contract passed | 3 project-days |
| @vitest/snapshot | 3.2.7 | contract passed | 3 project-days |
| @vitest/spy | 3.2.7 | contract passed | 2 project-days |
| @vitest/utils | 3.2.7 | contract passed | 2 project-days |
| chai | 5.3.3 | contract passed | 2 project-days |
| debug | 4.4.3 | contract passed | 5 project-days |
| expect-type | 1.4.0 | contract passed | 2 project-days |
| magic-string | 0.30.21 | contract passed | 2 project-days |
| pathe | 2.0.3 | contract passed | 4 project-days |
| picomatch | 4.0.5 | contract passed | 2 project-days |
| picomatch | 4.0.7 | contract passed | 3 project-days |
| std-env | 3.10.0 | contract passed | 3 project-days |
| tinybench | 2.9.0 | contract passed | 2 project-days |
| tinyexec | 0.3.2 | contract passed | 3 project-days |
| tinyglobby | 0.2.17 | contract passed | 5 project-days |
| tinypool | 1.1.1 | contract passed | 3 project-days |
| tinyrainbow | 2.0.0 | contract passed | 2 project-days |
| vite | 7.3.6 | contract passed | 5 project-days |
| vite-node | 3.2.4 | contract passed | 4 project-days |
| why-is-node-running | 2.3.0 | contract passed | 2 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 | 3.2.7 | 2.1.9 |
|---|---|---|---|
| @vitest/expect | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/mocker | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/pretty-format | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/runner | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/snapshot | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/spy | 4.1.11 | 3.2.7 | 2.1.9 |
| @vitest/utils | 4.1.11 | 3.2.7 | 2.1.9 |
| pathe | 2.0.3 | 2.0.3 | 1.1.2 |
| picomatch | 4.0.7 | 4.0.5 | — |
| std-env | 4.2.0 | 3.10.0 | 3.10.0 |
| tinyexec | 1.3.0 | 0.3.2 | 0.3.2 |
| tinyrainbow | 3.1.1 | 2.0.0 | 1.2.0 |
| vite | 8.2.2 | 7.3.6 | 5.4.21 |
| vite-node | — | 3.2.4 | 2.1.9 |
| @types/chai | — | 5.2.3 | — |
| chai | — | 5.3.3 | 5.3.3 |
| debug | — | 4.4.3 | 4.4.3 |
| es-module-lexer | 2.3.2 | — | — |
| expect-type | 1.4.0 | 1.4.0 | 1.4.0 |
| magic-string | 0.30.21 | 0.30.21 | 0.30.21 |
| obug | 2.1.4 | — | — |
| tinybench | 2.9.0 | 2.9.0 | 2.9.0 |
| tinyglobby | 0.2.17 | 0.2.17 | — |
| tinypool | — | 1.1.1 | 1.1.1 |
| why-is-node-running | 2.3.0 | 2.3.0 | 2.3.0 |
Moved: 14 · unchanged at every release: 11
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 ×5 3.2.7 → 4.1.10 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed PROJECT_TEST ELIFECYCLE Evidence gap ×4 2.1.9 → 3.2.7 executionContext=node · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-21 · Last seen: 2026-08-26Diagnostic re-verification candidate
-
observed PROJECT_TEST Evidence gap ×2 2.1.9 → 3.2.7 executionContext=node · os=windows · runtime=node@24.13 vitest.viEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ELIFECYCLE ×1 3.2.7 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 vitest.vi sha256:7711694d48fa…ELIFECYCLE Test failed. See above for more details.javascript/test-runner · test-runner-diagnostic · outer pnpm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed UNKNOWN exit 1 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Evidence gap ×1 3.2.7 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 vitest.vi sha256:0903ef5db350…(node:<n>) ExperimentalWarning: SQLite is an experimental feature and might change at any time …pnpm · unclassified-diagnostic · outer pnpm · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Evidence gap ×1 3.2.7 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 vitest.vi sha256:d53178e9c23b…<str> is not recognized as an internal or external command, · operable program or batch file. · undefined · <path>pnpm · unclassified-diagnostic · outer pnpm · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate