Repository navigation
Bump vite and vitest - #5
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) to 8.3.0 and updates ancestor dependency [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together. Updates `vite` from 5.4.21 to 8.3.0 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/create-vite@8.3.0/packages/vite) Updates `vitest` from 2.1.9 to 5.0.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/vitest) --- updated-dependencies: - dependency-name: vite dependency-version: 8.3.0 dependency-type: indirect - dependency-name: vitest dependency-version: 5.0.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1bb8a74. Configure here.
| "tsx": "^4.19.0", | ||
| "typescript": "^5.6.0", | ||
| "vitest": "^2.1.0" | ||
| "vitest": "^5.0.0" |
There was a problem hiding this comment.
Vitest 5 breaks Node 20 tests
High Severity
vitest 5 requires Node ^22.12.0 || ^24.0.0 || >=26.0.0, but engines still allows >=20.10.0 and CI runs Node 20. npm test will fail on the project's supported and CI Node version because Vitest 5 no longer supports Node 20.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 1bb8a74. Configure here.
Author
|
Looks like these dependencies are up-to-date now, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Bumps vite to 8.3.0 and updates ancestor dependency vitest. These dependencies need to be updated together.
Updates
vitefrom 5.4.21 to 8.3.0Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
95e8923release: v7.3.19d39d37feat: addignoreOutdatedRequestsoption tooptimizeDeps(#21364)acf7e05release: v7.3.0cff26ecfeat(deps): update esbuild from ^0.25.0 to ^0.27.0 (#21183)317b3b2release: v7.2.7721f163fix: plugin shortcut support (#21211)bda5dbbrelease: v7.2.63aa7527release: v7.2.572e398afix(deps): update all non-major dependencies (#21175)3765f7bfix: shortcuts not rebound after server restart (#21166)Updates
vitestfrom 2.1.9 to 5.0.0Release notes
Sourced from vitest's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)d46a747fix: treat test.describe as a suite during static collection (#11128)584cf30fix: add a warning if inline project has duplicate plugins due to unexpected ...f08ce4bfix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)51e9494feat!: parse files statically in vitest list by default (#11088)2122ffdfix: propagate --maxWorkers to projects (#11102)dc10f5ffix(browser): report the action error when a task times out (#11101)d4fe198feat: promote clearCache out of experimental (#11086)Maintainer changes
This version was pushed to npm by 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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.
Note
Medium Risk
Major Vitest/Vite upgrades can change test runtime behavior and Node version requirements without touching product code; CI must use Node 22.12+ for Vitest 5.
Overview
Bumps the dev test stack by raising
vitestfrom^2.1.0to^5.0.0inpackage.jsonand refreshingpackage-lock.json. No application or test source files are edited;npm teststill runsvitest rununchanged.The lockfile refresh pulls in Vitest 5’s toolchain, including Vite 8.3.0 (Rolldown-based bundling instead of Rollup 4), Chai 6, and updated
@vitest/*packages. That aligns with Vitest 5’s requirement for a newer Vite peer and stricter Node support (Vitest 5 declares Node^22.12.0, whilepackage.jsonstill advertises>=20.10.0).Reviewers should run the test suite on Node 22.12+ and watch for Vitest 5 behavior changes (e.g. default mock clearing, assertion/reporting tweaks) even though existing tests only use standard
describe/it/expectAPIs.Reviewed by Cursor Bugbot for commit 1bb8a74. Bugbot is set up for automated code reviews on this repo. Configure here.