feat: migrate console to Vite v8#2211
Open
shikanime wants to merge 2 commits into
Open
Conversation
shikanime
force-pushed
the
feat/migrate-to-vite-v8
branch
from
0d18e07 to
5f7c50d
Compare
Contributor
|
🤖 Hey ! The security scan report for the current pull request is available here. |
1 similar comment
Contributor
|
🤖 Hey ! The security scan report for the current pull request is available here. |
All 7 plugins had outdated vite 7.3.2 and vitest 4.1.5 in devDependencies. This caused CI unit tests to fail when resolving plugin imports because Vite 7 couldn't handle the Vite 8 workspace dependencies correctly.
shikanime
force-pushed
the
feat/migrate-to-vite-v8
branch
from
5f7c50d to
2f327bb
Compare
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
1 participant
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.
Quel est le comportement actuel ?
Le projet utilise Vite 7.3.2 avec esbuild/Rollup comme bundlers.
Quel est le nouveau comportement ?
Migration vers Vite 8 qui remplace esbuild et Rollup par Rolldown (bundler Rust unifié) et Oxc pour les transformations JS.
Changements principaux
cssTarget: 'chrome111'etcss.lightningcss.errorRecovery: true(requis par LightningCSS dans Vite 8)Vérification
pnpm build— build client réussi avec Rolldownpnpm test— 57 tests client + 189 tests server-nestjs passentCette PR introduit-elle un breaking change ?
Oui, Vite 8 est un changement de majeur :
cssTargetexplicite)vite-nodeest supprimé (déprécié au profit de l'Environment Module Runner intégré)