Debugger not running?

[saadq]

I'm having issues getting the debugger to run. Breakpoints are working, but trying to do Start Resume or Start Active File doesn't seem to run the file. Steps to reproduce my issue:

1. Open a JS file.
2. Start the debugger with Ctrl+F5
3. Add a breakpoint with F9
4. Run the debugger with F5 or with the Play button on the top right.

When I do the last step, all that happens is this in the console:

Connection attempt 1 to node process on 127.0.0.1:5858 failed. Will try again in 500.
(node:11975) [DEP0062] DeprecationWarning: `node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead.

I am on macOS Sierra Version 10.12.2. Any help would be appreciated.

[Redsandro]

Possibly related to https://github.com/kiddkai/atom-node-debugger/issues/234 and https://github.com/kiddkai/atom-node-debugger/issues/237

Try explicitly setting the path, e.g. --inspect=5858. Not sure you'll get it to work though. I can only inspect variables on node 4, not on node 6+.

[robertwbradford]

@saadq Did you ever find a fix?

[saadq]

Unfortunately no, I've just been debugging node with Chrome lately. One thing you may want to try instead is xatom-debug + xatom-debug-nodejs as an alternative, I remember it working for me when I tried.

[guerillagorilla]

I had this same issue, but after manually setting the Node Path (/usr/local/bin/node), I can now use the debugger.

[robertwbradford]

@guerillagorilla Thanks, that did the trick for me too.

[doublejosh]

This allows node to run and actually start the app, but the connection is still never made to the debugger so no data ever comes back in the panel ;(

[dhowe]

Any fix for this?

[scholtes1953]

It looks to me like this code relies on the deprecated (since node 7.7) internal _debugger.js. The new approach is to use the node inspector.