From 36057fb8990fe1a2864a4b6f18eeb45b3479359b Mon Sep 17 00:00:00 2001
From: Clark Du <duxin@cfilmcloud.com>
Date: Sat, 3 Jun 2017 16:04:37 +0800
Subject: [PATCH] Use yarn instead of npm in building

---
 .travis.yml  | 8 ++++----
 appveyor.yml | 5 +++--
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index c2a14e7f60..8f0c46e7fb 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -6,9 +6,9 @@ node_js:
 before_install:
   - if [[ `npm -v` != 3* ]]; then npm i -g npm@3; fi
 install:
-  - npm install
-  - npm run build
+  - yarn install
+  - yarn run build
 script:
-  - npm test
+  - yarn run test
 after_success:
-  - npm run coverage
+  - yarn run coverage
diff --git a/appveyor.yml b/appveyor.yml
index 5cf1f0ebc9..2dfd73a345 100644
--- a/appveyor.yml
+++ b/appveyor.yml
@@ -7,15 +7,16 @@ install:
   # Get the latest stable version of Node.js or io.js
   - ps: Install-Product node $env:nodejs_version
   # install modules
-  - npm install
+  - yarn install
 
 # Post-install test scripts.
 test_script:
   # Output useful info for debugging.
   - node --version
   - npm --version
+  - yarn --version
   # run tests
-  - npm test
+  - yarn run test
 
 # Don't actually build.
 build: off