Home
Support Forums

I cant deploy my portfolio!

PLEASE help us help you by writing a good post!

  • we need to know your netlify site name. Example: gifted-antelope-58b104.netlify.app
  • DNS issues? Tell us the custom domain, tell us the error message! We can’t help if we don’t know your domain.
  • Build problems? Link or paste the FULL build log & build settings screenshot

The better the post - the faster the answer.

Good evening, it has definitely been answered countless times here in this forum, by many who have found the solution.

Unfortunately, I tried to follow the steps, the solutions some of you suggest but I think that after 20 failed attempts it is time to take seriously what is happening with Netlify.

First, a step I deleted yarn. lock and package-lock as suggested for conflict reasons. Deploy failed

Second, I replaced the CI= npm run build solution as found here. Deploy failed

Third, add true at the build command and then npm run build. Deploy works but not page found.

Fourth, try run different possible commands such as : “npm run”, “npm run react-script/build” and many more.

Sixth my “scripts” folder in my package.json files has the following:
“scripts”: {

"start": "react-scripts start",

"build": "react-scripts build",

"test": "react-scripts test",

"eject": "react-scripts eject"

},
Seventh, locally in my computer the app is working fine not problems.

Eight provides information such as last diploy:

9:28:39 PM: Build ready to start
9:28:41 PM: build-image version: 2cee85eb7f808bf3b6e87378c5307f9411f0a332
9:28:41 PM: build-image tag: v3.8.0
9:28:41 PM: buildbot version: d9a660540b05c414edfc0246347871ef0e3afee9
9:28:41 PM: Building without cache
9:28:41 PM: Starting to prepare the repo for build
9:28:41 PM: No cached dependencies found. Cloning fresh repo
9:28:41 PM: git clone GitHub - OldDognoob/NPortfolio: This project is about creating a personal portfolio using React
9:28:43 PM: Preparing Git Reference refs/heads/master
9:28:44 PM: Parsing package.json dependencies
9:28:44 PM: Starting build script
9:28:44 PM: Installing dependencies
9:28:44 PM: Python version set to 2.7
9:28:46 PM: v12.18.0 is already installed.
9:28:46 PM: Now using node v12.18.0 (npm v6.14.4)
9:28:46 PM: Started restoring cached build plugins
9:28:46 PM: Finished restoring cached build plugins
9:28:47 PM: Attempting ruby version 2.7.2, read from environment
9:28:48 PM: Using ruby version 2.7.2
9:28:49 PM: Using PHP version 5.6
9:28:49 PM: Started restoring cached go cache
9:28:49 PM: Finished restoring cached go cache
9:28:49 PM: go version go1.14.4 linux/amd64
9:28:49 PM: go version go1.14.4 linux/amd64
9:28:49 PM: Installing missing commands
9:28:49 PM: Verify run directory
9:28:49 PM: ​
9:28:49 PM: ────────────────────────────────────────────────────────────────
9:28:49 PM: Netlify Build
9:28:49 PM: ────────────────────────────────────────────────────────────────
9:28:49 PM: ​
9:28:49 PM: ❯ Version
9:28:49 PM: @netlify/build 15.11.2
9:28:49 PM: ​
9:28:49 PM: ❯ Flags
9:28:49 PM: deployId: 60ef2cd734df8f30016eb063
9:28:49 PM: ​
9:28:49 PM: ❯ Current directory
9:28:49 PM: /opt/build/repo
9:28:49 PM: ​
9:28:49 PM: ❯ Config file
9:28:49 PM: No config file was defined: using default values.
9:28:49 PM: ​
9:28:49 PM: ❯ Context
9:28:49 PM: production
9:28:49 PM: ​
9:28:49 PM: ────────────────────────────────────────────────────────────────
9:28:49 PM: 1. Build command from Netlify app
9:28:49 PM: ────────────────────────────────────────────────────────────────
9:28:49 PM: ​
9:28:49 PM: $ CI= npm run build
9:28:50 PM: npm ERR! code ENOENT
9:28:50 PM: npm ERR! syscall open
9:28:50 PM: npm ERR! path /opt/build/repo/package.json
9:28:50 PM: npm ERR! errno -2
9:28:50 PM: npm ERR! enoent ENOENT: no such file or directory, open ‘/opt/build/repo/package.json’
9:28:50 PM: npm ERR! enoent This is related to npm not being able to find a file.
9:28:50 PM: npm ERR! enoent
9:28:50 PM: npm ERR! A complete log of this run can be found in:
9:28:50 PM: npm ERR! /opt/buildhome/.npm/_logs/2021-07-14T18_28_50_124Z-debug.log
9:28:50 PM: ​
9:28:50 PM: ────────────────────────────────────────────────────────────────
9:28:50 PM: “build.command” failed
9:28:50 PM: ────────────────────────────────────────────────────────────────
9:28:50 PM: ​
9:28:50 PM: Error message
9:28:50 PM: Command failed with exit code 254: CI= npm run build
9:28:50 PM: ​
9:28:50 PM: Error location
9:28:50 PM: In Build command from Netlify app:
9:28:50 PM: CI= npm run build
9:28:50 PM: ​
9:28:50 PM: Resolved config
9:28:50 PM: build:
9:28:50 PM: command: CI= npm run build
9:28:50 PM: commandOrigin: ui
9:28:50 PM: environment:
9:28:50 PM: - CI
9:28:50 PM: publish: /opt/build/repo
9:28:50 PM: publishOrigin: default
9:28:50 PM: Caching artifacts
9:28:50 PM: Started saving build plugins
9:28:50 PM: Finished saving build plugins
9:28:50 PM: Started saving pip cache
9:28:50 PM: Finished saving pip cache
9:28:50 PM: Started saving emacs cask dependencies
9:28:50 PM: Finished saving emacs cask dependencies
9:28:50 PM: Started saving maven dependencies
9:28:50 PM: Finished saving maven dependencies
9:28:50 PM: Started saving boot dependencies
9:28:50 PM: Finished saving boot dependencies
9:28:50 PM: Started saving rust rustup cache
9:28:50 PM: Finished saving rust rustup cache
9:28:50 PM: Started saving go dependencies
9:28:50 PM: Finished saving go dependencies
9:28:53 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
9:28:53 PM: Creating deploy upload records
9:28:53 PM: Failing build: Failed to build site
9:28:53 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2
9:28:53 PM: Finished processing build request in 12.217471901s

