# How do I resolve a 'module not found' error?

**Author:** Sam Ko

---

The 'module not found' error is a syntax error that appears when the static [**import**](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import) statement cannot find the file at the declared path. This common syntax error is caused by letter-casing inconsistencies that are present in your filename(s) between your repository and local machine, or both.

## Why this Happens

One possible cause for this issue is the fact that some filesystems are case-insensitive, however Vercel deployments use a case-sensitive filesystem. Because of this, it is possible that when you change the letter-casing in filenames on your local machine, Git will only pick up changes in your respective static [**import**](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import) statements. This would mean that your repository is now syntactically incorrect, resulting in a build error when deploying the repository on the Vercel platform.

## How to Resolve

The [build logs](https://vercel.com/knowledge/where-are-vercel-logs) will indirectly point to the file that is the causing the issue. Make sure that your file's letter-casing correctly matches with its respective static [**imports**](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import). Also make sure that your letter-casing in your filenames and imports are identical between your repository and local machine. If you are using `git`, make sure `git config core.ignorecase false` is set in your environment.

---

[View full KB sitemap](/kb/sitemap.md)