fix(@ngtools/webpack): use process.once instead of process.on

angular · Oct 18, 2017 · c410ba9 · c410ba9
1 parent 77a6cc8
commit c410ba9
Showing 1 changed file with 3 additions and 4 deletions.
diff --git a/packages/@ngtools/webpack/src/angular_compiler_plugin.ts b/packages/@ngtools/webpack/src/angular_compiler_plugin.ts
@@ -458,7 +458,6 @@ export class AngularCompilerPlugin implements Tapable {
       ? './type_checker_bootstrap.js'
       : './type_checker.js';
 
-
     let hasMemoryFlag = false;
     const memoryFlagRegex = /--max-old-space-size/;
     const debugArgRegex = /--inspect(?:-brk|-port)?|--debug(?:-brk|-port)/;
@@ -490,9 +489,9 @@ export class AngularCompilerPlugin implements Tapable {
       treeKill(this._typeCheckerProcess.pid, 'SIGTERM');
       process.exit();
     };
-    process.on('exit', killTypeCheckerProcess);
-    process.on('SIGINT', killTypeCheckerProcess);
-    process.on('uncaughtException', killTypeCheckerProcess);
+    process.once('exit', killTypeCheckerProcess);
+    process.once('SIGINT', killTypeCheckerProcess);
+    process.once('uncaughtException', killTypeCheckerProcess);
   }
 
   private _updateForkedTypeChecker(changedTsFiles: string[]) {