Records/npm/vitest/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 4.1.11 PASS 9 passing observations
• 4.1.10 FAIL
• 4.0.18 PASS 6 passing observations
• 4.0.16 PASS 11 passing observations
• 4.0.0 not measured

Where it reproduced

• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-14 → 2026-08-14

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 4.0.18 → first failing release 4.1.10

  What differs across the boundary

  • @vitest/expect 4.0.18 → 4.1.10 hypothesis
  • @vitest/mocker 4.0.18 → 4.1.10 hypothesis
  • @vitest/pretty-format 4.0.18 → 4.1.10 hypothesis
  • @vitest/runner 4.0.18 → 4.1.10 hypothesis
  • @vitest/snapshot 4.0.18 → 4.1.10 hypothesis
  • @vitest/spy 4.0.18 → 4.1.10 hypothesis
  • @vitest/utils 4.0.18 → 4.1.10 hypothesis
  • es-module-lexer 1.7.0 → 2.3.1, 2.3.2 hypothesis
  • obug 2.2.1 → 2.1.4 hypothesis
  • picomatch 4.0.7 → 4.0.5 hypothesis
  • std-env 3.10.0 → 4.2.0 hypothesis
  • tinyexec 1.3.1 → 1.3.0 hypothesis
  • vite 7.3.6 → 8.2.1 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release 4.1.10 → first passing release 4.1.11

  What differs across the boundary

  • @vitest/expect 4.1.11 → 4.1.10 hypothesis
  • @vitest/mocker 4.1.11 → 4.1.10 hypothesis
  • @vitest/pretty-format 4.1.11 → 4.1.10 hypothesis
  • @vitest/runner 4.1.11 → 4.1.10 hypothesis
  • @vitest/snapshot 4.1.11 → 4.1.10 hypothesis
  • @vitest/spy 4.1.11 → 4.1.10 hypothesis
  • @vitest/utils 4.1.11 → 4.1.10 hypothesis
  • es-module-lexer 2.3.2 → 2.3.1, 2.3.2 hypothesis
  • picomatch 4.0.5, 4.0.7 → 4.0.5 hypothesis
  • vite 7.3.6, 8.2.2 → 8.2.1 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

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: 16 · unchanged at every release: 5

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.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_PROCESS: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• vitest 4.1.10: Parse CLI arguments with parseCLI in vitest/node to enforce binary token validation, route positional test filters, normalize boolean and dot-notation options, and configure execution modes. Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWparseCLInode MIT-0 · 2026-08-17
• vitest 4.1.10: Differentiate mockReset, mockRestore, and mockClear lifecycle on vi.spyOn and vi.fn instances in Vitest Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWvi.spyOnvi.fnmockResetmockRestoremockClearnode MIT-0 · 2026-08-16
• vitest 4.1.10: Differentiate per-file test environments, docblock precedence over project configs, sequential setupFiles DOM lifecycle, and globals:true symbol exposure in Vitest 4 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcreateVitestenvironmentenvironmentMatchGlobssetupFilesglobalsnode MIT-0 · 2026-08-15