Deploy issues with pathways even though they are correct

Support
, ,
1

I’m trying to deploy my portfolio (harrisste.netlify.app) and I’m consistently getting failure messages regarding the pathways to my components. I have double-checked my pathways for all files - even retyped them to ensure I didn’t miss something small (I am sure I’m still overlooking something). I’ve included the error and a screenshot of the error, I tried to add a screenshot of my code, however, I was unable to. If someone can help I will be eternally grateful. I can include more information if needed. TIA!

image
image1230×612 84 KB

2

@HarrisSte It’s not really possible to provide you any detailed guidance from only the error, I’d need to also see the file/folder structure of your project.

You should check that this file exists:

/src/components/Welcome/Welcome.jsx

Paying particular attention to the capital letters, since Netlify’s build system is case-sensitive.

3

Luckily, I managed to figure my issue out. After double-checking everything (files, paths, etc.), I found the deployment wasn’t happy with the uppercase ‘Welcome’ rather than the lowercase. Despite the file existing, the pathway was named and capitalized correctly, but it only works when it’s lowercase. I had to rename some of my other files for my application. I currently have a smattering of upper/lower case file names, but that is the only way Netlify would allow me to deploy successfully. Is there a reason, that you know if, why this would happen?

I hope that made some sense…

4

Netlify’s build system is Ubuntu based.

5

Hi, @HarrisSte. Most filesystems on Linux are case-sensitive and the build system at Netlify is using Ubuntu Linux. MacOS and Windows both, generally speaking, treat file paths as case-insensitive.

The only solution for this is to perfectly match the upper-case and lower-case letters in your code if you want the code to run correctly on Linux.

1 Like
6

Thanks for your response! Interestingly enough, when I received the error and checked my files, everything was typed correctly – casing and all. That is where my confusion initially stemmed from. I successfully deployed only when I switched the file name to have the opposite casing – even though I never changed the file name after it’s initial creation.

Thanks again for your help!