update to latest vitest

[ymc9]

Summary by CodeRabbit

• Chores
  • Upgraded the development testing framework to a new major version for improved performance and features.
  • Updated IDE workspace extension recommendations to match the testing tooling.
  • Added a limit on testing configurations in the development environment to optimize performance.
  • Set the project to use ES module resolution mode for module handling.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated VSCode workspace recommendations and settings, added "type": "module" to package metadata, and bumped the Vitest devDependency from ^3.2.4 to ^4.0.14.

Changes

Cohort / File(s)	Change Summary
VSCode Workspace Configuration .vscode/extensions.json, .vscode/settings.json	Replaced workspace extension recommendation kingwl.vscode-vitest-runner → vitest.explorer and added "vitest.maximumConfigs": 20 to settings
Package manifest package.json	Added "type": "module" and upgraded devDependency vitest from ^3.2.4 to ^4.0.14

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Check compatibility implications of Vitest v4 (API changes or runner/config differences).
• Confirm "type": "module" does not break any CJS imports or tooling.
• Verify the new VSCode extension recommendation aligns with team tooling.

Poem

🐰
I hopped through JSON, tidy and bright,
Swapped a runner for an explorer's light,
Set configs to twenty, modules to new—
Vitest leaps forward, tests chase the dew. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'update to latest vitest' accurately summarizes the main change: upgrading vitest from ^3.2.4 to ^4.0.14, along with related configuration updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-vitest

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ca431c8 and 42479ba.

📒 Files selected for processing (1)

• package.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: build-test (20.x, sqlite)
• GitHub Check: build-test (20.x, postgresql)
• GitHub Check: claude-review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude finished @ymc9's task —— View job

---

PR Review: Vitest Update

Reviewing the Vitest dependency update from v3.2.4 to v4.0.14:

Todo List

• Examine package.json changes
• Review VS Code workspace configuration updates
• Check for potential breaking changes
• Assess test configuration impact
• Provide comprehensive feedback

Review Summary

This PR updates Vitest from v3.2.4 to v4.0.14 (a major version bump) and includes corresponding VS Code configuration updates.

✅ Positive Changes

1. Clean dependency update: The Vitest version bump in package.json is straightforward and follows semantic versioning.

2. VS Code extension alignment: The switch from kingwl.vscode-vitest-runner to vitest.explorer aligns with the official Vitest VS Code extension, which is the recommended approach.

3. Sensible configuration: The addition of vitest.maximumConfigs: 20 in VS Code settings is appropriate for a monorepo with multiple test configurations (I can see 10+ vitest.config.ts files across packages).

⚠️ Potential Concerns & Recommendations

1. Major Version Breaking Changes

Vitest v4.0 introduced several breaking changes that should be verified:

• Node.js requirement: Vitest v4 requires Node.js 20+
• Configuration changes: Some configuration options may have been deprecated or changed
• API changes: Test runner APIs may have breaking changes

Recommendation: Verify that all test suites still pass with the new version by running pnpm test across all packages.

2. Missing Changelog Documentation

The PR description is empty, making it difficult to understand:

• Which specific Vitest features/fixes motivated this update
• Whether any configuration adjustments were needed
• If any tests were updated to accommodate breaking changes

Recommendation: Add a brief description explaining the motivation and any changes made.

3. Dependency Lock File Impact

The pnpm-lock.yaml shows significant changes (101 additions, 234 deletions), which suggests substantial dependency tree changes.

Recommendation: Ensure CI passes and consider running tests locally to verify compatibility.

📋 Testing Checklist

Before merging, please verify:

• pnpm test passes for all packages
• pnpm build completes successfully
• VS Code Vitest extension works correctly in the workspace
• No test timeouts or configuration issues in monorepo packages

🔍 Code Quality Assessment

• No security concerns: This is a development dependency update with no production impact
• Good practices: Aligning with official Vitest tooling (VS Code extension)
• Appropriate scope: Changes are focused and don't introduce unnecessary modifications

