Treating warnings as errors because process.env.CI = true. Failed to compile

Question

I am working on a react-weather application for self learning purpose. Deployed the same in gh-pages.
URL
https://davisraimon.github.io/react-weather/
Repo
https://github.com/davisraimon/react-weather

When tried to integrate my application with Travis Ci, i got error as follows. It says like i have to change some env variable called Process.env.CI.

$ git clone --depth=50 --branch=master https://github.com/davisraimon/react-weather.git davisraimon/react-weather
nvm.install
4.18s$ nvm install stable
cache.1
Setting up build cache
cache.npm
$ node --version
v14.4.0
$ npm --version
6.14.5
$ nvm --version
0.35.3
install.npm
13.21s$ npm ci 
7.45s$ npm run build
> react-weather@0.1.0 build /home/travis/build/davisraimon/react-weather
> react-scripts build
Creating an optimized production build...
Treating warnings as errors because process.env.CI = true.
Most CI servers set it automatically.
Failed to compile.
./src/components/form.component.js
  Line 1:17:  'Component' is defined but never used  no-unused-vars
./src/App.js
  Line 2:8:    'logo' is defined but never used              no-unused-vars
  Line 8:7:    'API_key' is assigned a value but never used  no-unused-vars
  Line 37:5:   Expected a default case                       default-case
  Line 53:14:  Expected '===' and instead saw '=='           eqeqeq
  Line 69:20:  Expected '===' and instead saw '=='           eqeqeq
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-weather@0.1.0 build: `react-scripts build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the react-weather@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2020-06-30T17_45_07_887Z-debug.log
The command "npm run build" exited with 1.
cache.2
store build cache

I added env variable in .travis.yml file.

env:
    process.env.CI : false

Still its showing the same error.

Can anyone help me out of this situation please...

For future readers `process.env` is the node variable that contains all environment variables. In the `.travis.yml` file, you should just use the variable name, in this case `CI`, without the `process.env`. — Code-Apprentice, Mar 01 '23 at 18:17

score 84 · Answer 1 · answered Mar 15 '21 at 07:10

84

  "scripts": {
    "start": "react-scripts start",
    "build": "CI=false && react-scripts build",  // Add CI=False here
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },

answered Mar 15 '21 at 07:10

ENDEESA

3,373
2
21
17

Didnt work, pipeline complaining > CI=false && react-scripts build 'CI' is not recognized as an internal or external command, operable program or batch file. – hungryMind Jul 29 '22 at 09:14
@hungryMind was this on windows? – ENDEESA Sep 14 '22 at 01:11

score 30 · Answer 2 · answered Nov 06 '20 at 12:12

30

For me the solution was:

env: 
  CI: false

answered Nov 06 '20 at 12:12

Beegee Motus

303
3
5

3

Where to add this line? – Praveen M P Jun 01 '23 at 17:15

Francois Harmse · Answer 3 · 2022-02-24T09:13:10.140

if you have to continue with the build and deploy from within GitLab CICD pipelines, you can include CI=false like so:

CI=false npm run build

or

unset CI
npm run build

Here is a complete gitlab_ci job sample:

build-dev:
  environment: DEV
  image: node:16
  stage: build
  script:
    - npm install
    - CI=false npm run build
  only:
    - /^devrelease-.*$/
  tags:
    - docker

or

build-dev:
  environment: DEV
  image: node:16
  stage: build
  script:
    - unset CI
    - npm install
    - npm run build
  only:
    - /^devrelease-.*$/
  tags:
    - docker

score 10 · Answer 4 · answered Mar 02 '21 at 15:27

In my specific case, I was using Netlify, so all I did was set the ENV vars inside Netlify's panel:

Select Site Settings Tab
Select Build and Deploy
Scroll down to Environment variables and press Edit Variables
Fill it in with Key = CI and Value = false
Press save and trigger a new deploy

score 9 · Answer 5 · answered Jan 02 '21 at 18:49

9

For me replacing npm run build with CI='' npm run build worked.

answered Jan 02 '21 at 18:49

fight_club

327
4
13

score 2 · Answer 6 · edited Jul 17 '21 at 18:46

2

Follow the steps below and your problem would be solved:

Select Site Settings Tab
Select Build and Deploy
Scroll down to Environment variables choose Edit Variables
Fill it in with Key = CI and Value = false
Press clear cache and redeploy

...and have fun.

edited Jul 17 '21 at 18:46

Taslim Oseni

6,086
10
44
69

answered Jul 17 '21 at 10:53

Kenil Barvaliya

119
7

navinrangar · Answer 7 · 2022-09-22T19:41:51.567

2

This happens due to your CI server setting (in my case it is netlify).. Follow the steps below and your problem would be solved:

Select--> Site Settings Tab

Select--> Build and Deploy

Scroll down to Environment variables choose Edit Variables

Fill it in with Key = CI and Value = false

Press clear cache and redeploy

edited Sep 22 '22 at 19:41

answered Apr 20 '22 at 04:22

navinrangar

904
10
20

Thank you for this -- after bashing awhile in this situation w/ Netlify, I caught on that the `warnings` were failing the build completely, then finally studied the output a bit more closely and saw mention of the flag...which the error output was a bit more robust. Thanks so much for helping unblock me ;P – twknab Jun 12 '22 at 22:22

Radall · Answer 8 · 2023-06-02T07:51:45.203

2

Coming from hours of googling, for me the following worked for Azure Devops:

In your package.json

"scripts": {
  ...
  "build": "set \"CI=false\" && react-scripts build"
}

Note: The escaped quotes are important!

edited Jun 02 '23 at 07:51

answered Jul 27 '22 at 09:08

Radall

394
4
17

score 1 · Answer 9 · answered Aug 09 '21 at 11:46

CI=true is needed in case you would like to process test during the deployment but it can be easily archived by setting a flag via package.json (in case in your dockerfile already set ENV CI=true you can remove it)

 "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "CI=true react-scripts test"
  }

score 1 · Answer 10 · answered Aug 31 '22 at 06:09

1

In case you want to deploy to a windows server or using powershell, you can set the environment variables like this:

script:
  - $env:CI="false"
  - npm run build

or:

$env:CI="false"; npm run build

answered Aug 31 '22 at 06:09

borke

21
2

score 0 · Answer 11 · answered May 11 '21 at 23:13

0

In my case I was trying to deploy react app to Azure Static web pages via GitHub repo The env: CI: false

worked like a charm. Just a quick note. This was applied to the yaml defining the CI process in GitHub actions. The env element is with no indentation (at the same level as name: )

answered May 11 '21 at 23:13

ivlad

13
4

Could you pleas be more specific? Where in the yml file? – Ricardo Álvarez Aug 05 '22 at 01:49
Given all is set the same way at your side it should be located in your github repo under tab Actions -> Azure Static Web Apps CI/CD -> the link to the yaml is right under the title (Azure Static Web Apps CI/CD ) – ivlad Jan 10 '23 at 22:52

score 0 · Answer 12 · answered Dec 07 '21 at 04:30

0

In Gitlab CI job in yml file, adding below script in my job worked for me.

script:
- CI=false yarn run build

answered Dec 07 '21 at 04:30

Rajaram Shelar

7,537
24
66
107

score 0 · Answer 13 · answered Feb 01 '22 at 15:47

0

you must fix the warnings you have in react, that's why it doesn't let you deploy

answered Feb 01 '22 at 15:47

Melvin

73
5

score 0 · Answer 14 · answered Apr 12 '23 at 06:44

0

I'm using gitlab ci & yarn and this worked for me:

  script: 
    - CI=false yarn build

answered Apr 12 '23 at 06:44

Ranjeet Singh Bhati

1
2

score 0 · Answer 15 · edited Jun 06 '23 at 07:15

0

For me, I was deploying a ReactJs project and I faced the CI error. I added an environment variable to Netlify. Variable name added was: CI and it's value was given as: false

Netlify then ignored the errors and performed the build.

Netlify add environment variable option:

edited Jun 06 '23 at 07:15

Younes Charfaoui

1,059
3
10
20

answered Jun 05 '23 at 20:35

swbdecodes

1
1

Treating warnings as errors because process.env.CI = true. Failed to compile

15 Answers15

Linked