Recordsnpmjest29.7.0expect.toStrictEqual
Published samples
- jest 29.7.0: expect(a).toEqual(b) and expect(a).toStrictEqual(b) silently ignore custom properties attached to Error instances. 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.toStrictEqualnode MIT-0 · 2026-08-17
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 2✓
|
MEDIUM | 0 | 2 | 100% | 0 · 2✓ | 2026-08-18 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×5 29.6.3 → 29.7.0 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-16 · Last seen: 2026-08-16Diagnostic re-verification candidate