Issues · vitest-dev/vitest · GitHub

Labels Milestones New issue

First stderr entry shares timestamp with preceding stdout entry in custom reporters

#10307

· aslushnikov opened

on May 8, 2026

`concurrencyId` not exposed to custom reporters

enhancement: pending triage

#10306

· aslushnikov opened

on May 8, 2026

`UserConsoleLog` type is not exported from vitest

enhancement: pending triage

#10305

· aslushnikov opened

on May 8, 2026

Custom reporters can't access test tags

enhancement: pending triage

#10304

· aslushnikov opened

on May 8, 2026

Custom reporters can't access per-attempt details for retries

enhancement: pending triage

#10303

· aslushnikov opened

on May 8, 2026

`hasText` option is available in `getByRole(..., { hasText })` but no-op

#10295

· hi-ogawa opened

on May 8, 2026

Have a `strictModuleType` option to disable CJS-ESM interop

p2-nice-to-have

#10292

· sheremet-va opened

on May 7, 2026

Module mocking regression from Vitest 3 to Vitest 4

#10290

· patrickshipe opened

on May 7, 2026

Code coverage file overmatching when one package path is substring of another

#10289

· alecgibson opened

on May 7, 2026

Add `const T` type parameter to `it.each`/`describe.each` to preserve type narrowness

enhancement: pending triage

#10282

· Bertie690 opened

on May 6, 2026

expect().resolves does not accept a function

p2-nice-to-have

#10281

· IIIMADDINIII opened

on May 6, 2026

Types exports from vitest/browser are not found by typescript when using npm workspaces

#10280

· julienw opened

on May 6, 2026