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

node-process

v1.0.1

Published

A simple utility to handle sub-processes and multi threading and tasking in a node driven application

Downloads

4,841

Readme

Build Status

Node Process

Milti threading/tasking and background task helper module for nodejs.

Description

Read about the use and motivation behing this here: https://github.com/segsalerty2013/node-process/wiki

Installation

$ npm install node-process;

Usage

//for one sub process/thread
let node_process = require('node_process');
node_process.fork('path_to_valid_module', ['array of arg required by module'], true)
.then((response)=>{
    //response is string|object sent from the module back to the main thread
    //such response will be sent with process.send('string|object');
    console.log(response);
})
.catch((error)=>{
    //error occurred.
    console.log(error);
});

//for a sticky process/thread that never ends until main thread is dead
node_process.fork('path_to_valid_module', ['array of arg required by module'], false)
.then((response)=>{
    //response is string|object sent from the module back to the main thread
    //such response will be sent with process.send('string|object', 'Handler' ()=>{}, {keepOpen:true});
    //note the Handler i.e Empty ()=>{}
    //and the {keepOpen:true} options
    console.log(response);
})
.catch((error)=>{
    //error occurred.
    console.log(error);
});

Submit an issue, feedback or a feature request

  • Any issue topics are welcome.

CONTRIBUTING

  • Fork it!
  • Clone your fork
  • Create your feature branch: git checkout -b my-new-feature;
  • Add a test for each new code
  • Add add your new code
  • Run the tests: npm test;
  • Commit your changes: git commit -am 'Add some feature/fix';
  • Push to the branch: git push origin my-new-feature;
  • Submit a pull request: