Recordsnpmvitest4.1.10expect.rejects
shared with 2 packages — this evidence cannot say whose API it is
Published samples
- vitest 4.1.10: 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
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-18 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×1 4.1.10 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-14 · Last seen: 2026-08-14