@ephraimt I found an issue in the webpack dev configuration. We are currently using eval-source-map to generate the source map, but it seems that it’s bugged (breakpoints can be added but the execution does not stop). Check the following issue in the official Webpack repository. To fix it and to be able to debug, open your /projectName/webpack.dev.config.js file and change devtool: 'eval-source-map', with devtool: 'inline-source-map', It will fix the issue (I made the screenshot with a Vue template, but React templates work as well):

Feel free to disregard this request. I just couldn’t wait any longer so I wrote an object explorer in order to be able to navigate the events returned on the mobile device as they are different than in the preview. If anyone wants the function - it is pretty basic, but gives you a collapsible view of objects like in dev tools - the code is here: https://github.com/munsterlander/Onsen-Examples/tree/master/Remote-Console-In-Debugger Just do note, I hacked this together from some old code posted on the net and modified it for my needs.

So I have the answer about working on Monaca / Onsen while you fly - seeing as that is what I am currently doing (btw, I swear they are making the seats narrower every month!). My first test was to just connect to in-flight wifi but not actually buy the wifi to see if it would communicate through the router as each device would obtain a valid IP address. While this should work in theory, I could not get past the first hurdle of LocalKit requiring you to login to Monaca.io. The same goes for the debugger. So, the short answer is, offline development / debugging is not possible using the Monaca tools. A major bummer as I was really hoping to just be able to use Atom with the inspector and the preview tool. On the plus side though, this forced me to buy the $39.99 in-flight internet so now I can write on the forums and share this experiment with you all! :stuck_out_tongue_closed_eyes: