Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

409 Errors

See original GitHub issue

When setting the CI flag to true, webpack treats warnings as errors. So even if we set suppressConflictError to true, it still reports a warning, which is then treated as an error. I see a couple options:

allow a “overwriteExistingArtifcats” flag, or similar
Do not warn or error on the conflict error if the suppressConflictError flag is set to true

Any thoughts?

Issue Analytics

State:
Created 6 years ago
Comments:6

Top GitHub Comments

1reaction

rhys-vdwcommented, Oct 13, 2017

Check out facebookincubator/create-react-app#1150

0reactions

kjanoudicommented, Dec 5, 2017

i removed this from my scripts/build.js

if (
        process.env.CI &&
        (typeof process.env.CI !== 'string' ||
          process.env.CI.toLowerCase() !== 'false') &&
        messages.warnings.length
      ) {
        console.log(
          chalk.yellow(
            '\nTreating warnings as errors because process.env.CI = true.\n' +
              'Most CI servers set it automatically.\n'
          )
        );
        return reject(new Error(messages.warnings.join('\n\n')));
      }

@Grsmto