🚀 Socket Launch Week 🚀 Day 2: Introducing Repository Labels and Security Policies.Learn More
Socket
Sign inDemoInstall
Socket

did_it_work

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

did_it_work

A simple process launcher that determines whether the process succeeded or failed.

0.0.6
latest
npm
Version published
Weekly downloads
6.3K
17.16%
Maintainers
1
Weekly downloads
 
Created
Source

Did It Work?

Did it Work?: A simple process launcher that determines whether the process succeeded or failed.

Install

npm install did_it_work

Usage

var process = require('did_it_work');

process('my_awesome_program')
  .goodIfMatches(/Ready/, 1000)
  .badIfMatches(/Error/)
  .good(function(){
    console.log('The program worked (because it spat out "Ready" to stdout within 1000ms).')
  })
  .bad(function(){
    console.log('The program didn\'t work (because it spat out "Error" to stdout, or the program exited with non-zero code, or it didn\'t spit out "Ready" within 1000ms)')
  })
  .complete(function(){
    console.log('In any case, the program exited')
  })

Use spawn instead of exec

If you pass one string argument to the function, it will use child_process.exec to create the process. If, on the other hand, you need to use child_process.spawn, pass two arguments instead, the first being the executable and the second being an array of arguments. Example

process('echo', ['hello', 'world'])
  .complete(function(stdout){
    console.log('The program returned ' + stdout)
  })

RTFT

To see more, read the tests in tests.js.

FAQs

Package last updated on 20 Jun 2013

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts