build(deps-dev): Bump vite from 7.0.6 to 8.1.4#123
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.0.6 to 8.1.4. - [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/v8.1.4/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.1.4 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
| "typescript": "^5.8.3", | ||
| "typescript-eslint": "^8.38.0", | ||
| "vite": "^7.0.6", | ||
| "vite": "^8.1.4", |
There was a problem hiding this comment.
🟡 Test framework is incompatible with the upgraded build tool version, causing dual-version resolution
The build tool is upgraded to a version outside the test framework's supported range ("vite": "^8.1.4" at package.json:56), so tests and builds use different internal engine versions (7.x vs 8.x), risking configuration drift.
Impact: The same config file may be interpreted differently during builds versus tests, potentially causing silent behavioral differences or future breakage when vitest cannot resolve its nested dependency.
Version constraint mismatch between vitest and vite
Vitest 3.2.4 declares a dependency on vite: ^5.0.0 || ^6.0.0 || ^7.0.0-0 (verified in the lockfile). The ^7.0.0-0 range means >=7.0.0-0 <8.0.0, so vite 8.x is explicitly outside the supported range.
npm resolved this by installing a nested node_modules/vitest/node_modules/vite at version 7.3.6 and node_modules/vite-node/node_modules/vite at version 7.3.6. This means:
vite builduses vite 8.1.4vitestuses its own nested vite 7.3.6
The vite.config.ts is read by both tools but processed by different vite versions. Any vite 8 config changes that are incompatible with vite 7 (or vice versa) would cause one context to work and the other to fail. The correct fix is to either upgrade vitest to a version that supports vite 8, or keep vite at ^7.x until vitest adds vite 8 support.
Prompt for agents
The PR upgrades vite to ^8.1.4 but vitest 3.2.4 only supports vite ^5.0.0 || ^6.0.0 || ^7.0.0-0. npm works around this by installing a nested vite 7.3.6 for vitest, but this means builds and tests use different vite versions processing the same vite.config.ts. Either upgrade vitest to a version that officially supports vite 8 (if one exists), or keep vite at ^7.x until vitest adds vite 8 support. Check the vitest changelog/releases for a version compatible with vite 8.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps vite from 7.0.6 to 8.1.4.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
a477454release: v8.1.4ab5dafafeat(legacy): prefer oxc as minifier (fix #21973) (#22468)173a1b6fix(ssr): align named export function call stacktrace column with Node (#22829)575c32cfix(build): add workaround for building on stackblitz (#22840)72a5e21fix(optimizer): avoid optimizer run for transform request before init (#22852)a9539d6chore(deps): update dependency postcss-modules to v9 (#22867)70435b2docs: fix incorrect@defaultforserver.cors(#22859)2c4a217build: remove the custom onLog function (#22878)c581b55build: replace deprecatedonwarnwithonLog(#22741)ea22fb3refactor: eliminate ineffectiveDynamicImport warn (#22876)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vite 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)