Skip to content

pair @vitest/coverage-v8 with the vitest 5 major (main is ERESOLVE-broken) - #66

Merged
ronaldtse merged 1 commit into
mainfrom
vitest5-pair
Sep 7, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
vitest5-pair

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

What

Bumps @vitest/coverage-v8 to ^5.0.0, pairing it with the vitest ^5.0.0 major that dependabot's #39 merged without its peer.

Why

Main is currently red: npm install fails ERESOLVE (@vitest/coverage-v8@4.1.10 cannot resolve against vitest@5.0.0), failing every job at the install step.

Verification

  • npm install resolves clean (vitest@5.0.0 deduped with @vitest/coverage-v8@5.0.0)
  • Suite matches pristine-main behavior: 237 passed; the 11 cli.test.ts failures are the known local-environment artifact (fail identically on unmodified main locally while CI is green)

Dependabot merged the vitest ^5.0.0 major (#39) without its
coverage-v8 peer, leaving main's npm install ERESOLVE-broken. This
bumps @vitest/coverage-v8 to the matching ^5.0.0 - install resolves
clean (deduped 5.0.0 pair) and the suite matches pristine main
(237 passed; the 11 cli failures are the known local-env artifact,
CI-green on main).
@ronaldtse
ronaldtse merged commit 1c7b16e into main Sep 7, 2026
8 checks passed
@ronaldtse
ronaldtse deleted the vitest5-pair branch September 7, 2026 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant