Records/npm/vitest/4.1.10/globals

shared with 2 packages — this evidence cannot say whose API it is

Published samples

• 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

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-08-30

Failure clusters

• observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×5 3.2.7 → 4.1.10 executionContext=node · moduleSystem=esm
  Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30
  Diagnostic re-verification candidate