Debugging a Meteor Application Using NTVS (Node Tools for Visual Studio)

Question

I am studying using NTVS ( https://nodejstools.codeplex.com/ ) with Visual Studio 2013 to debug my Meteor / Node application. I can’t figure out how to debug work.

The problem is that when you start Meteor copies all my sources to the .local directory and launches them in a new instance of Node.exe. This confuses NTVS because it cannot follow the child process. And I cannot set breakpoints because Visual Studio does not know how to deal with the fact that the files that I edit are different from those that work in the .local directory.

I would like some way to run my Meteor code under Node.exe directly from my sources without pre-build steps. Is it possible?

I am glad that I do not have the intricacies of development, such as push-push and package updates on the fly. I can manage it differently.

The 'meteor bundle' does not do the trick because (a) it takes too much time and (b) it still makes a copy that throws breakpoints.

Hopefully there is a way to use Meteor as a terrific library separate from Meteor as a runtime, so I can debug it using NTVS.

Thanks,

/ Michael Ost

Answer 1

if the functionality of meteor tools for Visual Studio is insufficient, why not contribute to the project.

It's a bit old (the last fixer 18 months ago) and therefore probably outdated, but it will give you a start on how to make things work.

Answer 2

You can run the application in debug mode using meteor debug , and then attach the debugger to the port number 5858, it should work for all types of node.js debuggers, for example. Visual Studio, Visual Code, Webstorm, etc., because they all have the "attach" option of the debugger next to the "debug" option.