Website is deploying for longer then it should to show me an error

So… I was deploying my react website for the first time here, and I ran into some weird issues.
After trying out some things like cleaning the deployment cache and the like I changed the run command from npm run build to npm run start.
After which I got the following problem. The website build did not “crash” but is building without ever stopping (while I am writting this post at least).

Help/tips appreciated.

Blockquote
7:22:49 PM: Build ready to start
7:22:51 PM: build-image version: e4d2dbe4cfec46db257e869258461ded89b75c9b
7:22:51 PM: build-image tag: v3.7.3
7:22:51 PM: buildbot version: 2cb5794cb93042dadefe5dbdc6b35edc34c20454
7:22:51 PM: Fetching cached dependencies
7:22:51 PM: Failed to fetch cache, continuing with build
7:22:51 PM: Starting to prepare the repo for build
7:22:51 PM: No cached dependencies found. Cloning fresh repo
7:22:51 PM: git clone GitHub - Shogun321/Novi-repo
7:22:52 PM: Preparing Git Reference refs/heads/main
7:22:52 PM: Parsing package.json dependencies
7:22:53 PM: Starting build script
7:22:53 PM: Installing dependencies
7:22:53 PM: Python version set to 2.7
7:22:55 PM: v12.18.0 is already installed.
7:22:55 PM: Now using node v12.18.0 (npm v6.14.4)
7:22:55 PM: Started restoring cached build plugins
7:22:55 PM: Finished restoring cached build plugins
7:22:55 PM: Attempting ruby version 2.7.1, read from environment
7:22:57 PM: Using ruby version 2.7.1
7:22:57 PM: Using PHP version 5.6
7:22:57 PM: Started restoring cached node modules
7:22:57 PM: Finished restoring cached node modules
7:22:57 PM: Installing NPM modules using NPM version 6.14.4
7:23:35 PM: > core-js@2.6.12 postinstall /opt/build/repo/node_modules/babel-runtime/node_modules/core-js
7:23:35 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
7:23:35 PM: > core-js@3.11.1 postinstall /opt/build/repo/node_modules/core-js
7:23:35 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
7:23:35 PM: > core-js-pure@3.11.1 postinstall /opt/build/repo/node_modules/core-js-pure
7:23:35 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
7:23:36 PM: > ejs@2.7.4 postinstall /opt/build/repo/node_modules/ejs
7:23:36 PM: > node ./postinstall.js
7:23:38 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
7:23:38 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
7:23:38 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
7:23:38 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
7:23:38 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
7:23:38 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
7:23:38 PM: added 1987 packages from 807 contributors and audited 1990 packages in 40.322s
7:23:40 PM: 139 packages are looking for funding
7:23:40 PM: run npm fund for details
7:23:40 PM: found 0 vulnerabilities
7:23:40 PM: NPM modules installed
7:23:40 PM: Started restoring cached go cache
7:23:40 PM: Finished restoring cached go cache
7:23:40 PM: go version go1.14.4 linux/amd64
7:23:40 PM: go version go1.14.4 linux/amd64
7:23:40 PM: Installing missing commands
7:23:40 PM: Verify run directory
7:23:42 PM: ​
7:23:42 PM: ────────────────────────────────────────────────────────────────
7:23:42 PM: Netlify Build
7:23:42 PM: ────────────────────────────────────────────────────────────────
7:23:42 PM: ​
7:23:42 PM: ❯ Version
7:23:42 PM: @netlify/build 11.5.1
7:23:42 PM: ​
7:23:42 PM: ❯ Flags
7:23:42 PM: deployId: 608edfe98f94e5d62bcd61ac
7:23:42 PM: ​
7:23:42 PM: ❯ Current directory
7:23:42 PM: /opt/build/repo
7:23:42 PM: ​
7:23:42 PM: ❯ Config file
7:23:42 PM: No config file was defined: using default values.
7:23:42 PM: ​
7:23:42 PM: ❯ Context
7:23:42 PM: production
7:23:42 PM: ​
7:23:42 PM: ────────────────────────────────────────────────────────────────
7:23:42 PM: 1. Build command from Netlify app
7:23:42 PM: ────────────────────────────────────────────────────────────────
7:23:42 PM: ​
7:23:42 PM: $ npm run start
7:23:42 PM: > my-app@0.1.0 start /opt/build/repo
7:23:42 PM: > react-scripts start
7:23:45 PM: :information_source: 「wds」: Project is running at http://10.5.145.20/
7:23:45 PM: :information_source: 「wds」: webpack output is served from
7:23:45 PM: :information_source: 「wds」: Content not from webpack is served from /opt/build/repo/public
7:23:45 PM: :information_source: 「wds」: 404s will fallback to /
7:23:45 PM: Starting the development server…
7:23:45 PM:
7:23:59 PM: Compiled with warnings.
7:23:59 PM:
7:23:59 PM: src/components/NavBar.js
7:23:59 PM: Line 12:9: Unnecessarily computed property [’@media (max-width:780px)’] found no-useless-computed-key
7:23:59 PM: Line 18:9: Unnecessarily computed property [’@media (max-width:780px)’] found no-useless-computed-key
7:23:59 PM: Line 25:9: Unnecessarily computed property [’@media (max-width:780px)’] found no-useless-computed-key
7:23:59 PM: Line 35:9: Unnecessarily computed property [’@media (max-width:780px)’] found no-useless-computed-key
7:23:59 PM: Search for the keywords to learn more about each warning.
7:23:59 PM: To ignore, add // eslint-disable-next-line to the line before.

You’re running a development server, not a production build. Thus, the error. The build will eventually timeout and fail. You should have a command that would help you compile a production bundle.

2 Likes