Using child_process fork without customized Argv breaks debugging

[rsxdalv]

nodejs/node#8495
Without proper handling, the CP simply receives the same arguments, and thus you get it to receive the same argv as node, hence you get it to try and listen on the same port for debugger/inspector. All in all, making gulp & gulp-spawn-mocha debugging infeasible if not impossible.

This plugin has built in support for istanbul and better error handling (not throwing up stderr dump every time a test case fails); however, is far less debugging friendly.

[rsxdalv]

Currently trying to use:
this._child = proc.fork(bin, args.concat(this._files), {cwd: cwd, env: env, execPath: execPath, silent: !!output, execArgv: []});

[rsxdalv]

It works in the sense that you can then

.pipe(mocha({
            "require": "./utils/mocha.js",
            "reporter": argv.reporter || undefined,
            "debug": argv["debug-mocha"] || false,
            "inspect": debug_brk ? argv["inspect-mocha"] || undefined : undefined,
            "debug-brk": debug_brk,
        }, null));

However, clunkiness ensues as you cannot actually pass the port as it is interpreted as a test file (I believe gulp-mocha handles this for the user), instead forcing you to pass the --inspect=port manually, I fear something like so:

.pipe(mocha({
            "require": "./utils/mocha.js",
            "reporter": argv.reporter || undefined,
            "debug": argv["debug-mocha"] || false,
            "inspect=9239": true,  // This will, unfortunately, be seen as test file
            "debug-brk": debug_brk,
        }, null));