You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'd be happy to contribute back to your docs if you can lend some tips. my program fires up at min 3 child_processes
node --debug index.js
--debug doesn't stop on my debuggers. node debug ... does, but not --debug
how do i attach via the cli (if even feasible) to other processes? that is, i clearly see my new child_processes come up with 5859, 5860, etc etc, but to my knowledge there's no node attach -p 5860 cmd. what's your strategy here?
thanks!
-chris
The text was updated successfully, but these errors were encountered:
I realize this is an old thread but thought you might want to check out this updated post: Debugging Node.js with Chrome DevTools. You can use Chrome DevTools to attach to node processes. The tricky part (for me at least) is figuring out how to make 3rd party modules that call spawn use child-process-debug instead (or otherwise get the --debug / --inspect flag passed to them).
hello:
i'd be happy to contribute back to your docs if you can lend some tips. my program fires up at min 3 child_processes
node --debug index.js
--debug
doesn't stop on mydebugger
s.node debug ...
does, but not--debug
node attach -p 5860
cmd. what's your strategy here?thanks!
-chris
The text was updated successfully, but these errors were encountered: