Build plugin/config relocation
Vite 7 Sass legacy API option no longer works css preprocessorOptions sass api legacy
SCSS compilation fails or changes warnings after upgrade.
Agent Quick Fix
Repair against the current Vite contract, then keep the change narrow and source-backed.
Product: Vite
Current-contract area: Vite 7 Sass legacy API option no longer works
Likely root cause: SCSS compilation fails or changes warnings after upgrade.
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
SCSS compilation fails or changes warnings after upgrade.
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 7 Sass legacy API option no longer works css preprocessorOptions sass api legacy
Vite 7 Sass legacy API option legacy no longer works
site:vite.dev sass api legacy vite css preprocessorOptions
Vite 7 migration guide Sass legacy API removed
https://vite.dev/guide/migration.html
https://v7.vite.dev/guide/migration.html