Stop Treating warnings as errors because process.env.CI = true.

Hello,

When running the react-scripts build on the CI, the build script does the following

Treating warnings as errors because process.env.CI = true.

This is due to this line of code.

I disagree with treating the CI differently during the build as it creates inconsistency between local environment and the CI. I pushed the code to github knowingly about the warnings, having the CI break from the warning I approved of pushing is rather unexpected to the user.

[Timer]

Hi! We’ve had a large discussion about this previously and decided that this is the best default behavior.

If you’d like to not use this behavior, simply set CI to false during your build command, e.g. CI=false npm run build.

[jfly]

What about the other direction? What if I’d like to treat warnings as errors locally? Am I supposed to manually set the CI environment variable?

I’d prefer the default is to always treat warnings as errors, regardless of the environment, and give people some way to opt out if they think they know what they’re doing (such as @Bamieh).