CodeSampleX

Compatibilitynpmvitest4.1.11vitest.afterEach

Change the conditions
Fixed
OSubuntu glibc Package version4.1.11 Symbolvitest.afterEach
Filter Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

vitest.afterEach @4.1.11ubuntu glibc · x64 · node 22 · npm 10 · node

4 of 5 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
4 / 5
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
@vitest/expect 4.1.11 contract passed 1 project-day
@vitest/mocker 4.1.11 contract passed 1 project-day
@vitest/pretty-format 4.1.11 contract passed 1 project-day
@vitest/runner 4.1.11 contract passed 1 project-day
@vitest/snapshot 4.1.11 contract passed 1 project-day
@vitest/spy 4.1.11 contract passed 1 project-day
@vitest/utils 4.1.11 contract passed 1 project-day
es-module-lexer 2.3.2 contract passed 1 project-day
expect-type 1.4.0 contract passed 1 project-day
magic-string 0.30.21 contract passed 1 project-day
obug 2.1.4 contract passed 1 project-day
pathe 2.0.3 contract passed 1 project-day
picomatch 4.0.7 contract passed 1 project-day
std-env 4.2.0 contract passed 1 project-day
tinybench 2.9.0 contract passed 1 project-day
tinyexec 1.3.0 contract passed 1 project-day
tinyglobby 0.2.17 contract passed 1 project-day
tinyrainbow 3.1.1 contract passed 1 project-day
vite 8.2.2 builds observed 1 project-day
why-is-node-running 2.3.0 contract passed 1 project-day

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.113.2.72.1.9
@vitest/expect 4.1.11 3.2.7 2.1.9
@vitest/mocker 4.1.11 3.2.7 2.1.9
@vitest/pretty-format 4.1.11 3.2.7 2.1.9
@vitest/runner 4.1.11 3.2.7 2.1.9
@vitest/snapshot 4.1.11 3.2.7 2.1.9
@vitest/spy 4.1.11 3.2.7 2.1.9
@vitest/utils 4.1.11 3.2.7 2.1.9
pathe 2.0.3 2.0.3 1.1.2
picomatch 4.0.7 4.0.5
std-env 4.2.0 3.10.0 3.10.0
tinyexec 1.3.0 0.3.2 0.3.2
tinyrainbow 3.1.1 2.0.0 1.2.0
vite 8.2.2 7.3.6 5.4.21
vite-node 3.2.4 2.1.9
@types/chai 5.2.3
chai 5.3.3 5.3.3
debug 4.4.3 4.4.3
es-module-lexer 2.3.2
expect-type 1.4.0 1.4.0 1.4.0
magic-string 0.30.21 0.30.21 0.30.21
obug 2.1.4
tinybench 2.9.0 2.9.0 2.9.0
tinyglobby 0.2.17 0.2.17
tinypool 1.1.1 1.1.1
why-is-node-running 2.3.0 2.3.0 2.3.0

Moved: 14 · unchanged at every release: 11

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