chore(deps): update devdependency vite to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite (source)	^7.3.1 → ^8.0.3

---

Release Notes

vitejs/vite (vite)

v8.0.3

Compare Source

Features

• update rolldown to 1.0.0-rc.12 (#​22024) (84164ef)

Bug Fixes

• html: cache unfiltered CSS list to prevent missing styles across entries (#​22017) (5464190)
• module-runner: handle non-ascii characters in base64 sourcemaps (#​21985) (77c95bf)
• module-runner: skip re-import if the runner is closed (#​22020) (ee2c2cd)
• optimizer: scan is not resolving sub path import if used in a glob import (#​22018) (ddfe20d)
• ssr: ssrTransform incorrectly rewrites meta identifier inside import.meta when a binding named meta exists (#​22019) (cff5f0c)

Miscellaneous Chores

• deps: bump picomatch from 4.0.3 to 4.0.4 (#​22027) (7e56003)

Tests

• html: add tests for getCssFilesForChunk (#​22016) (43fbbf9)

v8.0.2

Compare Source

Features

• update rolldown to 1.0.0-rc.11 (#​21998) (ff91c31)

Bug Fixes

• deps: update all non-major dependencies (#​21988) (9b7d150)

Miscellaneous Chores

• deps: update dependency @​vitejs/devtools to ^0.1.5 (#​21992) (b2dd65b)

v8.0.1

Compare Source

Features

• update rolldown to 1.0.0-rc.10 (#​21932) (b3c067d)

Bug Fixes

• bundled-dev: properly disable inlineConst optimization (#​21865) (6d97142)
• css: lightningcss minify failed when build.target: 'es6' (#​21933) (5fcce46)
• deps: update all non-major dependencies (#​21878) (6dbbd7f)
• dev: always use ESM Oxc runtime (#​21829) (d323ed7)
• dev: handle concurrent restarts in _createServer (#​21810) (40bc729)
• handle + symbol in package subpath exports during dep optimization (#​21886) (86db93d)
• improve no-cors request block error (#​21902) (5ba688b)
• use precise regexes for transform filter to avoid backtracking (#​21800) (dbe41bd)
• worker: require(json) result should not be wrapped (#​21847) (0672fd2)
• worker: make worker output consistent with client and SSR (#​21871) (69454d7)

Miscellaneous Chores

• add changelog rearrange script (#​21835) (efef073)
• deps: bump required @vitejs/devtools version to 0.1+ (#​21925) (12932f5)
• deps: update rolldown-related dependencies (#​21787) (1af1d3a)
• rearrange 8.0 changelog (8e05b61)
• rearrange 8.0 changelog (#​21834) (86edeee)

v8.0.0

Compare Source

Features

• update rolldown to 1.0.0-rc.9 (#​21813) (f05be0e)
• warn when vite-tsconfig-paths plugin is detected (#​21781) (ada493e)

Bug Fixes

• deps: update all non-major dependencies (#​21786) (eaa4352)

---

Configuration

📅 Schedule: Branch creation - Between 06:00 AM and 09:59 AM, only on Monday ( * 6-9 * * 1 ) in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@6058

commit: a98dadf

[howwohmm]

Looking at this Vite v7 → v8 upgrade, here are key areas that need attention:

• New bundler integration: The lockfile shows rolldown@1.0.0-rc.11 appearing in the dependency tree, indicating Vite v8's new Rust-based bundler is being used. This could affect build performance and output, especially for the playgrounds. The team should test that playground builds still work correctly and watch for any bundle size or performance changes.

• CSS processing pipeline changes: The dependency resolution switched from lightningcss@1.32.0 to esbuild@0.27.3 in several chains, suggesting Vite v8 changed its CSS handling approach. Since Nuxt UI heavily relies on CSS processing for Tailwind and component styles, thoroughly test that all CSS compilation, especially in the playgrounds, works as expected.

• Plugin compatibility verification needed: Major Vite updates often introduce breaking changes in plugin APIs. While this only affects playground environments, verify that @vitejs/plugin-vue v6.0.5 and other Vite plugins in the dependency tree are fully compatible with Vite v8, particularly around Vue SFC processing and HMR functionality.

The lockfile changes look consistent and complete, but this major version bump warrants careful testing of the playground environments before merging.