malept / cross-spawn-promise Goto Github PK

Pre-flight checklist

• I have read the contribution documentation for this project.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem description

As a user I require the ability to capture stderr instead of stdout. More generally I require the ability to provide my own callback to resolve the promise, using data from both stdout and stderr.

Similarly, I have a need to override the default rendering of the command within error objects, in addition to what value goes to the logger. Use cases here include redacting sensitive info as well as allowing the user to render in a way that is more visible and useful. The default rendering does not put quotation marks around arg array elements, as example, and I'd prefer to have those, as well as output to more than one line. My ideal implementation would be more like JSON.stringify(args, null, 2).

Proposed solution

The solution is in my fork, where I have added options for formatOutputCallback, stringifyCommandCallback, and returnStderr.

The changes should necessitate a minor version change bump.

I've updated the readme and tests. I'll need to rebase, but first I'm looking for any feedback.

Alternatives considered

n/a

Additional information

No response

Pre-flight checklist

• I have read the contribution documentation for this project.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem description

When a spawn is launched in background, i've no way to kill it from the parent level.
cross-spawn-promise original npm library was storing in the promise object the childProcess id to let it be doable

const promise crossSpawnPromise.spawn('xxxxxx');

promise.childProcess.kill()

Proposed solution

N/A

Alternatives considered

N/A

Additional information

No response