Enable debugging using node-inspector about volo

[jrburke]

for the 0.1 series, doing this should work:

node --debug-brk path/to/volo command

for 0.2:

node --debug-brk `which volo` command

That gets you into the volo code, but not right at the point the volofile executes. Need to figure out a way to make that nice. Maybe have a debugger statement right before the volofile call so that the code will just stop there, then you can step into what happens with the volofile.

[mstade]

I had to do something like this to get debugging to work:

node --debug-brk "`dirname "\`which volo\`"`/node_modules/volo/bin/volo"

Otherwise, node tries to run the shell script that executes volo. Could that shell script be changed to take care of --debug and --debug-brk?

[jrburke]

node seems to manage that transition and handling of the --debug* options. I'm not sure how to get around that. Similar to what you mention, the best I have been able to manage so far is:

node --debug-brk `which volo` command

[mstade]

That's what I tried at first, but unfortunately it doesn't work on windows. Oh well, it works with the atrocity I pasted above and I have an alias set up for it anyhow :)

[jrburke]

Ah, OK. Well at the very least I think we should document what magic invocation should be used for this, depending on the platform. How are you running that command on Windows? cygwin shell, powershell, basic command line? Want to be sure we give the right info when documented.

[mstade]

I'm running it under git-bash, which I guess uses msysgit. I haven't tried under cygwin, but I'd assume it's the same deal. Basically, the environment is essentially lost. A similar thing happens with volo create actually, when it's trying to run npm install. That I got around by patching volo (here) to use child_process.exec instead (I believe.)