Support use of node-inspector with --debug #13

Closed
darvelo opened this Issue May 6, 2013 · 4 comments

Comments

Projects
None yet
3 participants
@darvelo

darvelo commented May 6, 2013

If node is run with the --debug flag it'll allow a remote debugger like node-inspector to work (in this case with WebKit Inspector). I'm not sure if this is currently supported.. I see something about debug-brk in the Readme but I'm unclear as to if it's related. I tried using forever-monitor options with:

monitor: {
  options: ['--debug'],
}

..but no joy. Not sure if I'm just doing something wrong or if it's not possible. Advice is appreciated. Thanks. :)

@blai

This comment has been minimized.

Show comment Hide comment
@blai

blai May 6, 2013

Owner

if you put your grunt-express setting like following, you can debug from a remote debugger that is listening to port 5858

grunt.initConfig({
  express: {
    server: {
      options: {
        ...
        'debug-brk': 5858
      }
    }
  }
});
Owner

blai commented May 6, 2013

if you put your grunt-express setting like following, you can debug from a remote debugger that is listening to port 5858

grunt.initConfig({
  express: {
    server: {
      options: {
        ...
        'debug-brk': 5858
      }
    }
  }
});
@darvelo

This comment has been minimized.

Show comment Hide comment
@darvelo

darvelo May 6, 2013

Thank you, kind sir.

darvelo commented May 6, 2013

Thank you, kind sir.

@darvelo darvelo closed this May 6, 2013

@benjaminkitt

This comment has been minimized.

Show comment Hide comment
@benjaminkitt

benjaminkitt Nov 6, 2013

Is this option still available? It isn't working for me...

Is this option still available? It isn't working for me...

@blai

This comment has been minimized.

Show comment Hide comment
@blai

blai Dec 5, 2013

Owner

No, since 1.0 grunt-express uses grunt-contrib-watch to manage the server (and its start/stop), so you no longer need to use something like debug-brk, you simply set the spawn to false (so the server is run in the same process of the grunt itself) and your breakpoint would work.

Owner

blai commented Dec 5, 2013

No, since 1.0 grunt-express uses grunt-contrib-watch to manage the server (and its start/stop), so you no longer need to use something like debug-brk, you simply set the spawn to false (so the server is run in the same process of the grunt itself) and your breakpoint would work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment