Bump @vitest/coverage-v8 from 3.2.4 to 4.1.2#381
Bump @vitest/coverage-v8 from 3.2.4 to 4.1.2#381dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.4 to 4.1.2. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.2/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
requested review from
a team,
CarlosGamero,
drdaemos and
kibertoad
as code owners
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe pull request updates the Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 74: package.json currently has a major version mismatch:
`@vitest/coverage-v8` is ^4.1.2 while vitest is still 3.2.4; update vitest to
^4.1.2 to match the coverage plugin and then update vitest.config.mts to remove
the deprecated all: true setting and replace it with explicit
coverage.include/glob patterns per Vitest v4 breaking changes (verify any other
v4 config keys). Ensure package.json dependency "vitest" version and
"@vitest/coverage-v8" align and that vitest.config.mts no longer uses all: true
but defines coverage.include appropriately.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 734fceff-2c6c-46c8-9c13-94a5e1cc38bd
📒 Files selected for processing (1)
package.json
| "@types/newrelic": "^9.14.8", | ||
| "@types/node": "^24.7.0", | ||
| "@vitest/coverage-v8": "^3.2.4", | ||
| "@vitest/coverage-v8": "^4.1.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check vitest v4 compatibility requirements and configuration
echo "=== Checking vitest config for deprecated v3 options ==="
rg -n -A2 -B2 'reporter:' vitest.config.mts
echo -e "\n=== Checking if vitest package needs to be updated ==="
cat package.json | jq -r '.devDependencies.vitest, .devDependencies."@vitest/coverage-v8"'Repository: lokalise/fastify-extras
Length of output: 402
🌐 Web query:
vitest v4 coverage-v8 compatibility requirements and breaking changes
💡 Result:
Vitest v4 compatibility requirements for coverage-v8: Requires Vite >=6.0.0 and Node.js >=20.0.0. Install @vitest/coverage-v8 and set coverage.provider: 'v8' (default provider). Breaking changes in v4 for coverage-v8: - Switched to new AST-based remapping (from v8-to-istanbul), providing more accurate coverage matching Istanbul; expect changes in reports, fewer false positives. - coverage.ignoreEmptyLines removed (empty lines without runtime code excluded by default). - coverage.experimentalAstAwareRemapping removed (now always on). - coverage.all and coverage.extensions removed; default to including only files loaded during tests. Explicitly set coverage.include (e.g., ['packages//src/.{js,ts}']) for uncovered files. - Updated ignore hints to Istanbul-compatible: use /* v8 ignore next /, / v8 ignore start / ... / v8 ignore stop /, often with -- @preserve (/ v8 ignore next -- @preserve /). See docs for full syntax. - coverage.ignoreClassMethods now supported. - V8-specific: Requires V8 runtime (Node.js, Chrome); no pre-instrumentation, but minor V8 limitations apply. Config example: export default defineConfig({ test: { coverage: { provider: 'v8', include: ['src//.{js,ts}'], exclude: ['src//.test.ts'], }, }, }); Run with npx vitest --coverage. V8 remains default and recommended for speed + accuracy.
Citations:
- 1: https://github.com/vitest-dev/vitest/releases/tag/v4.0.0
- 2: https://vitest.dev/guide/migration.html
- 3: https://www.npmjs.com/package/@vitest/coverage-v8
- 4: https://v4.vitest.dev/guide/migration
- 5: https://v4.vitest.dev/guide/coverage
- 6: https://vitest.dev/guide/coverage
- 7: https://v4.vitest.dev/config/coverage
- 8: https://main.vitest.dev/guide/migration.html
Critical: Version mismatch between @vitest/coverage-v8 (v4.1.2) and vitest core (v3.2.4).
The @vitest/coverage-v8 package is updated to v4.1.2, but vitest itself (line 86) remains at v3.2.4. This major version mismatch will break coverage functionality. Additionally, the vitest.config.mts uses all: true (line 23), which was removed in v4 as part of breaking changes that require explicit coverage.include configuration instead.
Update vitest to ^4.1.2 to match the coverage plugin version, and audit the coverage configuration for v4 breaking changes including removal of coverage.all and requirement for explicit coverage.include.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 74, package.json currently has a major version
mismatch: `@vitest/coverage-v8` is ^4.1.2 while vitest is still 3.2.4; update
vitest to ^4.1.2 to match the coverage plugin and then update vitest.config.mts
to remove the deprecated all: true setting and replace it with explicit
coverage.include/glob patterns per Vitest v4 breaking changes (verify any other
v4 config keys). Ensure package.json dependency "vitest" version and
"@vitest/coverage-v8" align and that vitest.config.mts no longer uses all: true
but defines coverage.include appropriately.
Bumps @vitest/coverage-v8 from 3.2.4 to 4.1.2.
Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
fc6f482chore: release v4.1.21f2d318chore: release v4.1.1aaf9f18fix(coverage): simplify provider types (#9931)4150b91chore: release v4.1.00c2c013chore: release v4.1.0-beta.6689a22afix(browser): types ofgetCDPSessionandcdp()(#9716)94eb73bchore(deps): update eslint packages (#9615)8c96bb0refator: update links to npmx (#9783)aaf7758chore: standardize packages README (#9776)57cbe39chore(deps): updateast-v8-to-istanbulto v1 (#9755)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@vitest/coverage-v8since your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)