After updating to 1.4.1, node inspector (v0.12.8) has been even flakier than usual for us, and the guide unfortunately lacks in this area.
- To start, which one of these is ‘the most correct’? The first one has always worked for us, but the 1.4 migration guide briefly mentions removing
--debug-brk, while other sources use the third.
meteor debug NODE_OPTIONS='--debug-brk' meteor env NODE_OPTIONS='--debug' meteor
What does the guide mean by you can now debug without using the --debug-brk option?. Without that flag, how does node-inspector know to start up / listen?
Node inspector no longer pauses at the first line of the process, is this expected behavior?
What URL do I go to for the debugging interface? It’s telling me to use 5858 & 5959 simultaneously after
To debug the server process using a graphical debugging interface, visit this URL in your web browser: http://localhost:8080/?port=5858 If your application is paused on a breakpoint but the code is not visible in the debugger, press the pause (||) button. Debugger listening on port 5959