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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@longlost/worker

v6.0.0

Published

promise based web worker implementation that handles calls to db and batches image processing and uploading

Readme

worker

runner.js

This utility handles running multiple Web Worker instances.

Concurrence

Under the hood, it spreads work out in parallel, accross as many logical processors as the workload demands, up to the maximum number allowed by the browser, determined by navigator.hardwareConcurrency. When the workload becomes greater than the available number of concurrent processes, the runner enqueues incomming jobs, matching them with recycled workers or recently vacated cores as soon as they become available. Concurrence is the default behavior, but can be defeated by setting options.concurrence to false, when calling the factory function.

Performance vs. Battery Life

Worker instances are allowed to remain idle for a short period before being automatically terminated. This is an attempt to lower the performance hit accrued by initializing new Worker instances. The default idle period of 2000ms can be changed by setting options.idle, when creating a new runner instance.

Simple Example

Since runner.js uses the incredible Comlink library to simplify Web Worker i/o, you will need to import it into each of your worker files and include each function that you wish to call from the main thread in its expose method.

npm install --save comlink @longlost/worker

or

yarn add comlink @longlost/worker

// Web Worker thread.
// my-cool-worker.js

import * as Comlink from 'comlink';


const myCoolFunction1 = (a, b, c) => {
	// ...some long running task.
};

const myCoolFunction2 = (a, b) => {
	// ...some long running task.
};


Comlink.expose({myCoolFunction1, myCoolFunction2});



// Main thread.
// app.js

import runner 	     from '@longlost/worker/runner.js';
import coolWorker    from './my-cool-worker.js';
import awesomeWorker from './my-awesome-worker.js';


(async function() {

	// These tasks will run in parallel, given the browser exposes more than one virtual core.
	const coolRunner = runner(coolWorker).run;

	// Optionally, force runner to run these tasks in series, with a one second idle time.
	const awesomeRunner = runner(awesomeWorker, {concurrence: false, idle: 1000}).run;


	const coolArgs1 = ['a', 'b', 'c'];

	const myCoolAndAwesomeResults = await Promise.all([
		coolRunner('myCoolFunction1', ...coolArgs1),
		coolRunner('myCoolFunction2', 'foo', 'bar'),
		awesomeRunner('myAwesomeFunction1', {baz: 'baz', qux: 'qux'}),
		awesomeRunner('myAwesomeFunction2')
	];

}());