Ionic-cli: Starting app-scripts server: --address 0.0.0.0 --port 8100 --livereload-port 35729 --dev-logger-port 53703 --nobrowser - Ctrl+C to cancel

[eai301]

cli packages: (C:UserseaiAppDataRoamingnpmnode_modules)

@ionic/cli-utils  : 1.19.0
ionic (Ionic CLI) : 3.19.0

global packages:

cordova (Cordova CLI) : 7.1.0

local packages:

@ionic/app-scripts : 3.1.2
Cordova Platforms  : none
Ionic Framework    : ionic-angular 3.9.2

System:

Node : v6.11.2
npm  : 5.5.1
OS   : Windows 10

Environment Variables:

ANDROID_HOME : not set

Misc:

backend : legacy

[imhoffd]

@eai301 Please fill out the issue template.

[Tulika12]

Starting app-scripts server: --address 0.0.0.0 --port 8100 --livereload-port
35729 --dev-logger-port 53703 --nobrowser - Ctrl+C to cancel
[14:59:45] watch started ...
[14:59:45] build dev started ...
[14:59:45] clean started ...
[14:59:45] clean finished in 5 ms
[14:59:45] copy started ...
[14:59:45] deeplinks started ...
[14:59:45] deeplinks finished in 22 ms
[14:59:45] transpile started ...
[14:59:50] transpile finished in 5.04 s
[14:59:50] preprocess started ...
[14:59:50] preprocess finished in 1 ms
[14:59:50] webpack started ...
[14:59:50] copy finished in 5.24 s
[14:59:58] webpack finished in 7.25 s
[14:59:58] sass started ...
[14:59:59] sass finished in 1.20 s
[14:59:59] postprocess started ...
[14:59:59] postprocess finished in 8 ms
[14:59:59] lint started ...
[14:59:59] build dev finished in 13.71 s
[14:59:59] watch ready in 13.80 s
[14:59:59] dev server running: http://localhost:8100/

[OK] Development server running!
Local: http://localhost:8100
External: http://192.168.1.4:8100
DevApp: testApp@8100 on Lwisl-PC
After ionic serve it was displaying this and not opening the application inside the browser

[amitdubey8888]

Try using following command!
npm run ionic:serve --verbose

[dineshkokare123]

thanks its help me.

[Sawee]

it worked for me. Thank

[vintots]

It work's for me . Thaks @dineshkokare123 !!! cheers!

[sonnet1414]

thanks a lot
it's work fine
But why this happen?

[LucaColombi]

in my case, another ionic serve instance was running