New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details
Socket
Book a DemoSign in
Socket

spawn-async

Package Overview
Dependencies
Maintainers
14
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

spawn-async - npm Package Compare versions

Comparing version
0.0.1
to
0.0.2
+8
-3
package.json
{
"name": "spawn-async",
"version": "0.0.1",
"version": "0.0.2",
"description": "spawn child processes asynchronously",

@@ -8,5 +8,10 @@ "main": "lib/spawn-async.js",

"type": "git",
"url": "git://github.com/davepacheco/node-spawn-async.git"
"url": "https://github.com/davepacheco/node-spawn-async.git"
},
"keywords": [ "spawn", "async", "fork", "exec" ],
"keywords": [
"spawn",
"async",
"fork",
"exec"
],
"license": "MIT",

@@ -13,0 +18,0 @@ "readmeFilename": "README.md",

@@ -24,2 +24,3 @@ # spawn-async: spawn child processes asynchronously

console.log(stdout);
worker.destroy();
}

@@ -73,7 +74,11 @@ });

`destroy()`: forcefully kills the worker process and causes pending `aspawn`
commands to fail. The behavior with respect to the corresponding child
processes is undefined, so you should only call this when you know there are no
outstanding commands, when you don't care about leaving orphaned child processes
around, or your system will automatically clean up such child processes.
commands to fail. The behavior with respect to the child processes that you've
already launched is undefined, so you should only call this when you know there
are no outstanding commands, when you don't care about leaving orphaned child
processes around, or your system will automatically clean up such child
processes.
The worker process sticks around (leaving your Node program running) until you
call `destroy()`.
### Events

@@ -80,0 +85,0 @@

Sorry, the diff of this file is not supported yet