Skip to content

Conversation

@ibrahimcesar
Copy link
Owner

Problem

CI builds are failing with this error:

npm error ERESOLVE could not resolve
npm error While resolving: @vitest/coverage-v8@4.0.10
npm error Found: vitest@3.2.4
npm error Could not resolve dependency:
npm error peer vitest@"4.0.10" from @vitest/coverage-v8@4.0.10

Root Cause

Version mismatch between dependencies:

  • vitest: ^3.2.4
  • @vitest/coverage-v8: ^4.0.10 (requires vitest@4.0.10)

The coverage package v4.x has a peer dependency on vitest v4.x, but we're using vitest v3.2.4.

Solution

Downgrade @vitest/coverage-v8 from ^4.0.10 to ^3.2.4 to match the vitest version.

Changes

  • @vitest/coverage-v8: ^4.0.10^3.2.4
  • Updated package-lock.json with compatible versions

Testing

✅ All 51 tests passing
✅ No vulnerabilities found
npm install succeeds without errors

Impact

  • Fixes all CI build failures
  • No breaking changes
  • No functionality changes
  • Same test coverage capabilities

This is a quick fix that should be merged to unblock CI. We can upgrade to vitest v4.x and coverage v4.x together in a future PR if needed.

ibrahimcesar and others added 2 commits November 20, 2025 11:21
Fixed ERESOLVE error in CI caused by version mismatch between
vitest and @vitest/coverage-v8.

Changed:
- @vitest/coverage-v8: ^4.0.10 → ^3.2.4

The @vitest/coverage-v8@4.x package requires vitest@4.x as a peer
dependency, but we're using vitest@3.2.4. Downgrading the coverage
package to v3.2.4 resolves the peer dependency conflict.

Tests: ✅ 51/51 passing
Vulnerabilities: 0

Fixes CI build failures in GitHub Actions.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@ibrahimcesar ibrahimcesar changed the title fix: Resolve vitest peer dependency conflict fix: resolve vitest peer dependency conflict Nov 20, 2025
@ibrahimcesar ibrahimcesar merged commit 4fe77d9 into main Nov 20, 2025
7 of 9 checks passed
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.

2 participants