Recordsnpm@vitest/runner4.1.11
Change the conditions
Current conditions
@vitest/runner @4.1.11windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
0 of 12 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (7)
- Project observations
- 74 / 97
- Contract verifications
- 0 / 12
- Usage records
- 35
- Independent reporting peers
- 1
- Last recorded
- 2026-09-13
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 2 ·
Steady 0
First observed break
4.1.11
linux · node@22.23 · moduleSystem=esm · executionContext=node
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @vitest/utils | 4.1.11 | CANDIDATE Correlated change; unproven combination | contract passed | 18 project-days |
| pathe | 2.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 18 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 |
|---|---|---|---|---|---|---|---|---|---|
| @vitest/utils | 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 |
| pathe | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 2.0.3 | 1.1.2 |
| strip-literal | — | — | — | — | — | 3.1.0 | 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.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×3 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:3e5f03903e29…<str> is not recognized as an internal or external command, · operable program or batch file. · > prism@0.1.0 test · > vitest runnpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×2 2.1.9 → 4.1.11 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-19 · Last seen: 2026-08-21Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ×2 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:87a2d9024768…[31m[1mAssertionError[22m: expected [ { kind: <str>, …(2) } ] to deeply equal [][39m · [32m- Expected[39m · [31m+ Received[39m · [32m- [][39mjavascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed UNKNOWN exit 1 Evidence gap ×2 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:2a222a8f384c…<str> is not recognized as an internal or external command, · operable program or batch file. · > gptbrowser@0.1.0 test · > vitest runnpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ×2 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:63f66b355db5…FAIL src/main/sources/runtime/electronPageWiring.test.ts > production source runtime wiring > backs a context with an ElectronSourcePage and loads the initial …· test-runner-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_TEST exit 1 ×2 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:e3ee590485ca…FAIL src/main/sources/runtime/sourceActions.test.ts [ src/main/sources/runtime/sourceActions.test.ts ] …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed UNKNOWN exit 1 Evidence gap ×2 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:4623f6ba5821…[31m⎯⎯⎯⎯⎯⎯[39m[1m[41m Failed Suites 1 [49m[22m[31m⎯⎯⎯⎯⎯⎯⎯[39m …vitest · unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 TS6133 ×1 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:055e5bd1ac52…src/shared/planner/mixInvariants.ts(<n>,<n>): error TS6133: <str> is declared but its value is never read.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS2740 ×1 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:10c0789adef8…src/preload/index.ts(<n>,<n>): error TS2740: Type <str> is missing the following properties from type <str>: sourceAction, sourceProject, authRailOpen, …typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS2554 ×1 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:4ae5785d6b8c…src/main/sources/runtime/sourceRuntime.test.ts(<n>,<n>): error TS2554: Expected 3 arguments, but got 4.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS2741 ×1 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:a1abf8af37d8…src/main/ipcHandlers.ts(<n>,<n>): error TS2741: Property <str> is missing in type <str> but required in type <str>.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_COMPILE exit 1 TS6133 ×1 4.1.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:d8ea1c73763a…src/main/sources/runtime/sourceRuntime.test.ts(<n>,<n>): error TS6133: <str> is declared but its value is never read. …typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
Showing the 12 most-reported of 29 recorded failure clusters. The rest are single reports.