My site name is : https://dimoschris.com

Any more info you need , I will provide you .
Any solution would be awesome.
Thank you in advance.

hi there, do you have a package.json file included in your project? that is different from a package lock file and should not be deleted.

do you have one on your local machine? if no, you will have to make one, either manually OR by doing “npm init” again.

Hello, of course

{

“name”: “my-portfolio”,

“version”: “0.1.0”,

“private”: true,

“dependencies”: {

"@fortawesome/fontawesome-svg-core": "^1.2.35",

"@fortawesome/free-brands-svg-icons": "^5.15.3",

"@fortawesome/free-regular-svg-icons": "^5.15.3",

"@fortawesome/free-solid-svg-icons": "^5.15.3",

"@fortawesome/react-fontawesome": "^0.1.14",

"@testing-library/jest-dom": "^5.11.4",

"@testing-library/react": "^11.1.0",

"@testing-library/user-event": "^12.1.10",

"aos": "^2.3.4",

"bootstrap": "^5.0.1",

"emailjs-com": "^3.1.0",

"firebase": "^8.6.7",

"framer-motion": "^4.1.17",

"jsx-to-string": "^1.4.0",

"react": "^17.0.2",

"react-bootstrap": "^1.6.1",

"react-dom": "^17.0.2",

"react-icons": "^4.2.0",

"react-masonry-css": "^1.0.16",

"react-router-dom": "^5.2.0",

"react-scripts": "^4.0.3",

"react-tsparticles": "^1.28.1",

"typewriter-effect": "^2.18.0",

"web-vitals": "^1.0.1"

},

“scripts”: {

"start": "react-scripts start",

"build": "react-scripts build",

"test": "react-scripts test",

"eject": "react-scripts eject"

},

“eslintConfig”: {

"extends": [

  "react-app",

  "react-app/jest"

]

},

“browserslist”: {

"production": [

  ">0.2%",

  "not dead",

  "not op_mini all"

],

"development": [

  "last 1 chrome version",

  "last 1 firefox version",

  "last 1 safari version"

]

}

}

Your site in a directory called my-portfolio rather that the root of your repo @DocMustang . Which is why you see the error