Overall Assessment

This is a well-scoped dependency update that brings the project up to the latest Vitest version. The VS Code configuration updates are appropriate and improve developer experience. The main concern is ensuring compatibility with the major version bump.

Status: ✅ Approve with verification - Recommend testing thoroughly before merge due to major version change.

[Copilot]

Pull request overview

This PR updates Vitest from version 3.2.4 to 4.0.14, bringing the testing framework to its latest version. The update includes corresponding changes to all Vitest-related packages and dependencies, along with VSCode workspace configuration updates to support the new version.

• Updates Vitest core from 3.2.4 to 4.0.14
• Updates all @vitest/* scoped packages to 4.0.14
• Updates VSCode extension recommendation to the official Vitest extension
• Adds VSCode setting for handling multiple Vitest configurations

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File	Description
package.json	Updates vitest dependency specifier from ^3.2.4 to ^4.0.14
pnpm-lock.yaml	Updates all vitest-related packages, chai (5.2.0 → 6.2.1), and associated dependencies; removes obsolete packages and adds new ones (obug)
.vscode/settings.json	Adds vitest.maximumConfigs setting with value 20 for handling multiple test configurations
.vscode/extensions.json	Changes recommended extension from kingwl.vscode-vitest-runner to vitest.explorer (official Vitest extension)

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.

[claude]

Claude finished @ymc9's task —— View job

---

PR Review: Vitest Update

Reviewing the Vitest dependency update from v3.2.4 to v4.0.14:

Todo List

• Examine package.json changes
• Review VS Code workspace configuration updates
• Check for potential breaking changes
• Assess test configuration impact
• Provide comprehensive feedback

Review Summary

This PR updates Vitest from v3.2.4 to v4.0.14 (a major version bump) and includes corresponding VS Code configuration updates.

✅ Positive Changes

1. Clean dependency update: The Vitest version bump in package.json is straightforward and follows semantic versioning.

2. VS Code extension alignment: The switch from kingwl.vscode-vitest-runner to vitest.explorer aligns with the official Vitest VS Code extension, which is the recommended approach.

3. Sensible configuration: The addition of vitest.maximumConfigs: 20 in VS Code settings is appropriate for a monorepo with multiple test configurations (I can see 10+ vitest.config.ts files across packages).

⚠️ Potential Concerns & Recommendations

1. Major Version Breaking Changes

Vitest v4.0 introduced several breaking changes that should be verified:

• Node.js requirement: Vitest v4 requires Node.js 20+
• Configuration changes: Some configuration options may have been deprecated or changed
• API changes: Test runner APIs may have breaking changes

Recommendation: Verify that all test suites still pass with the new version by running pnpm test across all packages.

2. Missing Changelog Documentation

The PR description is empty, making it difficult to understand:

• Which specific Vitest features/fixes motivated this update
• Whether any configuration adjustments were needed
• If any tests were updated to accommodate breaking changes

Recommendation: Add a brief description explaining the motivation and any changes made.

3. Dependency Lock File Impact

The pnpm-lock.yaml shows significant changes (101 additions, 234 deletions), which suggests substantial dependency tree changes.

Recommendation: Ensure CI passes and consider running tests locally to verify compatibility.

📋 Testing Checklist

Before merging, please verify:

• pnpm test passes for all packages
• pnpm build completes successfully
• VS Code Vitest extension works correctly in the workspace
• No test timeouts or configuration issues in monorepo packages

🔍 Code Quality Assessment

• No security concerns: This is a development dependency update with no production impact
• Good practices: Aligning with official Vitest tooling (VS Code extension)
• Appropriate scope: Changes are focused and don't introduce unnecessary modifications

Overall Assessment

This is a well-scoped dependency update that brings the project up to the latest Vitest version. The VS Code configuration updates are appropriate and improve developer experience. The main concern is ensuring compatibility with the major version bump.

Status: ✅ Approve with verification - Recommend testing thoroughly before merge due to major version change.

---