JS bundle failure

[linards]

Hi, Im getting errors when trying to deploy a gatsbyjs site.

2:58:25 PM: Can't resolve '../components/Layout' in '/opt/build/repo/src/pages'`Preformatted text`
2:58:25 PM: error Generating JavaScript bundles failed
2:58:25 PM: Can't resolve '../components/Layout' in '/opt/build/repo/src/pages'
2:58:25 PM: error Generating JavaScript bundles failed
2:58:25 PM: Can't resolve '../components/Seo' in '/opt/build/repo/src/pages'
2:58:25 PM: error Generating JavaScript bundles failed
2:58:25 PM: Can't resolve '../components/Seo' in '/opt/build/repo/src/pages'

I’ve checked my local repo and github, the naming convention on my components match locally.

Please let me kow what im doing wrong.

Thank you.

[perry]

can you verify that it builds locally?

if yes, but fails when you try and deploy on Netlify, this might be the culprit:

[Support Guide] Netlify app builds locally but fails on deploy (case sensitivity)

Last Reviewed By Netlify Support Staff: December 2022 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! 1. Errors you might see Case sens…

[linards]

Thanks @perry

It is finelocally:

[linards]

[DavidWells]

Sometimes git mixes up uppercase and lowercase file names. This can lead to errors like this.

Try to rename components/Seo to components/SeoComponent, update the imports, try the build locally to verify and then commit to git. Do the same with /components/Layout. This should “flush out” the uppercase/lowercase issue if it is the root cause here.

After this, you should be able to rename your components to whatever you wish

In the image https://global.discourse-cdn.com/netlify/original/2X/9/9ab7e903c1d4900a0b87ca62e34972667c63fa01.png I see the lowercase imports components/seo vs components/Seo which makes me think this IS the issue

[linards]

Thanks @DavidWells and @perry I’ve changed the github config file globally to ignore CaseSensitive, it worked. Thank you

[technoken35]

If you don’t mind, can you share how you changed your git config to ignore case sensitivity?

[luke]

Hi, @technoken35, we don’t have more information about how @linards resolved this. Our support team’s recommendation is to correct the site code to match the case of the actual files.

Maybe @linards will share his solution but our solution will also work if you want to try it.

If there are any questions about how to do this, please let us know.