From e1f7facefd2ced471e813d72ca5b1c21ed528d86 Mon Sep 17 00:00:00 2001
From: Joe Gibbs Politz <joe.politz@gmail.com>
Date: Fri, 20 Sep 2019 14:34:30 -0700
Subject: [PATCH] Set CI to false to continue deploying when we see certain
 webpack warnings

Right now we see: Critical dependency: the request of a dependency is an expression

I've tracked it somewhat to the need to do a big update in Stopify from
babel-core to @babel/core. That's going to be an undertaking, so allowing the
build to finish with these warnings and still deploy.
---
 .travis.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/.travis.yml b/.travis.yml
index 069dbe60b8..8bc1766262 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -29,7 +29,9 @@ after_failure:
 before_deploy:
 - cd ide
 - npm install
-- npm run build
+- echo "NOTE(joe): CI=false below avoids stopping the build on warnings from webpack about require() targets"
+- echo "NOTE(joe): We want to see them, but not be blocked on them"
+- CI=false npm run build
 deploy:
   provider: s3
   access_key_id: "AKIAUCA3RRQKLUSZTBS5"