Recordsnpm@vitest/expectfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
fil<path>:<n> · throw Error( · ^ · Error: Invalid Chai property: toSatisfy. Did you mean <str>?
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:994722463fe8…
@vitest/expect.Any @vitest/expect.Anything @vitest/expect.ArrayContaining @vitest/expect.ChaiStyleAssertions @vitest/expect.JestAsymmetricMatchers @vitest/expect.JestChaiExpect @vitest/expect.JestExtend @vitest/expect.ObjectContaining @vitest/expect.SchemaMatching @vitest/expect.StringContaining @vitest/expect.StringMatching @vitest/expect.equals @vitest/expect.getState @vitest/expect.hasAsymmetric @vitest/expect.isA @vitest/expect.isAsymmetric @vitest/expect.isStandardSchema @vitest/expect.setState
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-08-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.
| Library | 4.1.11 | 4.1.10 | 4.0.18 | 4.0.16 |
|---|---|---|---|---|
| @standard-schema/spec | 1.1.0 | 1.1.0 | 1.1.0 | 1.0.0 |
| @vitest/spy | 4.1.11 | 4.1.10 | 4.0.18 | 4.0.16 |
| @vitest/utils | 4.1.11 | 4.1.10 | 4.0.18 | 4.0.16 |
| tinyrainbow | 3.1.1 | 3.1.1 | 3.1.1 | 3.0.3 |
| @types/chai | 5.2.3 | 5.2.3 | 5.2.3 | 5.2.3 |
| chai | 6.2.2 | 6.2.2 | 6.2.2 | 6.2.2 |
Moved: 4 · unchanged at every release: 2
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.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @vitest/expect 4.1.11 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. HOWnode 22.23.2 MIT-0 · 2026-08-28