npm stuck in endless loop when running Ionic cordova run android --livereload
See original GitHub issueI think one day this whole npm mess will collapse under its weight
Now I am unable to run the app in livereload mode.
command: ionic cordova run android --livereload
Ionic info:
Ionic CLI : 5.4.2 (C:\Users\Jasko\AppData\Roaming\nvm\v10.15.3\node_modules\ionic)
Ionic Framework : ionic-angular 3.9.3
@ionic/app-scripts : 3.2.4
Cordova:
Cordova CLI : 9.0.0 (cordova-lib@9.0.1)
Cordova Platforms : android 8.1.0, browser 6.0.0
Cordova Plugins : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 1.2.1, (and 25 other plugins)
Utility:
cordova-res : 0.6.0 (update available: 0.8.0)
native-run : 0.2.8
System:
Android SDK Tools : 26.1.1 (e:\Android\SDK)
NodeJS : v10.15.3 (C:\Program Files\nodejs\node.exe)
npm : 6.4.1
OS : Windows 10
Output:
> ionic cordova run android --address 192.168.0.11 --device -l --ssl --debug
> npm.cmd run ionic:serve -- --address 192.168.0.11 --port 8101 --livereload-port 35730 --dev-logger-port 53704 --nobrowser --iscordovaserve --platform android --target cordova
[npm] > Real.Me@1.0.1 ionic:serve e:\Projects\xxx\src
[npm] > ionic serve -l --no-open "--address" "192.168.0.11" "--port" "8101" "--livereload-port" "35730" "--dev-logger-port" "53704" "--nobrowser" "--iscordovaserve" "--platform" "android" "--target" "cordova"
[npm] [WARN] The --nobrowser option has been deprecated. Please use --no-open.
[npm] > npm.cmd run ionic:serve -- --address 192.168.0.11 --port 8101 --livereload-port 35730 --dev-logger-port 53704 --nobrowser --platform android
[INFO] Waiting for connectivity with npm...
[npm] [npm] > Real.Me@1.0.1 ionic:serve e:\Projects\xxx\src
[npm] [npm] > ionic serve -l --no-open "--address" "192.168.0.11" "--port" "8101" "--livereload-port" "35730" "--dev-logger-port" "53704" "--nobrowser" "--platform" "android"
[npm] [npm] [WARN] The --nobrowser option has been deprecated. Please use --no-open.
[INFO] Waiting for connectivity with npm...
[npm] [npm] > npm.cmd run ionic:serve -- --address 192.168.0.11 --port 8101 --livereload-port 35730 --dev-logger-port 53704 --nobrowser --platform android
[npm] [INFO] Waiting for connectivity with npm...
Terminate batch job (Y/N)? [npm] Terminate batch job (Y/N)?
What the hell is going on here ??
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Endless loop when running Ionic cordova run android
It seems like an issue either with the project configuration or the global npm. Try the same command in some other ionic applications....
Read more >Ionic cordova build Get Stuck at "Generating ES5 bundles for ...
When I was building my ionic app via “ionic cordova run android --device --verbose”, it got stuck at … > ng.cmd run app:ionic-cordova-build ......
Read more >ionic live reload android Code Example - Code Grepper
Go to voice: resets all view cache: so data is reloaded with currently language. 2. window.location.assign('/');. Source: forum.ionicframework.com.
Read more >The 9 Most Common Mistakes That Ionic Developers Make
Common Mistake #6: Trying to Run Cordova Plugins Inside the Browser. The majority of developers using Ionic will want their app to run...
Read more >I am really stuck with white screen after load on Android API ...
I've created two blank projects, 1 with capacitor and one with Cordova and they both have the same result. I've googled this solidly...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Your npm scripts suggest you have overridden the build/serve. See the docs.
Unless you absolutely need them, I would recommend removing the
ionic:serve
andionic:build
scripts in yourpackage.json
.issue solved. now you can close it