[PR #512] [MERGED] chore: upgrade vitest to 4.1 #634

New issue

Closed

opened 2026-05-06 13:09:12 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 13:09:12 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/cloudflare/vinext/pull/512
Author: @james-elicx
Created: 3/12/2026
Status: ✅ Merged
Merged: 3/13/2026
Merged by: @james-elicx

Base: main ← Head: chore/upgrade-vitest-4.1

📝 Commits (2)

f2b7bb8 chore: upgrade vitest to 4.1
d932051 fix: clear console.warn spy state before asserting call counts

📊 Changes

3 files changed (+92 additions, -164 deletions)

View changed files

📝 package.json (+1 -1)
📝 pnpm-lock.yaml (+87 -163)
📝 tests/next-config.test.ts (+4 -0)

📄 Description

Summary

Upgrades vitest from ^3.2.1 to ^4.1.0
No config changes needed: the existing vitest.config.ts uses no deprecated options (no poolOptions, singleThread/singleFork, workspace, basic reporter, etc.)
Prerequisites satisfied: Node.js 24 and Vite 7 both meet the Vitest 4 requirements (Node >= 20, Vite >= 6)

Migration notes checked

Per the Vitest 4 migration guide:

V8 coverage remapping is now AST-based by default — no coverage config in use, no impact
coverage.all / coverage.extensions removed — not used
poolOptions / singleThread / singleFork removed — not used
basic reporter removed — not used
workspace → projects rename — not used
Test options-as-third-arg deprecated — not used in test files

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/cloudflare/vinext/pull/512 **Author:** [@james-elicx](https://github.com/james-elicx) **Created:** 3/12/2026 **Status:** ✅ Merged **Merged:** 3/13/2026 **Merged by:** [@james-elicx](https://github.com/james-elicx) **Base:** `main` ← **Head:** `chore/upgrade-vitest-4.1` --- ### 📝 Commits (2) - [`f2b7bb8`](https://github.com/cloudflare/vinext/commit/f2b7bb8338f318b3eae0ca3960e8454c4f01b731) chore: upgrade vitest to 4.1 - [`d932051`](https://github.com/cloudflare/vinext/commit/d932051945a199677cb0b4eefd870782981e26fd) fix: clear console.warn spy state before asserting call counts ### 📊 Changes **3 files changed** (+92 additions, -164 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) 📝 `pnpm-lock.yaml` (+87 -163) 📝 `tests/next-config.test.ts` (+4 -0) </details> ### 📄 Description ## Summary - Upgrades vitest from `^3.2.1` to `^4.1.0` - No config changes needed: the existing `vitest.config.ts` uses no deprecated options (no `poolOptions`, `singleThread`/`singleFork`, `workspace`, `basic` reporter, etc.) - Prerequisites satisfied: Node.js 24 and Vite 7 both meet the Vitest 4 requirements (Node >= 20, Vite >= 6) ## Migration notes checked Per the [Vitest 4 migration guide](https://vitest.dev/guide/migration#vitest-4): - V8 coverage remapping is now AST-based by default — no coverage config in use, no impact - `coverage.all` / `coverage.extensions` removed — not used - `poolOptions` / `singleThread` / `singleFork` removed — not used - `basic` reporter removed — not used - `workspace` → `projects` rename — not used - Test options-as-third-arg deprecated — not used in test files --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>