Package Exports
- sb-exec
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (sb-exec) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Exec
Node's Process spawning APIs beautified
Installation
npm install --save sb-execAPI
type $OptionsAccepted = {
timeout?: number | Infinity, // In milliseconds
stream?: 'stdout' | 'stderr' | 'both',
env: Object,
stdin?: string | Buffer,
local?: {
directory: string,
prepend?: boolean
},
throwOnStderr?: boolean = true,
allowEmptyStderr?: boolean = false,
ignoreExitCode?: boolean
} // Also supports all options of child_process::spawn
type PromisedProcess = {
then(callback: Function): Promise
catch(callback: Function): Promise
kill(signal: number)
}
export function exec(filePath: string, parameters: array, options: $OptionsAccepted): PromisedProcess
export function execNode(filePath: string, parameters: array, options: $OptionsAccepted): PromisedProcessExplanation
Promise callbacks
thencallback is supposed to accept one of these results, depending onoptions.stream:stdoutandstderrwill result in a string, representing an stdout or stderr stream, respectively.bothwill result in an object of{stdout, stderr, exitCode}representing their respective streams and an exit code of a process.- If
options.streamis not provided it is assumed to bestdout, so a promise will result in a string representing an stdout stream.
options.local
options.local adds node executables in node_modules relative to
options.local.directory to PATH like in npm scripts.
options.local.prepend prioritizes local executables over ones already in PATH.
License
This project is licensed under the terms of MIT License, see the LICENSE file for more info