# Vite assetFileNames callback receives changed metadata names originalFileNames asset chunk naming Vite 8

Status: search-observed
Product: Vite
Last verified: 2026-06-25
Canonical HTML: https://gitdocs.org/fix/vite-assetfilenames-callback-receives-changed-metadata-names-originalfilenames-asset-chunk-namin
Machine JSON: https://gitdocs.org/api/fixes/vite-assetfilenames-callback-receives-changed-metadata-names-originalfilenames-asset-chunk-namin.json

## Exact Symptom

See the observed Codex queries below.

## Diagnosis

Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.

## Fix

```
Verifier checks behavior across multiple requests/build modes, not merely compilation. Check emitted assets and runtime behavior across the supported target.
```

## Avoid

- 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.

## Observed Codex Queries

- 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/

## Sources

- Vite migration from v7 to v8: https://vite.dev/guide/migration
- Official reference opened by Codex: https://rollupjs.org/configuration-options/