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

wrecker

v1.0.3

Published

An easy to use worker thread pool.

Downloads

38

Readme

wrecker

npm version Build Status codecov install size

Worker threads without the work!

Usage

First define a module that contains the jobs you want to run in worker threads. Export an object whose keys are job names and whose values are functions that take zero or one arguments. The functions can be async. For example:

jobs.js

module.exports = {
  five: function() {
    return 5;
  },
  nine: function() {
    return 9;
  },
  add: function(args) {
    return args.a + args.b;
  },
};

Now you can create a WorkerPool and use it to run these jobs in worker threads. For example, this prints 14:

const WorkerPool = require('wrecker');
const path = require('path');

const JOBS_MODULE_PATH = path.join(__dirname, 'jobs.js');

const pool = new WorkerPool(JOBS_MODULE_PATH);

async function start() {
  const a = await pool.doWork('five');
  const b = await pool.doWork('nine');
  const sum = await pool.doWork('add', { a, b });

  // Shut down the pool and terminate all worker threads.
  await pool.shutdown();

  return sum;
}

start().then(sum => console.log(sum));

API

const pool = new WorkerPool(jobsModulePath, options)

The WorkerPool constructor takes two arguments. The first is required, it's the path to your jobs module (where jobs are exported as shown above). The second is an optional options argument. Here is an example with all options specified:

const path = require('path');
const WorkerPool = require('wrecker');

const JOBS_MODULE_PATH = path.join(__dirname, 'jobs.js');
const options = {
  numWorkers: 5, // The number of worker threads to spawn. By default, this is the number of CPU cores in the system.
  debugLog: console.warn, // A function to log debug messages to (such as when your worker threads unexpectedly exit). By default, debug messages are not logged.
};

const pool = new WorkerPool(JOBS_MODULE_PATH, options);

pool.doWork(jobName, jobArgument)

Do work in a worker thread. The first argument is the string name of the job (which should be defined as a function in your jobs module) and the second is the argument that will be passed to that job. The jobArgument should be JSON serializable. doWork returns a promise that returns the result of the job. See the example under Usage above.

The work will be executed on the next available worker thread. If no worker thread is currently available, the job will be queued until a thread is available.

pool.shutdown()

Terminate all threads in the pool. After calling this, you will not be able to do any more work with this pool (doWork will throw an error). Any work in progress may be ended abruptly, mid-processing. shutdown() returns a promise that resolves when all threads are terminated.