First deploy problems - react project

[KajiyamaVK]

Hi guys,

First of all - sorry… I’m really new at this.

I wanted to make my website first deploy and I’m getting this error here. First, I want to highlight some points that could help you guys with my solution.

1 - I don’t have the node_modules folder here. As I put the node_modules in gitIgnore, the file wasn’t sent here.
2 - I didn’t build my project locally. I’m doing this just here. Should I build it and send the build folder here?

This is the the log that I’m getting.

2:20:56 AM: Build ready to start
2:20:58 AM: build-image version: c23500190e408b04bdfcf9703d16c460ef03b813
2:20:58 AM: build-image tag: v3.3.15
2:20:58 AM: buildbot version: 85ab9be17c6555a1d991d1cf7b0dbb73c18d0b92
2:20:58 AM: Fetching cached dependencies
2:20:58 AM: Starting to download cache of 254.3KB
2:20:58 AM: Finished downloading cache in 79.922933ms
2:20:58 AM: Starting to extract cache
2:20:58 AM: Failed to fetch cache, continuing with build
2:20:58 AM: Starting to prepare the repo for build
2:20:58 AM: No cached dependencies found. Cloning fresh repo
2:20:58 AM: git clone https://github.com/KajiyamaVK/Kajix
2:21:00 AM: Preparing Git Reference refs/heads/master
2:21:01 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘build’ versus ‘./build’ in the Netlify UI
2:21:01 AM: Starting build script
2:21:01 AM: Installing dependencies
2:21:01 AM: Python version set to 2.7
2:21:02 AM: Downloading and installing node v10.21.0…
2:21:02 AM: Downloading https://nodejs.org/dist/v10.21.0/node-v10.21.0-linux-x64.tar.xz…
2:21:03 AM: Computing checksum with sha256sum
2:21:03 AM: Checksums matched!
2:21:05 AM: Now using node v10.21.0 (npm v6.14.4)
2:21:05 AM: Started restoring cached build plugins
2:21:05 AM: Finished restoring cached build plugins
2:21:06 AM: Attempting ruby version 2.6.2, read from environment
2:21:07 AM: Using ruby version 2.6.2
2:21:07 AM: Using PHP version 5.6
2:21:07 AM: 5.2 is already installed.
2:21:07 AM: Using Swift version 5.2
2:21:07 AM: Started restoring cached node modules
2:21:07 AM: Finished restoring cached node modules
2:21:07 AM: Installing NPM modules using NPM version 6.14.4
2:21:36 AM: > node-sass@4.13.0 install /opt/build/repo/node_modules/node-sass
2:21:36 AM: > node scripts/install.js
2:21:37 AM: Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.0/linux-x64-64_binding.node
2:21:37 AM: Download complete
2:21:37 AM: Binary saved to /opt/build/repo/node_modules/node-sass/vendor/linux-x64-64/binding.node
2:21:37 AM: Caching binary to /opt/buildhome/.npm/node-sass/4.13.0/linux-x64-64_binding.node
2:21:37 AM: > core-js@2.6.8 postinstall /opt/build/repo/node_modules/babel-runtime/node_modules/core-js
2:21:37 AM: > node -e “try { require(‘./scripts/postinstall’); } catch (e) { /* empty / }"
2:21:38 AM: > core-js@3.6.2 postinstall /opt/build/repo/node_modules/core-js
2:21:38 AM: > node -e “try{require(‘./postinstall’)}catch(e){}”
2:21:38 AM: > core-js-pure@3.1.2 postinstall /opt/build/repo/node_modules/core-js-pure
2:21:38 AM: > node -e "try { require(‘./scripts/postinstall’); } catch (e) { / empty */ }”
2:21:38 AM: > node-sass@4.13.0 postinstall /opt/build/repo/node_modules/node-sass
2:21:38 AM: > node scripts/build.js
2:21:38 AM: Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-64/binding.node
2:21:38 AM: Testing binary
2:21:38 AM: Binary is fine
2:21:41 AM: npm
2:21:41 AM: WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/jest-haste-map/node_modules/fsevents):
2:21:41 AM: npm
2:21:41 AM: WARN
2:21:41 AM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
2:21:41 AM: npm
2:21:41 AM: WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/fsevents):
2:21:41 AM: npm
2:21:41 AM: WARN
2:21:41 AM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
2:21:41 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/chokidar/node_modules/fsevents):
2:21:41 AM: npm WARN
2:21:41 AM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
2:21:41 AM: added 1704 packages from 874 contributors and audited 1913 packages in 32.381s
2:21:42 AM: 4 packages are looking for funding
2:21:42 AM: run npm fund for details
2:21:42 AM: found 55037 vulnerabilities (38934 low, 21 moderate, 16081 high, 1 critical)
2:21:42 AM: run npm audit fix to fix them, or npm audit for details
2:21:42 AM: NPM modules installed
2:21:42 AM: Started restoring cached go cache
2:21:42 AM: Finished restoring cached go cache
2:21:42 AM: go version go1.12 linux/amd64
2:21:42 AM: go version go1.12 linux/amd64
2:21:42 AM: Installing missing commands
2:21:42 AM: Verify run directory
2:21:44 AM: ​
2:21:44 AM: ┌─────────────────────────────┐
2:21:44 AM: │ Netlify Build │
2:21:44 AM: └─────────────────────────────┘
2:21:44 AM: ​
2:21:44 AM: ❯ Version
2:21:44 AM: @netlify/build 2.0.10
2:21:44 AM: ​
2:21:44 AM: ❯ Flags
2:21:44 AM: deployId: 5eea50f8b4be4138da718881
2:21:44 AM: mode: buildbot
2:21:44 AM: ​
2:21:44 AM: ❯ Current directory
2:21:44 AM: /opt/build/repo
2:21:44 AM: ​
2:21:44 AM: ❯ Config file
2:21:44 AM: No config file was defined: using default values.
2:21:44 AM: ​
2:21:44 AM: ❯ Context
2:21:44 AM: production
2:21:44 AM: ​
2:21:44 AM: ┌────────────────────────────────┐
2:21:44 AM: │ 1. Build command from settings │
2:21:44 AM: └────────────────────────────────┘
2:21:44 AM: ​
2:21:44 AM: $ npm run build
2:21:44 AM: > trydo@0.1.0 build /opt/build/repo
2:21:44 AM: > node scripts/build.js
2:21:45 AM: Creating an optimized production build…
2:21:47 AM: Browserslist: caniuse-lite is outdated. Please run next command npm update
2:22:32 AM:
2:22:32 AM: Treating warnings as errors because process.env.CI = true.
2:22:32 AM: Most CI servers set it automatically.
2:22:32 AM:
2:22:32 AM: Failed to compile.
2:22:32 AM:
2:22:32 AM: ./src/dark/MainDemo.jsx
2:22:32 AM: Line 10:8: ‘Testimonial’ is defined but never used no-unused-vars
2:22:32 AM: Line 12:8: ‘Portfolio’ is defined but never used no-unused-vars
2:22:32 AM: Line 14:8: ‘BrandTwo’ is defined but never used no-unused-vars
2:22:32 AM: Line 19:9: ‘PostList’ is assigned a value but never used no-unused-vars
2:22:32 AM: ./src/home/Interior.jsx
2:22:32 AM: Line 11:10: ‘slickDot’ is defined but never used no-unused-vars
2:22:32 AM: ./src/index.js
2:22:32 AM: Line 12:8: ‘Demo’ is defined but never used no-unused-vars
2:22:32 AM: ./src/blocks/Counters.jsx
2:22:32 AM: Line 2:8: ‘TeamOne’ is defined but never used no-unused-vars
2:22:32 AM: ./src/elements/Contact.jsx
2:22:32 AM: Line 3:32: ‘FiMapPin’ is defined but never used no-unused-vars
2:22:32 AM: Line 5:8: ‘GoogleMapReact’ is defined but never used no-unused-vars
2:22:32 AM: Line 7:8: ‘BrandTwo’ is defined but never used no-unused-vars
2:22:32 AM: Line 13:7: ‘AnyReactComponent’ is assigned a value but never used no-unused-vars
2:22:32 AM: npm
2:22:32 AM: ERR!
2:22:32 AM: code ELIFECYCLE
2:22:32 AM: npm
2:22:32 AM: ERR! errno 1
2:22:32 AM: npm
2:22:32 AM: ERR!
2:22:32 AM: trydo@0.1.0 build: node scripts/build.js
2:22:32 AM: npm
2:22:32 AM: ERR! Exit status 1
2:22:32 AM: npm
2:22:32 AM: ERR!
2:22:32 AM: npm
2:22:32 AM: ERR!
2:22:32 AM: Failed at the trydo@0.1.0 build script.
2:22:32 AM: npm
2:22:32 AM: ERR! This is probably not a problem with npm. There is likely additional logging output above.
2:22:32 AM: npm
2:22:32 AM: ERR!
2:22:32 AM: A complete log of this run can be found in:
2:22:32 AM: npm
2:22:32 AM: ERR!
2:22:32 AM: /opt/buildhome/.npm/_logs/2020-06-17T17_22_32_558Z-debug.log
2:22:32 AM: ​
2:22:32 AM: ┌─────────────────────────────┐
2:22:32 AM: │ “build.command” failed │
2:22:32 AM: └─────────────────────────────┘
2:22:32 AM: ​
2:22:32 AM: Error message
2:22:32 AM: Command failed with exit code 1: npm run build
2:22:32 AM: ​
2:22:32 AM: Error location
2:22:32 AM: In Build command from settings:
2:22:32 AM: npm run build
2:22:32 AM: ​
2:22:32 AM: Resolved config
2:22:32 AM: build:
2:22:32 AM: command: npm run build
2:22:32 AM: publish: /opt/build/repo/build
2:22:32 AM: Caching artifacts
2:22:32 AM: Started saving node modules
2:22:32 AM: Finished saving node modules
2:22:32 AM: Started saving build plugins
2:22:32 AM: Finished saving build plugins
2:22:32 AM: Started saving pip cache
2:22:32 AM: Finished saving pip cache
2:22:32 AM: Started saving emacs cask dependencies
2:22:32 AM: Finished saving emacs cask dependencies
2:22:32 AM: Started saving maven dependencies
2:22:32 AM: Finished saving maven dependencies
2:22:32 AM: Started saving boot dependencies
2:22:33 AM: Finished saving boot dependencies
2:22:33 AM: Started saving go dependencies
2:22:33 AM: Finished saving go dependencies
2:22:36 AM: Error running command: Build script returned non-zero exit code: 1
2:22:36 AM: Failing build: Failed to build site
2:22:36 AM: Failed during stage ‘building site’: Build script returned non-zero exit code: 1
2:22:36 AM: Finished processing build request in 1m38.287256144s

What am I doing wrong?

[perry]

hi there, please take a look at this post! it likely holds the answer.

New CI=true build configuration, "Treating warnings as errors because process.env.CI = true"

Beginning on June 15, 2020 Netlify will start a gradual rollout of adding the environment variable CI to build environments, with the value of true . This environment variable, short for Continuous Integration, is commonly set in various CI environments like Travis CI and Github Actions, among many others. The ecosystem has largely agreed to use this environment setting to detect when a build is executing in a CI environment, as opposed to a local development environment. This setting allows…

[KajiyamaVK]

It really worked. For those who are here to check about the problem - the issue was that the Warnings that I had were being considered as errors. As pointed out I could have 2 options - please check the post that I marked as a solution.

Thanks man.