Nativescript-cli: Livesync with --bundle never stops

[NickIliev]

The issue is inconsistent and happens sometimes on Mac with next CLI.

Using CLI 4.2.0-2018-05-28-11682
on Mac OS High Sierra
with next modules and runtimes

When I trigger the following command

tns run android --bundle

The webpack watch seems to work even after I kill the process with Ctrl + C.
Notice that the webpack watch is not stopped even after some git commands were executed.

Webpack compilation complete. Watching for file changes.
File change detected. Starting incremental webpack compilation...

niliev@mcsofniliev ~/D/g/nativescript-marketplace-demo> git pull
Updating 93de41e..8ec54bd
Fast-forward
 app/bundle-config.ts                  | 40 ----------------------------------------
 app/common/linear-gradient.android.ts | 24 ++++++++++++------------
 app/common/linear-gradient.ios.ts     | 24 ++++++++++++------------
 app/vendor-platform.android.ts        |  9 ---------
 app/vendor-platform.ios.ts            |  3 ---
 app/vendor.ts                         | 10 ----------
 webpack.config.js                     |  3 ++-
 7 files changed, 26 insertions(+), 87 deletions(-)
 delete mode 100644 app/vendor-platform.android.ts
 delete mode 100644 app/vendor-platform.ios.ts
 delete mode 100644 app/vendor.ts
niliev@mcsofniliev ~/D/g/nativescript-marketplace-demo> git branch
  master
* niliev/next
  niliev/next-new
  niliev/update
niliev@mcsofniliev ~/D/g/nativescript-marketplace-demo>
[at-loader] Checking started in a separate process...

[at-loader] Ok, 0.312 sec.
Hash: 0be069450e3eba2d7b33
Version: webpack 3.10.0
Time: 19245ms
    Asset     Size  Chunks                    Chunk Names
bundle.js  1.01 MB       0  [emitted]  [big]  bundle
vendor.js   647 kB       1  [emitted]  [big]  vendor
 [148] ./app.ts 2.1 kB {0} [built]
 [149] ./bundle-config.ts 5.43 kB {0} [built]
 [183] . (root|page|fragment|common)\.(xml|css|js|ts|scss|less|sass)$ 3.81 kB {0} [built]
 [209] ./examples/conference-agenda/conference-agenda-page.css 1.89 kB {0} [optional] [built]
 [397] ./views/code-page.ts 1.07 kB {0} [optional] [built]
 [399] ./views/example-info-page-common.css 258 bytes {0} [optional] [built]
 [400] ./views/example-info-page.css 778 bytes {0} [optional] [built]
 [410] ./views/group-page/group-page.xml 1.5 kB {0} [optional] [built]
 [411] ./views/main-page/featured-examples-common.css 320 bytes {0} [optional] [built]
 [416] ./views/what-is-new-common.css 784 bytes {0} [optional] [built]
 [417] ./views/what-is-new-page.css 522 bytes {0} [optional] [built]
 [437] ./vendor.ts 344 bytes {1} [built]
 [438] . nonrecursive ^\.\/app\.(css|scss|less|sass)$ 174 bytes {1} [built]
 [439] ./app.css 1.09 kB {1} [optional] [built]
 [441] ./vendor-platform.ts 198 bytes {1} [built]
    + 439 hidden modules
Webpack compilation complete. Watching for file changes.
File change detected. Starting incremental webpack compilation...

[at-loader] Checking started in a separate process...

[at-loader] Ok, 0.267 sec.
Hash: e221dd16f9ae6b652411
Version: webpack 3.10.0

[Fatme]

It seems like a leaked node process. Maybe killall -9 node command will fix the problem.