npm ERR! enoent ENOENT: no such file or directory, open ‘/opt/build/repo/package.json’

You are building from a sub-directory so need to set the Base directory in your Netlify build settings? e.g.

  • in the UI when you create a New site from Git . For an existing site, you can update the setting at Site settings > Build & deploy > Continuous Deployment > Build settings .

Hello again,
Let me clarify what you are saying to me, I need to set my sub-directory to be the Base directory in Netlify settings. Looking through the info docs you provide me, I try to set up the following at the Build setting window as follow:


But no luck! Attempting 30 failed
Deploy log:
2:25:49 PM: Build ready to start

2:25:51 PM: build-image version: 2cee85eb7f808bf3b6e87378c5307f9411f0a332

2:25:51 PM: build-image tag: v3.8.0

2:25:51 PM: buildbot version: 30dbdb4695638bcc89067dec803733260bd838a5

2:25:51 PM: Building without cache

2:25:51 PM: Starting to prepare the repo for build

2:25:52 PM: No cached dependencies found. Cloning fresh repo

2:25:52 PM: git clone GitHub - OldDognoob/NPortfolio: This project is about creating a personal portfolio using React

2:25:53 PM: Preparing Git Reference refs/heads/master

2:25:54 PM: Parsing package.json dependencies

2:25:54 PM: Different build dir detected, going to use the one specified in the Netlify configuration file: ‘my-portfolio’ versus ‘/my-portfolio’ in the Netlify UI

2:25:54 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘my-portfolio/build’ versus ‘build’ in the Netlify UI

2:25:55 PM: Starting build script

2:25:55 PM: Installing dependencies

2:25:55 PM: Python version set to 2.7

2:25:56 PM: v12.18.0 is already installed.

2:25:57 PM: Now using node v12.18.0 (npm v6.14.4)

2:25:57 PM: Started restoring cached build plugins

2:25:57 PM: Finished restoring cached build plugins

2:25:57 PM: Attempting ruby version 2.7.2, read from environment

2:25:58 PM: Using ruby version 2.7.2

2:25:59 PM: Using PHP version 5.6

2:25:59 PM: Started restoring cached node modules

2:25:59 PM: Finished restoring cached node modules

2:25:59 PM: Installing NPM modules using NPM version 6.14.4

2:26:02 PM: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I’ll try to do my best with it!
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

2:26:02 PM: npm ERR! code EBADPLATFORM

2:26:02 PM: npm ERR! notsup Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

2:26:02 PM: npm ERR! notsup Valid OS: darwin

2:26:02 PM: npm ERR! notsup Valid Arch: any

2:26:02 PM: npm ERR! notsup Actual OS: linux

2:26:02 PM: npm ERR! notsup Actual Arch: x64

2:26:02 PM: npm ERR! A complete log of this run can be found in:

2:26:02 PM: npm ERR! /opt/buildhome/.npm/_logs/2021-07-15T11_26_02_922Z-debug.log

2:26:02 PM: Error during NPM install

2:26:02 PM: Build was terminated: Build script returned non-zero exit code: 1

2:26:03 PM: Creating deploy upload records

2:26:03 PM: Failing build: Failed to build site

2:26:03 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 1

2:26:03 PM: Finished processing build request in 11.422783755s

So, either I am stupid enough or I don’t understand or something else is the problem and I can’t find it.

Without leading / @DocMustang

Good evening again, first of all, I want to thank you both of you for the help you offered me.
After the last message, I made the changes needed but I am unhappy as the result is the same.
Probably Netlify does not let me refresh my site.
I quote you the last Diary log:
5:58:10 PM: Build ready to start

5:58:22 PM: build-image version: 2cee85eb7f808bf3b6e87378c5307f9411f0a332

5:58:22 PM: build-image tag: v3.8.0

5:58:22 PM: buildbot version: 30dbdb4695638bcc89067dec803733260bd838a5

5:58:22 PM: Building without cache

5:58:22 PM: Starting to prepare the repo for build

5:58:22 PM: No cached dependencies found. Cloning fresh repo

5:58:22 PM: git clone GitHub - OldDognoob/NPortfolio: This project is about creating a personal portfolio using React

5:58:24 PM: Preparing Git Reference refs/heads/master

5:58:25 PM: Parsing package.json dependencies

