npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

spawn-watch

v0.1.2

Published

Simple node spawn process helper for creation, deletion and monitoring

Downloads

7

Readme

npm version

spawn-watch

Simple spawn process helper for creation & monitoring

Install

npm install spawn-watch

Usage

const SpawnWatch = require('spawn-watch');

initOptions = {
    ipc:true,
    encodings:{
        stdin:'ascii',
        stdout:'utf-8',
        stderr:'ascii'
    }
};

config = {
    command: 'node',    //command to run (required)
    args: ['-v'],       //List of string arguments (require at least [])
    options: {}         //List of options (require at least {})
};

//init (options are not required)
let spawnWatch = new SpawnWatch(initOptions);

//subscribe to error observable
spawnWatch.errorStream.subscribe(err => {
    console.log('got errors meeehhh', err);
});

//subscribe to stdout observable
spawnWatch.outEventStream.subscribe(data => {
    console.log('got data output', data);
});

//subscribe to spawn-watch status updates observable
spawnWatch.processEventStream.subscribe(status => {
    console.log('got status', status);
});

//subscribe to spawn-watch IPC observable
spawnWatch.ipcStream.subscribe(msg => {
    console.log('got IPC msg', msg);
});

//spawn process
spawnWatch.start(config);

methods

Ease handling of spawned child processes with simple interface.

  • spawnWatch.start(config) - spawn a process with the given configuration
  • spawnWatch.stop() - exit a process (and sub processes)
  • spawnWatch.restart([config]) - exit some previously started process and spawn a new one afterwards. config is optional, if not provided the process will restart with the same config as the previous process.

outputs

stdout, stderr are piped to spawn-watch observables RXJS so you can subscribe even before any process is spawned. That way there is no need to micro-manage listeners.

  • spawnWatch.outEventStream.subscribe(function(){}) - stdout data is piped to this observable
  • spawnWatch.errorStream.subscribe(function(){}) - stderr & process.on('error') are piped to this observable
  • spawnWatch.ipcStream.subscribe(function(){}) - receive process.send() data from the child process in this observable (need an IPC channel to emit something).

inputs

  • spawnWatch.input(data) function that handle writing to stdin for you. Sending strings or JSON to the spawned process
  • spawnWatch.ipcInput(data) function that use an IPC channel to send data from parent to child process. Will return false if no IPC channel is set.

other

You can get the state of the spawned process at any given moment, subscribe to the process state stream, or retrieve the config that was applied to spawn this process.

  • spawnWatch.processEventStream.subscribe(function(){}) - observable emitting the status changes over time [stopped, started, pending start, pending stop]
  • spawnWatch.processStatus - status property
  • spawnWatch.currentConfig - get config of current process

constructor options

Here are the option object properties you can pass to the SpawnWatch constructor

property | type | default value | comment ------------ | ------------- | ------------- | ------------- ipc | [boolean] | false | enables an ipc channel between parent and child process. Alternatively you can define it with the options.stdio property at the child process config level. encodings.stdin | [string] | 'utf-8' | encoding of the process stream. See node doc for supported encodings. encodings.stdout | [string] | 'utf-8' | encoding of the process stream. See node doc for supported encodings. encodings.stderr | [string] | 'utf-8' | encoding of the process stream. See node doc for supported encodings.