Recordsnpm@vitest/mocker4.1.11@vitest/mocker.collectModuleExports
Change the conditions
Current conditions
@vitest/mocker.collectModuleExports @4.1.11ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (2)
- Project observations
- 3 / 3
- Contract verifications
- 0 / 3
- Independent reporting peers
- 2
- Last recorded
- 2026-09-01
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.1.11
windows · node@24.13 · executionContext=node · moduleSystem=cjs
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @vitest/spy | 4.1.11 | CANDIDATE Correlated change; unproven combination | contract passed | 15 project-days |
| estree-walker | 3.0.3 | PASS All observations passed | contract passed | 15 project-days |
| magic-string | 0.30.21 | PASS All observations passed | contract passed | 15 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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 | 4.0.0 | 3.2.7 | 3.2.4 | 3.0.0 | 2.1.9 |
|---|---|---|---|---|---|---|---|---|---|
| @vitest/spy | 4.1.11 | 4.1.10 | 4.0.18 | 4.0.16 | 4.0.0 | 3.2.7 | 3.2.4 | 3.0.0 | 2.1.9 |
| estree-walker | 3.0.3 | 3.0.3 | 3.0.3 | 3.0.3 | 3.0.3 | 3.0.3 | 3.0.3 | 3.0.3 | 3.0.3 |
| magic-string | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 |
Moved: 1 · 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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 4.1.11 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 @vitest/mocker.collectModuleExports sha256:43caf7a060e7…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_LOAD_URL ×1 4.1.11 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:a60e7101af87…Contract test failed: Error: Failed to load custom Reporter from basic · at loadCustomReporterModule (fil<path>:<n>:<n>) · at fil<path>:<n>:<n> …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 4.1.11 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 @vitest/mocker.collectModuleExports sha256:10e769edac62…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate