
There couldn't be so many bugs specific to each platform! I was wrong. And for the platform specific bugs, I would just have to debug my Android apps with the chrome dev tools and iOS apps with the Safari dev tools. Yeah, you're a javascript developer, you know what I'm talking about :). You know, these console.log() you forget in your code after fixing your bug and that haunts your debug console for days, because you're too lazy to remove them. At first, I thought that just serving the app and having live reload on the browser would be enough to be able to find and fix easily all the bugs just by using console.log(). And the biggest one of all was: Debugging. It was awesome!īut, as for many early technologies, there were caveats. Suddenly I could create mobile apps working on iOS AND Android just with my web developer knowledge. Ionic 1 was a real revolution for me as a frontend developer. Once upon a time, debugging Ionic apps was taking way too much time. Also, it's free and has a huge community making it better and better every day. If you haven't tried it, it's a really lightweight IDE and has pretty much all the features you need to develop mobile applications using Ionic 3. I'll also assume that you have already installed Visual Studio Code. If you haven't done that yet, I invite you to learn all that on the Ionic website.


I'll consider you have already been playing around with Ionic 3 and managed to make it run it on a device or emulator. Putting breakpoints directly in VS Code to pause your app running directly on a device or emulator.Live reload the running app each time you make changes to your code without having to build it all over again.In this article, I will show you how to setup your development environment using VS Code to be able to debug correctly your Ionic app running on iOS or Android. Tools, tutorials, cordova, mobile, app, ionic, vscode, debug Live debug your Cordova/Ionic application with Visual Studio Code
