Build plugin/config relocation

Vite optimizeDeps include exclude config no longer take effect option mapping changed Vite 8

Dependency prebundling excludes/include settings no longer take effect.

ViteJavaScript build toolingBuild plugin/config relocationvite8

Agent Quick Fix

Repair against the current Vite contract, then keep the change narrow and source-backed.

Product: Vite
Current-contract area: Vite 8 optimizeDeps option mapping changed
Likely root cause: Dependency prebundling excludes/include settings no longer take effect.
Repair direction: Verifier checks the current package identity/config format and a real transformed output. Check emitted assets and runtime behavior across the supported target.

Symptom

Dependency prebundling excludes/include settings no longer take effect.

Why This Happens

The old package/config name is syntactically valid, but current tool packaging and discovery rules live in external release documentation.

Common Wrong Fixes

  • Changing local code without checking the current external contract.
  • Retrying the same install, build, or API call with no version/source change.
  • Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

Vite optimizeDeps include exclude config no longer take effect option mapping changed Vite 8
site:vite.dev optimizeDeps include exclude Vite config dependency pre-bundling
https://vite.dev/config/dep-optimization-options
https://vite.dev/blog/announcing-vite8
https://vite.dev/guide/migration

Source Trail