5:58:25 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘my-portfolio/build’ versus ‘build’ in the Netlify UI

5:58:25 PM: Starting build script

5:58:25 PM: Installing dependencies

5:58:25 PM: Python version set to 2.7

5:58:27 PM: v12.18.0 is already installed.

5:58:27 PM: Now using node v12.18.0 (npm v6.14.4)

5:58:27 PM: Started restoring cached build plugins

5:58:27 PM: Finished restoring cached build plugins

5:58:27 PM: Attempting ruby version 2.7.2, read from environment

5:58:29 PM: Using ruby version 2.7.2

5:58:29 PM: Using PHP version 5.6

5:58:29 PM: Started restoring cached node modules

5:58:29 PM: Finished restoring cached node modules

5:58:29 PM: Installing NPM modules using NPM version 6.14.4

5:58:32 PM: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I’ll try to do my best with it!
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

5:58:32 PM: npm ERR! code EBADPLATFORM

5:58:32 PM: npm ERR! notsup Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

5:58:32 PM: npm ERR! notsup Valid OS: darwin

5:58:32 PM: npm ERR! notsup Valid Arch: any

5:58:32 PM: npm ERR! notsup Actual OS: linux

5:58:32 PM: npm ERR! notsup Actual Arch: x64

5:58:32 PM: npm ERR! A complete log of this run can be found in:

5:58:32 PM: npm ERR! /opt/buildhome/.npm/_logs/2021-07-15T14_58_32_949Z-debug.log

5:58:32 PM: Error during NPM install

5:58:32 PM: Build was terminated: Build script returned non-zero exit code: 1

5:58:33 PM: Creating deploy upload records

5:58:33 PM: Failing build: Failed to build site

5:58:33 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 1

5:58:33 PM: Finished processing build request in 10.919898086s

And how it shows at the Continuous Deployment page:

Every effort is a fail.
I will try to see if there are any other options.
Thank you for your help.

Returning to the topic, after 4o failed attempts and 2 days working thoroughly I managed to upload my portfolio. After exhaustive research here on the forum and on other sites, I came to the conclusion that Netlify can make you lose weight! :rofl:
I followed the following actions:

  1. I upgraded to the latest npm edition with the command: npm install -g npm to overcome this problem:
    "npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I’ll try to do my best with it!
    npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

5:58:32 PM: npm ERR! code EBADPLATFORM

5:58:32 PM: npm ERR! notsup Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

5:58:32 PM: npm ERR! notsup Valid OS: darwin

5:58:32 PM: npm ERR! notsup Valid Arch: any

5:58:32 PM: npm ERR! notsup Actual OS: linux

5:58:32 PM: npm ERR! notsup Actual Arch: x64

5:58:32 PM: npm ERR! A complete log of this run can be found in:

5:58:32 PM: npm ERR! /opt/buildhome/.npm/_logs/2021-07-15T14_58_32_949Z-debug.log

5:58:32 PM: Error during NPM install "
2. I define the build command appropriately:


