Debugging in Meteor

Sep 17, 2014 at 9:09 PM

We are investigating the use of NTVS to run our Meteor/Node application. The IDE is great for working with Javascript, but we are stuck on the debugging side of things. I can't set any breakpoints in my Meteor app with NTVS and VS2013.

When Meteor starts under node.exe, it spawns a second copy of node.exe that it runs my application under. I guess this is how Meteor implements its hot-code updates, where it restarts node if you change a source file. My guess is that my problem is that NTVS and the VS debugger are not able to acknowledge breakpoints in that child version of node.

Has anyone worked around this issue? Maybe a way to get Meteor to skip starting the second copy of node? Or get NTVS to debug the child process (without something tricky like using "attach to process")?

Thanks for any tips!

Sep 18, 2014 at 2:11 AM
On NTVS side of things, this is basically another scenario that would be covered by implementing this feature:
Sep 18, 2014 at 9:29 PM
This is a limitation of Visual Studio in general, right? I'm not aware of built in support for being able to debug in to a child process.

I'm hoping to find a work around within Meteor too.

Sep 19, 2014 at 1:32 AM
For anyone who might be interested, I am now investigating debugging the code that Meteor bundles up instead of working around Meteor's application framework. Bundles run without Meteor, which is what I want.

I had to start my own MongoDB for it to connect to, but the debugger launches. Unfortunately VS2013 is crashing with an error 10054 when I run this way. More digging required!