I have tried starting a project from the "Blank Node.js Console Application" and "Blank Node.js Web Application" projects. When I place a breakpoint and then press F5, the application is executed, but no breakpoints are ever hit. Intellisense is working fine. I am using VS Ultimate 2013 Update 4.
Comments: This is Node breaking debuggers again... https://github.com/node-inspector/node-inspector/issues/534 Basically, we start it with `--debug-brk` and assume that it'll wait for us to signal it to go ahead once we're ready (after doing all the things like, say, binding breakpoints). But as of v0.12, it doesn't wait anymore, and so breakpoints are bound asynchronously as the code is running. It doesn't look like there's anything we can do here other than document it and hope that it gets fixed. By the way, io.js does not have this problem.
Comments: This is Node breaking debuggers again... https://github.com/node-inspector/node-inspector/issues/534 Basically, we start it with `--debug-brk` and assume that it'll wait for us to signal it to go ahead once we're ready (after doing all the things like, say, binding breakpoints). But as of v0.12, it doesn't wait anymore, and so breakpoints are bound asynchronously as the code is running. It doesn't look like there's anything we can do here other than document it and hope that it gets fixed. By the way, io.js does not have this problem.