That’s a lot of information mentioned there. There’s a missing file according to those lines. Kindly check the path or as @AaronP asked, share the repository.
@hrishikesh that’s just part of the “Can’t resolve” list, there’s more of the same actually. But the weird thing on my local machine I’m not getting any errors. Everything works fine.
I will see if I can make the repo public. FYI @AaronP
Are you sure? I just downloaded your repo, deleted package-lock.json, ran npm install and then, npm run build, I get the following:
> ddvdrivertraining@1.0.0 build C:\Users\Hrishikesh\Desktop\DDVDriverTraining-master
> gulp; hugo --gc --minify
[16:29:29] Using gulpfile ~\Desktop\DDVDriverTraining-master\gulpfile.js
[16:29:29] Task never defined: ;
[16:29:29] To list available tasks, try running: gulp --tasks
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ddvdrivertraining@1.0.0 build: `gulp; hugo --gc --minify`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ddvdrivertraining@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Hrishikesh\AppData\Roaming\npm-cache\_logs\2020-10-24T10_59_29_976Z-debug.log
@hrishikesh I forgot to mention, you should use the branch react.
This will be merged in master as soon as everything works fine, and in that branch I also switched from npm to yarn (which also means there’s no package-lock.json).
The problem was incorrect case for components. It works on Windows and macOS (that’s why it build successfully on my Windows laptop and you might be using either of the two), but, Netlify uses Ubuntu which is Linux based and Linux can’t work with the mixed cases. So, all your components are in the folders which start with a small case, while the pages start with a capital case. While importing the components, you need to maintain the case, but, instead, you were importing all the components with the starting letter capital.
I did read about that, and I double checked afterwards. But on my machine (macOS) the folders do have a capital letter (I created them like this). Does GitHub maybe change them to lowercase when they don’t have an extension or something like that?
I don’t think so, because the folders in your page folder are still all capital. But, if you want to try, this page: [v2] Build breaking on Netlify · Issue #8205 · gatsbyjs/gatsby · GitHub suggests you can do something like git config core.ignorecase false. I’m not sure how and where to use it though.