Vite
Vite build failed because of case-sensitive file paths
ENOENT: no such file or directory / Module not found
A Vite project that works on a case-insensitive file system can fail in CI or Linux builds when import casing does not match the real file names.
Observed message
ENOENT: no such file or directory / Module not found
Why it happens
- An import path uses different letter casing than the actual file name.
- The project was developed on Windows or macOS and then built on a case-sensitive Linux environment.
- A rename changed file casing without updating all imports consistently.
How to fix it
- Update imports so every file path matches the exact on-disk casing.
- Check recent renames and verify that Git committed casing-only file name changes correctly.
- Run the build in a case-sensitive environment during development or CI to catch these mismatches earlier.
