Skip to content

chore(deps-dev): bump vitest from 1.6.1 to 4.1.0 in the npm_and_yarn group across 1 directory #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps-dev): bump vitest from 1.6.1 to 4.1.0 in the npm_and_yarn group across 1 directory #34

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/transpiler/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,6 @@
"@typescript-eslint/eslint-plugin": "^7.0.0",
"@typescript-eslint/parser": "^7.0.0",
"@vitest/coverage-v8": "^1.6.1",
"vitest": "^1.6.0"
"vitest": "^4.1.0"
Comment on lines 42 to +43
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Jun 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify vitest package-family alignment in manifest + lockfile (read-only)
set -euo pipefail

echo "== package.json =="
rg -n '"(`@vitest/coverage-v8`|vitest)"\s*:' packages/transpiler/package.json

echo
echo "== pnpm-lock.yaml (resolved entries) =="
rg -n '^(\s{2}`@vitest/coverage-v8`@|\s{2}vitest@)' pnpm-lock.yaml

Repository: OpenDevFlow/md-latex

Length of output: 310

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== pnpm-lock.yaml: any `@vitest/coverage-v8` entries =="
rg -n '`@vitest/coverage-v8`' pnpm-lock.yaml

echo
echo "== pnpm-lock.yaml: narrow to resolved headings like '`@vitest/coverage-v8`@x.y.z:' =="
rg -n '^[[:space:]]{2}`@vitest/coverage-v8`@' pnpm-lock.yaml || true

echo
echo "== pnpm-lock.yaml: narrow to any 'coverage-v8@' occurrences =="
rg -n 'coverage-v8@' pnpm-lock.yaml

Repository: OpenDevFlow/md-latex

Length of output: 628

🌐 Web query:

@vitest/coverage-v8 version 1.6.1 compatibility with vitest 4.x

💡 Result:

@vitest/coverage-v8 1.6.1 is not something you should rely on for Vitest 4.x compatibility. The authoritative vitest/coverage-v8 docs and package metadata indicate the V8 coverage provider is tightly coupled to specific Vitest versions (it declares peerDependencies on Vitest and @vitest/browser for the provider build) and Vitest 4.x users should use a matching/newer @vitest/coverage-v8 release. What we can confirm from sources: 1) @vitest/coverage-v8 is designed as a Vitest “coverage provider” selected via test.coverage.provider = 'v8' and requires installing it as the support package [1]. 2) The package specifies peer dependencies on vitest (and @vitest/browser) for the provider implementation, which is a strong signal that a particular provider version is meant to align with a particular Vitest major/minor line [2]. 3) Vitest 4.0 introduced “V8 code coverage major changes” in the migration guide, indicating that coverage behavior/implementation is expected to change across Vitest majors and therefore older provider versions may not match expectations [3]. 4) There are also reported issues specifically around Vitest 4.x dynamically importing @vitest/coverage-v8 when coverage.provider is set to "v8", which points to runtime/provider-resolution details that may break depending on install layout and versions [4]. Practical recommendation: - For Vitest 4.x, upgrade @vitest/coverage-v8 to the corresponding 4.x-compatible release (rather than pinning to 1.6.1). Vitest’s coverage provider docs emphasize selecting and installing the provider package, and the provider versioning/peerDependencies indicate you need an aligned version [1][2]. If you tell me your exact versions (vitest version, v3/v4 minor, and your package manager: npm/yarn/pnpm), I can suggest the safest @vitest/coverage-v8 version to use and any monorepo/workspace configuration pitfalls.

Citations:

🌐 Web query:

@vitest/coverage-v8 4.1.0 peerDependencies vitest

💡 Result:

In version 4.1.0 of @vitest/coverage-v8, the package does not explicitly list vitest as a peerDependency [1][2]. However, beginning with version 4.1.3, @vitest/coverage-v8 (and @vitest/coverage-istanbul) were added as optional dependencies to the main vitest package to resolve issues with dependency resolution in strict package manager environments like pnpm [3][4]. Prior to this change, users encountering resolution errors in monorepos or strict environments were advised to manually configure peer dependencies via package manager extensions (such as pnpm's packageExtensions) [3].

Citations:

Align @vitest/coverage-v8 with Vitest 4.x

packages/transpiler/package.json uses vitest:^4.1.0 but @vitest/coverage-v8:^1.6.1; pnpm-lock.yaml resolves @vitest/coverage-v8@1.6.1 alongside vitest@4.1.0, which can break Vitest 4 coverage. Update the coverage provider to the Vitest-4 line (e.g. ^4.1.3).

Suggested fix 
   "devDependencies": {
-    "`@vitest/coverage-v8`": "^1.6.1",
+    "`@vitest/coverage-v8`": "^4.1.3",
     "vitest": "^4.1.0"
   }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"@vitest/coverage-v8": "^1.6.1",
"vitest": "^1.6.0"
"vitest": "^4.1.0"
"`@vitest/coverage-v8`": "^4.1.3",
"vitest": "^4.1.0"
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/transpiler/package.json` around lines 42 - 43, Update the
`@vitest/coverage-v8` dependency in packages/transpiler/package.json to the Vitest
4.x compatible line (e.g., change "`@vitest/coverage-v8`": "^1.6.1" to a 4.x
version such as "^4.1.3") so it matches the installed vitest ("vitest":
"^4.1.0"); modify the dependency entry for "`@vitest/coverage-v8`" in package.json
and run your lockfile installer (pnpm install) to regenerate pnpm-lock.yaml and
ensure the resolved version aligns with vitest 4.x.

}
}
Loading
Loading