Records npmvitest

Coverage gap requested. The version and API coordinates listed below remain unanswered. This does not mean other versions or APIs of this package lack samples or compatibility evidence.

@3.2.7 · expect.toBe · 2 anonymous daily reports
@3.2.7 · it.each · 2 anonymous daily reports
@3.2.4 · describe · 2 anonymous daily reports
@3.2.4 · expect · 2 anonymous daily reports
@3.2.4 · it · 2 anonymous daily reports
@3.2.7 · expect · 2 anonymous daily reports
@3.2.7 · it · 2 anonymous daily reports
@3.2.7 · vi.mock · 2 anonymous daily reports
@3.2.7 · vi.mocked · 2 anonymous daily reports
@3.0.0 · 2 anonymous daily reports
@3.2.7 · expect.rejects.toThrow · 1 anonymous daily report
@3.2.7 · expect.objectContaining · 1 anonymous daily report
@3.2.7 · expect.rejects.toMatchObject · 1 anonymous daily report
@3.2.7 · expect.toThrow · 1 anonymous daily report
@3.0.0 · expect.toHaveBeenCalledWith · 1 anonymous daily report
@3.0.0 · vi.mock · 1 anonymous daily report
@3.0.0 · vi.mocked · 1 anonymous daily report
@3.2.7 · fileParallelism · 1 anonymous daily report
@3.2.7 · maxWorkers · 1 anonymous daily report
@3.2.7 · mockImplementation · 1 anonymous daily report
@3.2.7 · testTimeout · 1 anonymous daily report
@3.2.7 · vitest --maxWorkers · 1 anonymous daily report
@3.2.7 · vitest fileParallelism · 1 anonymous daily report
@3.2.7 · vitest maxWorkers · 1 anonymous daily report
@3.2.7 · expect.arrayContaining · 1 anonymous daily report
@3.2.7 · rejects.toThrow · 1 anonymous daily report
@3.2.7 · test · 1 anonymous daily report
@3.0.0 · vi · 1 anonymous daily report
@3.2.7 · vitest.expect.toBeNull · 1 anonymous daily report
@4.0.18 · expect · 1 anonymous daily report
@4.0.18 · it · 1 anonymous daily report
@3.2.4 · describe.runIf · 1 anonymous daily report
@3.0.0 · describe · 1 anonymous daily report
@3.0.0 · expect · 1 anonymous daily report
@3.0.0 · it · 1 anonymous daily report
@3.2.7 · describe · 1 anonymous daily report
@3.2.7 · globalSetup · 1 anonymous daily report
@3.2.7 · 1 anonymous daily report

Change the conditions

Current conditions

createVitest @4.1.11x64 · node 22 · 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 (1)

Project observations: 8 / 9
Contract verifications: 1 / 1
Independent reporting peers: 1
Last recorded: 2026-08-28

Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Open the next level

Verified — this network ran a contract at this coordinate.
ubuntu glibc · x64 · node 22 · npm 10 · node

8 of 9 passed

Open the next level

Observed — real project builds reported from this coordinate.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 18 · Steady 7

First observed break

3.2.7

windows · node@24.13 · executionContext=node · moduleSystem=esm

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster

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/expect	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/mocker	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/pretty-format	4.1.11	4.1.10	4.0.18	4.0.16	4.0.0	3.2.7	3.2.7	3.2.7	2.1.9
@vitest/runner	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/snapshot	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
@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
es-module-lexer	2.3.2	2.3.2	1.7.0	1.7.0	1.7.0	—	—	—	—
expect-type	1.4.0	1.4.0	1.4.0	1.3.0	1.4.0	1.4.0	1.4.0	1.4.0	1.4.0
obug	2.1.4	2.1.4	2.2.1	2.1.1	—	—	—	—	—
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
picomatch	4.0.7	4.0.5	4.0.7	4.0.3	4.0.5	4.0.5	4.0.7	—	—
std-env	4.2.0	4.2.0	3.10.0	3.10.0	3.10.0	3.10.0	3.10.0	3.10.0	3.10.0
tinyexec	1.3.0	1.3.0	1.3.1	1.0.2	0.3.2	0.3.2	0.3.2	0.3.2	0.3.2
tinyglobby	0.2.17	0.2.17	0.2.17	0.2.15	0.2.17	0.2.17	0.2.17	—	—
tinyrainbow	3.1.1	3.1.1	3.1.1	3.0.3	3.1.1	2.0.0	2.0.0	2.0.0	1.2.0
vite	8.2.2	8.2.1	7.3.6	7.3.1	7.3.6	7.3.6	7.3.6	6.4.3	5.4.21
vite-node	—	—	—	—	—	3.2.4	3.2.4	3.0.0	2.1.9
@types/chai	—	—	—	—	—	5.2.3	5.2.3	—	—
chai	—	—	—	—	—	5.3.3	5.3.3	5.3.3	5.3.3
debug	—	—	—	—	4.4.3	4.4.3	4.4.3	4.4.3	4.4.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
tinybench	2.9.0	2.9.0	2.9.0	2.9.0	2.9.0	2.9.0	2.9.0	2.9.0	2.9.0
tinypool	—	—	—	—	—	1.1.1	1.1.1	1.1.1	1.1.1
why-is-node-running	2.3.0	2.3.0	2.3.0	2.3.0	2.3.0	2.3.0	2.3.0	2.3.0	2.3.0

Moved: 18 · unchanged at every release: 7

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.