3. The portfolio works now.
4. The diary log at this time is the following:
8:30:36 PM: Build ready to start
8:30:39 PM: build-image version: 2cee85eb7f808bf3b6e87378c5307f9411f0a332
8:30:39 PM: build-image tag: v3.8.0
8:30:39 PM: buildbot version: 32ee034528f86819a5a44b62c049d133b2305b7d
8:30:39 PM: Building without cache
8:30:39 PM: Starting to prepare the repo for build
8:30:39 PM: No cached dependencies found. Cloning fresh repo
8:30:39 PM: git clone GitHub - OldDognoob/NPortfolio: This project is about creating a personal portfolio using React
8:30:41 PM: Preparing Git Reference refs/heads/master
8:30:42 PM: Parsing package.json dependencies
8:30:42 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘my-portfolio/build’ versus ‘build’ in the Netlify UI
8:30:42 PM: Starting build script
8:30:42 PM: Installing dependencies
8:30:42 PM: Python version set to 2.7
8:30:44 PM: v12.18.0 is already installed.
8:30:44 PM: Now using node v12.18.0 (npm v6.14.4)
8:30:44 PM: Started restoring cached build plugins
8:30:44 PM: Finished restoring cached build plugins
8:30:44 PM: Attempting ruby version 2.7.2, read from environment
8:30:46 PM: Using ruby version 2.7.2
8:30:46 PM: Using PHP version 5.6
8:30:46 PM: Started restoring cached node modules
8:30:46 PM: Finished restoring cached node modules
8:30:46 PM: Installing NPM modules using NPM version 6.14.4
8:31:35 PM: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I’ll try to do my best with it!
8:31:35 PM: > tsparticles@1.28.1 install /opt/build/repo/my-portfolio/node_modules/tsparticles
8:31:35 PM: > node ./scripts/install.js
8:31:35 PM: Thank you for installing tsParticles.
8:31:35 PM: Remember to checkout the official website https://particles.js.org to explore some samples.
8:31:35 PM: You can find more samples on CodePen too: https://codepen.io/collection/DPOage
8:31:35 PM: If you need documentation you can find it here: https://particles.js.org
8:31:35 PM: Remember to leave a star on the tsParticles repository if you like the project and want to support it: GitHub - matteobruni/tsparticles: tsParticles - Easily create highly customizable particles animations and use them as animated backgrounds for your website. Ready to use components available for React, Vue.js (2.x and 3.x), Angular, Svelte, jQuery, Preact, Inferno.
8:31:36 PM: > core-js@3.6.5 postinstall /opt/build/repo/my-portfolio/node_modules/@firebase/polyfill/node_modules/core-js
8:31:36 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
8:31:36 PM: > @fortawesome/fontawesome-common-types@0.2.35 postinstall /opt/build/repo/my-portfolio/node_modules/@fortawesome/fontawesome-common-types
8:31:36 PM: > node attribution.js
8:31:36 PM: Font Awesome Free 0.2.35 by @fontawesome - https://fontawesome.com
8:31:36 PM: License - Font Awesome (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
8:31:36 PM: > core-js@2.6.12 postinstall /opt/build/repo/my-portfolio/node_modules/babel-runtime/node_modules/core-js
8:31:36 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
8:31:36 PM: > core-js@3.15.2 postinstall /opt/build/repo/my-portfolio/node_modules/core-js
8:31:36 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
8:31:36 PM: > core-js-pure@3.14.0 postinstall /opt/build/repo/my-portfolio/node_modules/core-js-pure
8:31:36 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
8:31:36 PM: > ejs@2.7.4 postinstall /opt/build/repo/my-portfolio/node_modules/ejs
8:31:36 PM: > node ./postinstall.js
8:31:37 PM: > protobufjs@6.11.2 postinstall /opt/build/repo/my-portfolio/node_modules/protobufjs
8:31:37 PM: > node scripts/postinstall
8:31:37 PM: > @fortawesome/fontawesome-svg-core@1.2.35 postinstall /opt/build/repo/my-portfolio/node_modules/@fortawesome/fontawesome-svg-core
8:31:37 PM: > node attribution.js
8:31:38 PM: Font Awesome Free 1.2.35 by @fontawesome - https://fontawesome.com
8:31:38 PM: License - Font Awesome (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
8:31:38 PM: > @fortawesome/free-brands-svg-icons@5.15.3 postinstall /opt/build/repo/my-portfolio/node_modules/@fortawesome/free-brands-svg-icons
8:31:38 PM: > node attribution.js
8:31:38 PM: Font Awesome Free 5.15.3 by @fontawesome - https://fontawesome.com
8:31:38 PM: License - Font Awesome (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
8:31:38 PM: > @fortawesome/free-regular-svg-icons@5.15.3 postinstall /opt/build/repo/my-portfolio/node_modules/@fortawesome/free-regular-svg-icons
8:31:38 PM: > node attribution.js
8:31:38 PM: Font Awesome Free 5.15.3 by @fontawesome - https://fontawesome.com
8:31:38 PM: License - Font Awesome (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
8:31:38 PM: > @fortawesome/free-solid-svg-icons@5.15.3 postinstall /opt/build/repo/my-portfolio/node_modules/@fortawesome/free-solid-svg-icons
8:31:38 PM: > node attribution.js
8:31:38 PM: Font Awesome Free 5.15.3 by @fontawesome - https://fontawesome.com
8:31:38 PM: License - Font Awesome (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
8:31:41 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
8:31:41 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:31:41 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
8:31:41 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:31:41 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
8:31:41 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:31:41 PM: added 2182 packages from 1103 contributors and audited 2188 packages in 53.252s
8:31:43 PM: 155 packages are looking for funding
8:31:43 PM: run npm fund for details
8:31:43 PM: found 3 moderate severity vulnerabilities
8:31:43 PM: run npm audit fix to fix them, or npm audit for details
8:31:43 PM: NPM modules installed
8:31:43 PM: Started restoring cached go cache
8:31:43 PM: Finished restoring cached go cache
8:31:43 PM: go version go1.14.4 linux/amd64
8:31:43 PM: go version go1.14.4 linux/amd64
8:31:43 PM: Installing missing commands
8:31:43 PM: Verify run directory
8:31:44 PM: ​
8:31:44 PM: ────────────────────────────────────────────────────────────────
8:31:44 PM: Netlify Build
8:31:44 PM: ────────────────────────────────────────────────────────────────
8:31:44 PM: ​
8:31:44 PM: ❯ Version
8:31:44 PM: @netlify/build 15.11.5
8:31:44 PM: ​
8:31:44 PM: ❯ Flags
8:31:44 PM: deployId: 60f070bc0b7b532912052d28
8:31:44 PM: ​
8:31:44 PM: ❯ Current directory
8:31:44 PM: /opt/build/repo/my-portfolio
8:31:44 PM: ​
8:31:44 PM: ❯ Config file
8:31:44 PM: No config file was defined: using default values.
8:31:44 PM: ​
8:31:44 PM: ❯ Context
8:31:44 PM: production
8:31:44 PM: ​
8:31:44 PM: ────────────────────────────────────────────────────────────────
8:31:44 PM: 1. Build command from Netlify app
8:31:44 PM: ────────────────────────────────────────────────────────────────
8:31:44 PM: ​
8:31:44 PM: $ CI= npm run build
8:31:45 PM: > my-portfolio@0.1.0 build
8:31:45 PM: > react-scripts build
8:31:46 PM: Creating an optimized production build…
8:32:12 PM: Compiled with warnings.
8:32:12 PM:
8:32:12 PM: src/App.js
8:32:12 PM: Line 3:26: ‘Router’ is defined but never used no-unused-vars
8:32:12 PM: src/components/AboutMe/AboutMe.js
8:32:12 PM: Line 5:3: ‘faDesktop’ is defined but never used no-unused-vars
8:32:12 PM: Line 7:3: ‘faEye’ is defined but never used no-unused-vars
8:32:12 PM: Line 8:3: ‘faMobile’ is defined but never used no-unused-vars
8:32:12 PM: Line 23:13: Headings must have content and the content must be accessible by a screen reader jsx-a11y/heading-has-content
8:32:12 PM: Line 41:13: Using target="_blank" without rel=“noreferrer” is a security risk: see HTML Standard react/jsx-no-target-blank
8:32:12 PM: src/components/Header/Header.js
8:32:12 PM: Line 20:15: The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value. If you cannot provide a valid href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: eslint-plugin-jsx-a11y/anchor-is-valid.md at master · jsx-eslint/eslint-plugin-jsx-a11y · GitHub jsx-a11y/anchor-is-valid
8:32:12 PM: src/components/Home.js
8:32:12 PM: Line 39:15: Using target="_blank" without rel=“noreferrer” is a security risk: see HTML Standard react/jsx-no-target-blank
8:32:12 PM: Line 50:15: Using target="_blank" without rel=“noreferrer” is a security risk: see HTML Standard react/jsx-no-target-blank
8:32:12 PM: Line 64:11: Using target="_blank" without rel=“noreferrer” is a security risk: see HTML Standard react/jsx-no-target-blank
8:32:12 PM: src/components/Projects/SingleProject.js
8:32:12 PM: Line 4:37: ‘technology’ is assigned a value but never used no-unused-vars
8:32:12 PM: Line 15:21: Using target="_blank" without rel=“noreferrer” is a security risk: see HTML Standard react/jsx-no-target-blank
8:32:12 PM: Line 16:21: Using target="_blank" without rel=“noreferrer” is a security risk: see HTML Standard react/jsx-no-target-blank
8:32:12 PM: src/components/Skills/Skills.js
8:32:12 PM: Line 29:13: Headings must have content and the content must be accessible by a screen reader jsx-a11y/heading-has-content
8:32:12 PM: src/index.js
8:32:12 PM: Line 7:3: ‘Switch’ is defined but never used no-unused-vars
8:32:12 PM: Line 8:3: ‘Route’ is defined but never used no-unused-vars
8:32:12 PM: Line 9:3: ‘Link’ is defined but never used no-unused-vars
8:32:12 PM: Line 10:3: ‘NavLink’ is defined but never used no-unused-vars
8:32:12 PM: Line 11:3: ‘useLocation’ is defined but never used no-unused-vars
8:32:12 PM: Search for the keywords to learn more about each warning.
8:32:12 PM: To ignore, add // eslint-disable-next-line to the line before.
8:32:12 PM: File sizes after gzip:
8:32:12 PM: 104.37 KB build/static/js/2.7f991264.chunk.js
8:32:12 PM: 8.98 KB build/static/js/main.2ee900d4.chunk.js
8:32:12 PM: 930 B build/static/css/main.fbb5c5b6.chunk.css
8:32:12 PM: 776 B build/static/js/runtime-main.5dfefed0.js
8:32:12 PM: The project was built assuming it is hosted at /.
8:32:12 PM: You can control this with the homepage field in your package.json.
8:32:12 PM: The build folder is ready to be deployed.
8:32:12 PM: You may serve it with a static server:
8:32:12 PM: npm install -g serve
8:32:12 PM: serve -s build
8:32:12 PM: Find out more about deployment here:
8:32:12 PM: Deployment | Create React App
8:32:12 PM: ​
8:32:12 PM: (build.command completed in 28s)
8:32:12 PM: ​
8:32:12 PM: ────────────────────────────────────────────────────────────────
8:32:12 PM: 2. Deploy site
8:32:12 PM: ────────────────────────────────────────────────────────────────
8:32:12 PM: ​
8:32:12 PM: Starting to deploy site from ‘my-portfolio/build’
8:32:12 PM: Creating deploy tree
8:32:12 PM: Creating deploy upload records
8:32:12 PM: 0 new files to upload
8:32:12 PM: 0 new functions to upload
8:32:12 PM: Site deploy was successfully initiated
8:32:12 PM: ​
8:32:12 PM: (Deploy site completed in 182ms)
8:32:12 PM: ​
8:32:12 PM: ────────────────────────────────────────────────────────────────
8:32:12 PM: Netlify Build Complete
8:32:12 PM: ────────────────────────────────────────────────────────────────
8:32:12 PM: ​
8:32:12 PM: (Netlify Build completed in 28.3s)
8:32:12 PM: Starting post processing
8:32:12 PM: Post processing - HTML
8:32:13 PM: Post processing - header rules
8:32:13 PM: Post processing - redirect rules
8:32:13 PM: Post processing done
8:32:13 PM: Caching artifacts
8:32:13 PM: Started saving node modules
8:32:13 PM: Finished saving node modules
8:32:13 PM: Started saving build plugins
8:32:13 PM: Finished saving build plugins
8:32:13 PM: Started saving pip cache
8:32:13 PM: Site is live :sparkles:
8:32:13 PM: Finished saving pip cache
8:32:13 PM: Started saving emacs cask dependencies
8:32:13 PM: Finished saving emacs cask dependencies
8:32:13 PM: Started saving maven dependencies
8:32:13 PM: Finished saving maven dependencies
8:32:13 PM: Started saving boot dependencies
8:32:13 PM: Finished saving boot dependencies
8:32:13 PM: Started saving rust rustup cache
8:32:13 PM: Finished saving rust rustup cache
8:32:13 PM: Started saving go dependencies
8:32:13 PM: Finished saving go dependencies
8:32:16 PM: Build script success
8:32:48 PM: Finished processing build request in 2m9.024713424s

Now we can close the subject.
But before that, I would like to point out, that Netlify never caused so many heart-attack problems as before. The frustration of finding the mistake or if there is no mistake where to find your solution need to take care. I will not say that I am satisfied with the Netlify platform. I am satisfied with the site of helping by the community developers but the platform itself needs to be evaluated more than ever.
Thank you all in advance for your kind help and guide direction.
Unfortunately, we either we don’t know how it works and if sometimes we are making difficult questions please be patient with us.

Yours sincerely
DocMustang