Treating warnings as errors because process.env.CI = true. [Solved]

If you face the “Treating warnings as errors because process.env.CI = true.” issue no matter where this post will help you solve this issue, you just have to change your build script to solve this issue!

If your console looks like this, you are probably in the same situation as mine!

Treating warnings as errors because process.env.CI = true.
Most CI servers set it automatically. 
Failed to compile.

What is this error all about?

CI 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 instead of a local development environment.

How to fix “Treating warnings as errors because process.env.CI = true.”

In order to fix “Treating warnings as errors because process.env.CI = true.” This error simply means the CI environment variable is set to true. That is why warnings behave like errors. You just have to set the CI environment variable to false, that is all you need to do. You can do this by changing the environment variable directly in hosting or by changing the build command by adding CI=false.

Follow the below-listed steps to fix Treating warnings as errors because process.env.CI = true. Most CI servers set it automatically. error.

Fix “Treating warnings as errors because process.env.CI = true.” in Cloud environment

1. Open build setting

On Netlity it is, Project > Settings > Deploys > Build command

On Vercel it is, Project > Settings > Build & Development Settings

2. Change build command by adding CI=false at starting

CI=false npm run build
or
CI=false yarn build

3. Rebuild and re-deploy your application.

If you still have the issue please let me know in the comments below!

Fix “Treating warnings as errors because process.env.CI = true.” in Windows 11/10/8/7

1. Open your package.json
2. Change build command by adding set \”CI=false\” at starting

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

3. Rebuild and re-deploy your application.

That’s it! By following the steps above, you should be able to fix the “Treating warnings as errors because process.env.CI = true.” error. If you have any further questions or suggestions, feel free to leave them in the comments section below.