Breaking ionic serve doesn't close the connection

Description:

Using ionic serve --port=8101 and then breaking it (CTRL+C) won’t close the connection.

Steps to Reproduce:

1. install latest ionic locally and globally

The Ionic CLI has an update available (3.20.0 => 4.0.1)! Would you like to install it? Yes
> npm i -g ionic@latest
✔ Running command - done!

[OK] Updated Ionic CLI to 4.0.1! 🎉

Please re-run your command.

Note: You can downgrade to your old version by running: npm i -g ionic@3.20.0

1. run ionic serve --port=8101
2. wait for it to finish building.
3. CTRL+C
4. run ionic serve --port=8101
5. you will see he started using port 8102 since 8101 is occuped
6. check ionic processes: ps -ef | grep ionic
7. You now have two entries from serve.

My ionic info:

Ionic:

   ionic (Ionic CLI)  : 4.0.1
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.1.10

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : ios 4.5.4

System:

   Android SDK Tools : 26.1.1
   ios-deploy        : 1.9.2
   ios-sim           : 6.1.2
   NodeJS            : v10.0.0 (/usr/local/Cellar/node/10.0.0/bin/node)
   npm               : 6.2.0
   OS                : macOS High Sierra
   Xcode             : Xcode 9.4.1 Build version 9F2000

Environment:

   ANDROID_HOME : /Users/gregorpapez/Library/Android/sdk

[adailtonribeiro]

@dwieeb I tested on my machine and it’s working for me too Thank you so much for that!

[w3-jostergaard]

Hey together, I know this issue is old, but I got the exact problem with ionic -v 5.4.16

For me, even when I use ionic cordova run android --device a node process keep staying alive, I noticed it when my CPU usage got very high from several instances of node.js.

I use Windows 10 Home Version (10.0.19042 Build 19042)

ionic info also freezes the cli with ionic info --verbose i get following output before it freezes:

ionic:lib Terminal info: { ci: false, shell: 'C:\\WINDOWS\\system32\\cmd.exe', tty: true, windows: true } +0ms

ionic:lib CLI global options: { _: [ 'info' ], help: null, h: null, verbose: true, quiet: null, interactive: true, color: true, confirm: null, json: null, project: null, '--': [] } +5ms

ionic:lib:project Project type from config: Ionic 2/3 (ionic-angular) +0ms

ionic:lib:project Project details: { configPath: 'C:\\dev\\angular_projects\\panthera-automotive-app\\ionic.config.json', errors: [], context: 'app', type: 'ionic-angular' } +1ms

ionic Context: { binPath: 'C:\\Users\\Jonas Ostergaard\\AppData\\Roaming\\npm\\node_modules\\ionic\\bin\\ionic', libPath: 'C:\\Users\\Jonas Ostergaard\\AppData\\Roaming\\npm\\node_modules\\ionic', execPath: 'C:\\dev\\angular_projects\\panthera-automotive-app', version: '5.4.16' } +0ms

ionic:lib:telemetry Sending telemetry for command: 'ionic info' [ '--verbose', '--interactive', '--color' ] +0ms

Does someone has an idea? Got the problem reintroduced in a newer version?