Recordsnpmvite8.2.1expect.toStrictEqual
shared with 2 packages — this evidence cannot say whose API it is
Published samples
- vite 8.2.1: Run a real vitest suite with no network, and know which of its matchers disagree with each other 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. HOWexpect.toEqualexpect.toStrictEqualexpect.rejectsexpect.toThrowvi.useFakeTimersvi.advanceTimersByTimevi.advanceTimersByTimeAsyncstartVitestnode 22 MIT-0 · 2026-08-14
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.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 2✓
|
MEDIUM | 1 | 2 | 100% | 1 · 2✓ | 2026-09-08 |
snapshot · 2026-09-15
Failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×5 7.3.6 → 8.2.1 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate