chore(deps-dev): bump vite from 7.3.2 to 8.2.1 - #307
Merged
Conversation
Vite 8 replaces Rollup and esbuild with Rolldown and Oxc, and makes Lightning CSS the default CSS minifier. None of the three Vite projects needed a config migration: vitejs-ts and lit-ts have no vite.config file, and the SvelteKit one only registers the sveltekit() plugin. The SvelteKit toolchain is bumped along with it because @sveltejs/vite-plugin-svelte 6 peers on Vite 7 at most. Its version 7 requires svelte >= 5.46.4, and @sveltejs/kit 2.49 does not accept plugin-svelte 7, so both are bumped as well.
|
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.



Bump Vite from 7.3.2 to 8.2.1 in the three projects that use it:
vitejs-ts,lit-tsandsveltekit-ts.Vite 8 replaces Rollup and esbuild with Rolldown and Oxc, and makes Lightning CSS the default CSS minifier. Node requirements are unchanged (
^20.19 || >=22.12), so.nvmrcand the CI workflow stay as is.No config migration needed
Going through the v7 to v8 migration guide against this repository:
vitejs-tsandlit-tshave novite.config.*file at all (they pass--base ./on the CLI), so there is no config surface to migrate.sveltekit-ts/vite.config.tsonly registers thesveltekit()plugin: norollupOptions,esbuild,optimizeDeps,build.commonjsOptionsormanualChunksto rename.lit-tsuses TypeScript legacy decorators (experimentalDecorators), which Oxc supports, and does not use theaccessorkeyword (the one known broken combination).index.html,tsconfig.json, the READMEs or the dependabot configuration.SvelteKit toolchain bump
Required to get Vite 8 in
sveltekit-ts:@sveltejs/vite-plugin-svelte~6.2.4to~7.2.0: version 6 peers onvite ^6.3 || ^7at mostsvelte~5.46.1to~5.56.8: plugin-svelte 7 requiressvelte >= 5.46.4@sveltejs/kit~2.49.4to~2.70.2: 2.49 does not accept plugin-svelte 7svelte-check~4.3.5to~4.7.5The lockfile is regenerated for the affected subtree only (38 packages changed, all in the vite/svelte/lightningcss orbit). Parcel, Rspack, Rollup and Farm dependencies are untouched.
Verification
Locally on Node 22.20:
npm cithennpm run build --workspaces: all 8 projects build, including the 5 non-Vite onesnpm run check -w projects/sveltekit-ts: 503 files, 0 errors, 0 warningsvite devsmoke test onvitejs-ts: server ready,/and/src/main.tsboth return 200Note
Vite builds now emit a new non-fatal warning: Rolldown flags a direct
eval()call in@maxgraph/core/lib/esm/internal/utils.js:23. It does not fail the build, but it is worth addressing in the maxGraph core repository.