Use exec, not spawn, to kill Chrome process on Windows (#1206)

Using `childProcess.spawnSync` fails on Windows. `childProcess.execSync` works fine.
GoogleChrome · Dec 22, 2016 · 1513a1d · 1513a1d
1 parent 0b5f5bb
commit 1513a1d
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/lighthouse-cli/chrome-launcher.ts b/lighthouse-cli/chrome-launcher.ts
@@ -29,7 +29,6 @@ const rimraf = require('rimraf');
 const log = require('../lighthouse-core/lib/log');
 const spawn = childProcess.spawn;
 const execSync = childProcess.execSync;
-const spawnSync = childProcess.spawnSync;
 
 class ChromeLauncher {
   prepared: Boolean = false
@@ -215,7 +214,7 @@ class ChromeLauncher {
 
         log.log('ChromeLauncher', 'Killing all Chrome Instances');
         if (process.platform === 'win32') {
-          spawnSync(`taskkill /pid ${this.chrome.pid} /T /F`);
+          execSync(`taskkill /pid ${this.chrome.pid} /T /F`);
         } else {
           process.kill(-this.chrome.pid);
         }