React build times out although the required file exists (Error: ENOENT: no such file or directory, open '/opt/build/repo/src/index.js')

[Divide-by-0]

Our build is exceeding the maximum allowed runtime and I’m not sure 1) why it’s taking so long, it’s our first deploy of our react site, and 2) if the error at the end of the log is the reason for why it’s exceeding runtime, or if it’s an error as a RESULT of timing out.

copysmith.netlify.app is our site (not sure why it shows a login with figma), and then copysmith.ai is our site.

[Divide-by-0]

Also, the file mentioned exists, and I’ll add the code in the next comment.

Locally, everything works.

[Divide-by-0]

This is the index.js file. Is it not finding a file in this file’s imports?

[perry]

hi there! our default runtime is 15 minutes, but unless your site is large/complex i would expect it to complete quite a bit before that.

One thing i am seeing is that you are doing a lot of linting with warnings as part of your deploy step - ideally you don’t want to do that and instead only deploy the optimized code. The linting process might be slowing down your build, but again, i wouldn’t expect it to really push you to the 15 minute mark.

i’m going to guess that there is something lingering in the background that never terminates - maybe one of these posts are helpful in figuring it out what it might be:

[Support Guide] How can I optimize my Netlify build time?

Last reviewed by Netlify Support - August, 2023 If you are interested in learning more about how our bots approach building sites, these three articles are a great place to start: How our Build Bots build sites The last major upgrade to our build environment and perhaps least-loved but most useful, how to debug your builds So you might think, it’s great that Netlify builds every commit from my repos…but isn’t that a bit wasteful? The answer is, it depends, but we can at least give you…

[Support Guide] How long should Netlify builds take?

Last checked in April 2022 The only universal answer to this is: it varies. More detail would probably be helpful, right? Below we explain which factors affect the lengths of builds on Netlify One key factor is the site itself. Larger sites will take longer to build than smaller ones, and things like images and video can impact this (if those assets need to be downloaded or processed during build). Another factor is the static site generator (SSG) being used (if any). The perfo…

[Support Guide] Understanding & unregistering service workers

Last reviewed by Netlify Support - August, 2023 A service worker is a script that your browser runs in the background to accomplish a variety of tasks. Browsers cache service workers for 24 hours by default, and don’t update them when you reload your page. Therefore, you may have a service worker on your site which could prevent you from seeing the latest and greatest changes that you’ve made. If you suspect a service worker is causing this issue, I recommend disabling/removing the service wor…

[Support Guide] Hung or stuck, but seemingly successful build

Last review by Netlify Support Team on December 2022 When a deploy gets stuck with no apparent build failure, it typically means that while our robots did start building your code, it didn’t wrap up some process within the 15 minute time limit our build environment requires. Why can this happen? More on that in a sec, but first I want to mention that our build environment requires all processes, not just the main ones started by your build to complete. If even one thing gets stuck, the proces…