nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

node.js build fails if warnings present

varnav

Hello!

I have following configuration for pipeline:

image: node:latest

pipelines:
  default:
    - step:
        script: # Modify the commands below to build your repository.
          - npm install
          - npm run build

Build fails if any warnings present.

Creating an optimized production build...
Failed to compile. When process.env.CI = true, warnings are treated as failures. Most CI servers set this automatically.

How to handle this?

Accepted answers

All comments

Ana Retamal

Hi Varnav, the build is failing as warnings are being treated as errors due to a certain environment variable being set/not set. In this case, it looks from your error message like the affected variable is 'process.env.CI' (which is now set to true). You may need to set that to false in order to allow compiling to pass even in the face of warnings being raised.

Let us know if this solved your issue!

Cheers,

Ana

varnav

Setting CI to false does not help, but unsetting it does help. But, unfortunately, this also supresses all warnings.

Looks like this is a create-react-app issue.

Shikha Chugh

I am having a very tough time setting CI to false. Where do I do it from? I tried doing from Repo's environment variables , yet during my build run it is set as True.

I also tried doing it from the global settings at my team level or user level. Yet to no avail!

How do I set environment variable CI to false?

Shikha Chugh

@varnav did you end up figuring out what the create-react-app issue was?

I am having the same issue during building, I wonder what solution you end up finding?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-pipelines

node.js