Are you struggling to understand why your project runs locally but errors out with missing files or logs that point toward issues with case when you try and build on Netlify? You are not alone. Often, case (as in: UPPERCASE or lowercase letters in filenames or paths) can cause problems. Here is a guide to understanding how case sensitivity issues present themselves, why they arise, and how you can fix them!
Case sensitivity issues can be frustrating to debug because sometimes you’ll receive error messages letting you know that files could not be found when they are clearly present during the build process. See this post for a great example:
Sometimes you might just have a failing build without any useful error messaging as it depends on which file has the issue.
If you work on Windows or OSX (mac), you are working on a case-insensitive system. The file system used in Netlify builds is case sensitive, while your local environment is not. Unfortunately, the error messages that result may not clearly indicate this!
Meaning: if your code includes a file or reference to a file like
jQuery/jquery.js — the Netlify build may fail due to the mixed case filename. This issue can be present with ANY file that is an important part of your project, including, but not limited to:
- entry-point application files like App.js or Main.js (not the same as app.js or main.js)
- partials, modules, imports, templates
- dependencies, packages
- font files
- image, css and json files
- netlify.toml, _redirects, package.json, Gemfile or any other config or settings files
This issue also happens regardless of where the case sensitivity occurs. To be really clear, during the build step:
somefile.js != someFile.js != SomeFile.js != SOMEFILE.js != sOmEfIlE.js
We strongly recommend that you pay very close attention to how you use case from the very beginning in your project, and standardize how you use case throughout so you don’t have problems during the build step on Netlify.
If you haven’t committed your files to version control (we are assuming you are using Git) then it is sufficient to simply rename the file(s) in question and the problem should fix itself.
That said, most people realize they are having a case issue when they try and build on Netlify, as the problem doesn’t occur locally. This almost always means that the file(s) have been committed to Git and pushed to a provider such as GitHub. Simply renaming the file and re-committing and pushing it does not generally work because Git’s default setting is to ignore case, and so those changes aren’t always registered.
This thread on Stack Overflow has lots of useful approaches on how to deal with this. We have also found that the following steps will do the trick:
- deleting the file
- committing and pushing to GitHub
- re-creating the file
- adding, committing, pushing to GitHub
As soon as the case issue is resolved, you should see any problems related to this vanish and enjoy smooth, problem free builds on our platform
If you are still having issues after fixing the case related issues, this Support Guide contains many other troubleshooting steps for common concerns! Good luck & please comment below if you have additional thoughts!