Hi,
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!
/Michael
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!
/Michael