React App, Netlify deploy from GitHub not deploying

[bwkarr77]

I am attempting to deploy an app from GitHub on Netlify. I created the app using React, Three.js, and semantic-ui. When I run it on my local server it runs fine, but when I try to run the deployment on Netlify it attempts to deploy for 15 minutes and then times with the following error:

My Netlify page is at: Netlify App
My GitHub Repo is at: GitHub - bwkarr77/game-of-life: Game Of Life - CS Build Week 1

Any ideas what I need to change in order to get my app to deploy?

Deploy log is below:
8:47:07 PM: Build ready to start
8:47:09 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
8:47:09 PM: build-image tag: v3.4.1
8:47:09 PM: buildbot version: fcbc7a79f7372e5995cf02954ef19fc48d20c871
8:47:09 PM: Fetching cached dependencies
8:47:10 PM: Failed to fetch cache, continuing with build
8:47:10 PM: Starting to prepare the repo for build
8:47:10 PM: No cached dependencies found. Cloning fresh repo
8:47:10 PM: git clone GitHub - bwkarr77/game-of-life: Game Of Life - CS Build Week 1
8:47:11 PM: Preparing Git Reference pull/8/head
8:47:12 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘build’ versus ‘build/’ in the Netlify UI
8:47:13 PM: Starting build script
8:47:13 PM: Installing dependencies
8:47:13 PM: Python version set to 2.7
8:47:14 PM: v12.18.0 is already installed.
8:47:14 PM: Now using node v12.18.0 (npm v6.14.4)
8:47:15 PM: Started restoring cached build plugins
8:47:15 PM: Finished restoring cached build plugins
8:47:15 PM: Attempting ruby version 2.7.1, read from environment
8:47:16 PM: Using ruby version 2.7.1
8:47:16 PM: Using PHP version 5.6
8:47:16 PM: 5.2 is already installed.
8:47:16 PM: Using Swift version 5.2
8:47:16 PM: Started restoring cached node modules
8:47:16 PM: Finished restoring cached node modules
8:47:17 PM: Installing NPM modules using NPM version 6.14.4
8:47:59 PM: > node-sass@4.14.1 install /opt/build/repo/node_modules/node-sass
8:47:59 PM: > node scripts/install.js
8:48:00 PM: Downloading binary from https://github.com/sass/node-sass/releases/download/v4.14.1/linux-x64-72_binding.node
8:48:00 PM: Download complete
8:48:00 PM: Binary saved to /opt/build/repo/node_modules/node-sass/vendor/linux-x64-72/binding.node
8:48:01 PM: Caching binary to /opt/buildhome/.npm/node-sass/4.14.1/linux-x64-72_binding.node
8:48:01 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/babel-runtime/node_modules/core-js
8:48:01 PM: > node -e “try{require(‘./postinstall’)}catch(e){}”
8:48:01 PM: > core-js@3.6.5 postinstall /opt/build/repo/node_modules/core-js
8:48:01 PM: > node -e “try{require(‘./postinstall’)}catch(e){}”
8:48:01 PM: > core-js-pure@3.6.5 postinstall /opt/build/repo/node_modules/core-js-pure
8:48:01 PM: > node -e “try{require(‘./postinstall’)}catch(e){}”
8:48:02 PM: > node-sass@4.14.1 postinstall /opt/build/repo/node_modules/node-sass
8:48:02 PM: > node scripts/build.js
8:48:02 PM: Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-72/binding.node
8:48:02 PM: Testing binary
8:48:02 PM: Binary is fine
8:48:05 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/react-scripts/node_modules/fsevents):
8:48:05 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:48:05 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/fsevents):
8:48:05 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:48:05 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/chokidar/node_modules/fsevents):
8:48:05 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:48:05 PM: added 2009 packages from 830 contributors and audited 2014 packages in 47.253s
8:48:07 PM: 72 packages are looking for funding
8:48:07 PM: run npm fund for details
8:48:07 PM: found 3596 low severity vulnerabilities
8:48:07 PM: run npm audit fix to fix them, or npm audit for details
8:48:07 PM: NPM modules installed
8:48:07 PM: Started restoring cached go cache
8:48:07 PM: Finished restoring cached go cache
8:48:07 PM: go version go1.14.4 linux/amd64
8:48:07 PM: go version go1.14.4 linux/amd64
8:48:07 PM: Installing missing commands
8:48:07 PM: Verify run directory
8:48:08 PM: ​
8:48:08 PM: ┌─────────────────────────────┐
8:48:08 PM: │ Netlify Build │
8:48:08 PM: └─────────────────────────────┘
8:48:08 PM: ​
8:48:08 PM: ❯ Version
8:48:08 PM: @netlify/build 3.3.0
8:48:08 PM: ​
8:48:08 PM: ❯ Flags
8:48:08 PM: deployId: 5f4ef99b49978800076d46b6
8:48:08 PM: mode: buildbot
8:48:08 PM: ​
8:48:08 PM: ❯ Current directory
8:48:08 PM: /opt/build/repo
8:48:08 PM: ​
8:48:08 PM: ❯ Config file
8:48:08 PM: No config file was defined: using default values.
8:48:08 PM: ​
8:48:08 PM: ❯ Context
8:48:08 PM: deploy-preview
8:48:08 PM: ​
8:48:08 PM: ┌───────────────────────────────────┐
8:48:08 PM: │ 1. Build command from Netlify app │
8:48:08 PM: └───────────────────────────────────┘
8:48:08 PM: ​
8:48:08 PM: $ npm start
8:48:09 PM: > game-of-life@0.1.0 start /opt/build/repo
8:48:09 PM: > react-scripts start
8:48:10 PM: ｢wds｣: Project is running at http://10.4.98.234/
8:48:10 PM: ｢wds｣: webpack output is served from /bwkarr77/game-of-life
8:48:10 PM: ｢wds｣: Content not from webpack is served from /opt/build/repo/public
8:48:10 PM: ｢wds｣: 404s will fallback to /bwkarr77/game-of-life/
8:48:10 PM: Starting the development server…
8:48:10 PM:
8:48:36 PM: Compiled with warnings.
8:48:36 PM:
8:48:36 PM: ./src/components/3D/Settings3D.jsx
8:48:36 PM: Line 31:10: ‘rules’ is assigned a value but never used no-unused-vars
8:48:36 PM: Line 31:17: ‘setRules’ is assigned a value but never used no-unused-vars
8:48:36 PM: ./src/components/files/presets3D.jsx
8:48:36 PM: Line 35:7: ‘toBlock’ is assigned a value but never used no-unused-vars
8:48:36 PM: Line 43:7: ‘toEgg’ is assigned a value but never used no-unused-vars
8:48:36 PM: Line 62:7: ‘ship1’ is assigned a value but never used no-unused-vars
8:48:36 PM: ./src/components/Navbar.jsx
8:48:36 PM: Line 3:20: ‘Router’ is defined but never used no-unused-vars
8:48:36 PM: Line 4:3: ‘Route’ is defined but never used no-unused-vars
8:48:36 PM: Line 8:10: ‘Divider’ is defined but never used no-unused-vars
8:48:36 PM: ./src/components/Game/Grid.jsx
8:48:36 PM: Line 3:8: ‘UseStyling’ is defined but never used no-unused-vars
8:48:36 PM: Line 6:28: ‘colorStyle’ is assigned a value but never used no-unused-vars
8:48:36 PM: ./src/components/Game/Settings.jsx
8:48:36 PM: Line 3:8: ‘Presets’ is defined but never used no-unused-vars
8:48:36 PM: ./src/components/settings/Rules.jsx
8:48:36 PM: Line 5:43: ‘setRules’ is assigned a value but never used no-unused-vars
8:48:36 PM: ./src/components/3D/Game3DClassTest.jsx
8:48:36 PM: Line 6:10: ‘Divider’ is defined but never used no-unused-vars
8:48:36 PM: Search for the keywords to learn more about each warning.
8:48:36 PM: To ignore, add // eslint-disable-next-line to the line before.
9:17:08 PM: Build exceeded maximum allowed runtime
9:17:08 PM: Failed to compile.
9:17:08 PM:
9:17:08 PM: ./src/index.js
9:17:08 PM: Error: ENOENT: no such file or directory, open ‘/opt/build/repo/src/index.js’

[perry]

hey there!

A couple of things are going on here we’re gonna want to iron out.

First, it seems like you are doing quite a bit of linting (error checking) on deploy - that’s not what is causing your build error, but it is good practice to only deploy code that has passed linting locally

Secondly, this is possibly related but maybe not:

9:17:08 PM: Build exceeded maximum allowed runtime
9:17:08 PM: Failed to compile.

our standard runtime for builds is 15 minutes.

unless your site is large, it should really build under that limit -

But i wonder if the linting you are doing is slowing us down (which is why i say maybe related) and we are hitting that 15 min ceiling as a result.

If i were you i’d lint locally, remove that process from my production build process, and try and see if that cuts your build time down to under 15 min.

Some other resources:

[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] 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…