Framework semantic default
Vite assetFileNames callback receives changed metadata names originalFileNames asset chunk naming Vite 8
A deployment script cannot find expected output files after build.
Agent Quick Fix
Repair against the current Vite contract, then keep the change narrow and source-backed.
Product: Vite
Current-contract area: Vite 8 asset/chunk naming callback receives changed metadata
Likely root cause: A deployment script cannot find expected output files after build.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Check emitted assets and runtime behavior across the supported target.Symptom
A deployment script cannot find expected output files after build.
Why This Happens
Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.
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 assetFileNames callback receives changed metadata names originalFileNames asset chunk naming Vite 8
site:vite.dev assetFileNames originalFileNames names Vite
Rollup output.assetFileNames PreRenderedAsset originalFileNames names
https://rollupjs.org/configuration-options/
'output.assetFileNames' in https://rollupjs.org/configuration-options/