Recordsnpmvitest4.0.16vitest.it
Change the conditions
Current conditions
vitest.it @4.0.16windows 11 · x64 · node 24 · npm 11 · node
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
- 19 / 66
- Contract verifications
- 0 / 9
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 20 ·
Steady 0
First observed break
4.0.16 @vitest/expect@4.0.16
windows · node@24.13 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @vitest/expect | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/mocker | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/pretty-format | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/runner | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/snapshot | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/spy | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| @vitest/utils | 4.0.16 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| es-module-lexer | 1.7.0 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| expect-type | 1.3.0 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| magic-string | 0.30.21 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| obug | 2.1.1 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| pathe | 2.0.3 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| picomatch | 4.0.3 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| std-env | 3.10.0 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| tinybench | 2.9.0 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| tinyexec | 1.0.2 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| tinyglobby | 0.2.15 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| tinyrainbow | 3.0.3 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| vite | 7.3.1 | FAIL Linked failure observed; version changed across releases | contract passed | 1 project-day |
| why-is-node-running | 2.3.0 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
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.
Moved: 18 · unchanged at every release: 7
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_COMPILE exit 2 TS2307 ×4 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:0470f88d95bb…lib/hooks/queries/index.ts(<n>,<n>): error TS2307: Cannot find module <str> or its corresponding type declarations. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS7006 ×4 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:21025cd78572…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2561 ×4 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:5f96e966539e…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2561: Object literal may only specify known properties, but <str> does not exist in type …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2345 ×4 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:7e077f646acc…lib/api/real-estate-statistics.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2551 ×4 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:8a1ebc675f2b…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2551: Property <str> does not exist on type <str>. Did you mean <str>? …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2339 ×4 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:e51205820175…lib/api/real-estate-map-addresses.ts(<n>,<n>): error TS2339: Property <str> does not exist on type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2305 ×4 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:e7aa54217e13…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2345 ×2 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:0d787687eb6d…lib/services/sync-service.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2322 ×2 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:398ffe6fb765…lib/api/records/politician-records.ts(<n>,<n>): error TS2322: Type <str> is not assignable to type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2305 ×2 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:4c6770254770…app/factcheck/[id]/layout.tsx(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2339 ×2 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:a2b1d30276e3…lib/api/politicians/detail.ts(<n>,<n>): error TS2339: Property <str> does not exist on type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2694 ×2 4.0.16 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 vitest.it sha256:a62486f02028…app/api/users/[id]/activities/route.ts(<n>,<n>): error TS2694: Namespace <str> has no exported member <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
Showing the 12 most-reported of 15 recorded failure clusters. The rest are single reports.