chore(deps-dev): bump vitest from 3.2.4 to 4.0.2 #248
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 to 4.0.2. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.2/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.0.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
📝 WalkthroughSummary by CodeRabbit
Note: This release contains no user-facing changes. WalkthroughA development dependency version update in Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes This is a straightforward dependency version update affecting only one field in the manifest file. The change is mechanical and non-breaking to the codebase structure or public exports, requiring minimal verification beyond confirming the version bump is intentional and compatible with the project's test infrastructure. Pre-merge checks❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
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
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json(1 hunks)
| "typescript": "^5.9.3", | ||
| "vite": "^6.3.5", | ||
| "vitest": "^3.2.4" | ||
| "vitest": "^4.0.2" |
There was a problem hiding this comment.
🧩 Analysis chain
Verify test suite compatibility with vitest v4.0.2.
This is a major version bump with breaking changes (reporter changes, spy rewrite, pool rewrite). Although Vite 6.x is compatible, the breaking changes may require adjustments to your test setup or code.
Please verify that the test suite passes with vitest 4.0.2 by running:
If tests fail, check the vitest migration guide for v4 breaking changes, particularly around:
- Custom reporters (if used)
- Spy/mock APIs
- Pool configuration
🏁 Script executed:
#!/bin/bash
# Run the test suite to confirm compatibility with vitest 4.0.2
npm testLength of output: 124
🏁 Script executed:
#!/bin/bash
# Find test files in the codebase
echo "=== Searching for test files ==="
fd -e '\.test\.(ts|js|tsx|jsx)$' -o -e '\.spec\.(ts|js|tsx|jsx)$' -o -name '__tests__' -type dLength of output: 149
🏁 Script executed:
#!/bin/bash
# Find vitest and vite config files
echo "=== Searching for vitest/vite config files ==="
fd -e 'vitest.config.*' -o -e 'vite.config.*'Length of output: 163
🏁 Script executed:
#!/bin/bash
# Search for spy, mock, vi.* usage patterns in test files
echo "=== Searching for spy/mock patterns ==="
rg -n '\b(spy|mock|vi\.)' --type=ts --type=js -C2 | head -100Length of output: 39
🏁 Script executed:
#!/bin/bash
# Check for custom reporter configuration
echo "=== Searching for reporter configuration ==="
rg -n -i 'reporter' package.json vitest.config.* vite.config.* 2>/dev/null || trueLength of output: 44
🏁 Script executed:
#!/bin/bash
# Display package.json devDependencies to understand testing setup
echo "=== Relevant dependencies from package.json ==="
rg -A 20 '"devDependencies"' package.jsonLength of output: 436
🏁 Script executed:
#!/bin/bash
# Broader search for test files without fd extension issues
echo "=== Searching for test files with rg ==="
rg -l '\.(test|spec)\.(ts|js|tsx|jsx)$' --type-list | head -20Length of output: 430
🏁 Script executed:
#!/bin/bash
# Check for any test-related files in src directory
echo "=== Looking in src directory ==="
find src -type f \( -name '*.test.*' -o -name '*.spec.*' \) 2>/dev/null | head -20Length of output: 66
🏁 Script executed:
#!/bin/bash
# Look for test directories
echo "=== Searching for test directories ==="
find . -maxdepth 3 -type d \( -name '__tests__' -o -name 'tests' -o -name 'test' \) 2>/dev/nullLength of output: 38
🏁 Script executed:
#!/bin/bash
# Check package-lock or yarn.lock for @lokalise/package-vite-config details
echo "=== Checking shared config dependency details ==="
rg -A 5 '@lokalise/package-vite-config' --type=json | head -30Length of output: 1303
🏁 Script executed:
#!/bin/bash
# Check if there's a src directory and its structure
echo "=== Source directory structure ==="
ls -la src/ 2>/dev/null || echo "No src directory found"Length of output: 362
🏁 Script executed:
#!/bin/bash
# Display the test file to check for vitest API usage
echo "=== Test file content ==="
cat src/frontegg-oauth-client.test.tsLength of output: 10615
🏁 Script executed:
#!/bin/bash
# Check the actual vitest version in @lokalise/package-vite-config dependencies
echo "=== Checking shared config's vitest dependency ==="
rg -A 20 '"@lokalise/package-vite-config": {' package-lock.json | grep -A 20 'node_modules/@lokalise/package-vite-config'Length of output: 182
🏁 Script executed:
#!/bin/bash
# Search for specific vitest 4.0.0 breaking changes in test file
echo "=== Searching for potential breaking changes: spies, deprecated patterns ==="
rg '\b(vi\.spyOn|spyOn|vi\.mock|mock\(|vi\.resetAllMocks|resetAllMocks|vi\.clearAllMocks)\b' src/frontegg-oauth-client.test.ts -nLength of output: 76
🏁 Script executed:
#!/bin/bash
# Look up vitest 4.0.2 release notes for actual breaking changes
echo "=== Searching for breaking change patterns in test file ==="
cat src/frontegg-oauth-client.test.ts | grep -i "deprecated\|breaking\|changed" || echo "No deprecated patterns found"Length of output: 88
🏁 Script executed:
#!/bin/bash
# Check what @lokalise/package-vite-config exports
echo "=== Checking if package-lock has details on shared config content ==="
rg -A 50 'node_modules/@lokalise/package-vite-config' package-lock.json | head -60Length of output: 2438
🌐 Web query:
@lokalise/package-vite-config vitest 4 support
💡 Result:
I couldn't find any explicit mention that @lokalise/package-vite-config adds or targets Vitest 4 support in its public package info (latest published version 4.0.0). The package README on npm doesn't call out Vitest 4 compatibility. [1]
Note: Vitest 4 changed the way config types are referenced (migrating from "vitest" to "vitest/config"), so projects or shared configs must update accordingly — see Vitest's config docs. [2]
If you want, I can:
- open the package source in the shared-ts-libs repo and check its vite/test config files for Vitest-specific code, or
- open an issue/PR template text you can use to ask the maintainers.
Sources:
[1] @lokalise/package-vite-config package info (npm).
[2] Vitest — Configuring Vitest (Vitest docs).
🏁 Script executed:
#!/bin/bash
# Search npm for all versions of @lokalise/package-vite-config
echo "=== Checking npm for available versions ==="
npm view @lokalise/package-vite-config versions --json 2>/dev/null | tail -50Length of output: 145
🏁 Script executed:
#!/bin/bash
# Check latest version of @lokalise/package-vite-config
echo "=== Latest version info ==="
npm view @lokalise/package-vite-config@latest 2>/dev/null | grep -A 5 "version\|peerDependencies"Length of output: 265
Vitest 4.0.2 conflicts with shared config peerDependency.
The shared config dependency @lokalise/[email protected] explicitly requires vitest ^3.0.7 (which excludes v4.x). Updating to vitest 4.0.2 violates this peerDependency constraint and will cause:
- Unmet peerDependency warnings
- Potential test failures or unexpected behavior
Resolution: Either upgrade to a newer version of @lokalise/package-vite-config that supports vitest 4.x, or revert vitest to v3.x. Currently, the latest version available is 4.0.0 with no v5+ release supporting vitest 4. Contact the maintainers of @lokalise/package-vite-config to confirm vitest 4 support before merging.
🤖 Prompt for AI Agents
In package.json around line 38, vitest is set to "4.0.2" which conflicts with
the peerDependency required by @lokalise/[email protected] (which
expects vitest ^3.0.7); fix by either (A) reverting vitest to a 3.x range that
satisfies the peer dep (e.g., "^3.0.7") and run npm/yarn install to update
lockfile, or (B) upgrade @lokalise/package-vite-config to a version that
explicitly supports vitest 4.x (confirm with maintainers) and then update
package.json and reinstall; choose one path and ensure
package-lock.json/yarn.lock is updated and CI tests pass before merging.
|
Superseded by #251. |
Bumps vitest from 3.2.4 to 4.0.2.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
07bc56achore: release v4.0.22eedbcefix(spy): reset spies if bothrestoreMocksandmockResetis set in the co...26ce88dfix(pool): assign envs before running tests to keep in sync with process.env ...4a28faachore: release v4.0.13fae73efix(pool): don't teardown the communication channel too soon if something is ...8100063fix: move thegetBuiltinscheck (#8765)da7ce17chore: release v4.0.08e15bc8perf: create only one fetcher per project (#8762)9f0ecccfix:baseoption doesn't crash vitest (#8760)d3ef4f2perf(pool): resolve all environments first (#8759)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)