CodeSampleX

Recordsnpm@vitest/runner4.1.10@vitest/runner.afterEach

Change the conditions
Fixed
Package version4.1.10 Symbol@vitest/runner.afterEach Package managernpm
Filter OSdebian glibc Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@vitest/runner.afterEach @4.1.10debian glibc · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

4.1.10

executionContext=node

6 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
@vitest/utils 4.1.10 CANDIDATE Correlated change; unproven combination contract passed 24 project-days
pathe 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 24 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.

Library4.1.114.1.104.0.184.0.164.0.03.2.73.2.43.0.02.1.9
@vitest/utils 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
pathe 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 2.0.3 1.1.2
strip-literal — — — — — 3.1.0 3.1.0 — —

Moved: 2 · unchanged at every release: 1

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