You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This major upgrade from Vite v6 to v7 introduces significant breaking changes that require developer action, including updates to the required Node.js version and default browser targets.
Key Breaking Changes:
Node.js Requirement: Support for Node.js 18 has been dropped. Vite v7 requires Node.js version 20.19+ or 22.12+. Your development and deployment environments must be updated.
Default Browser Target Changed: The default for build.target has been changed from 'modules' to 'baseline-widely-available'. This increases the minimum browser versions for the production build, potentially dropping support for older browsers.
Chrome: 87 → 107
Firefox: 78 → 104
Safari: 14.0 → 16.0
Legacy Sass API Removed: In accordance with Sass's own deprecation, support for the legacy Sass JavaScript API has been removed. Vite will now only use the modern API.
Vitest Compatibility: If you use Vitest for testing, you must upgrade to Vitest version 3.2 or newer.
Recommendation:
Before merging, verify that your CI/CD and local development environments meet the new Node.js version requirement. Review your project's browser support policy to ensure the new default targets are acceptable; otherwise, explicitly configure build.target in your vite.config.js. If you are using Sass, confirm you are not relying on the legacy API.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
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
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.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
client/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-ESBUILD-17750822
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.