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

threadwork

v0.6.0

Published

Simple, no frills, threading in Node.js

Downloads

5

Readme

threadwork

Simple, no frills, threading in Node.js

Why

Other solutions were too complex. Many threading apps just need a way to create a thread pool and call the threaded function; that's what this does.

How

Most threading solutions stringify the function and arguments before passing them to a worker. Stringifying creates friction when using dependencies. threadwork skips stringifying the function by using a reference instead, reducing the effort to create a threaded function.

Example

// fibonacci.js
const { ThreadPool } = require('threadwork');

function fibonacci(n) {
	if (n < 2) return n;
	return fibonacci(n - 1) + fibonacci(n - 2);
}

module.exports = new ThreadPool({ task: fibonacci });
// index.js
const pool = require('./fibonacci');

(async () => {
	try {
		const results = await Promise.all([
			pool.run(10),
			pool.run(20),
			pool.run(30)
		]);
		console.log(results); // [55, 6765, 832040]
	} catch (e) {
		console.log(e);
	} finally {
		await pool.close();
	}
})();

API

  • new ThreadPool({ task, size }) - The primary class. It should be instantiated at the top-level and only once per file.

    • task - The worker runs this function
    • size - The number of workers in the pool (defaults to the number of cores)
  • await pool.run(arg1, arg2, ...) - Executes the task once with the arguments provided.

  • await pool.close() - Terminates all the workers, allowing the process to exit.

  • pool.isMainThread - Allows logic based on whether we're in a worker or not.

Compatibility

Node.js 12+ for stable worker_threads

ts-node-dev

There's best-effort support for ts-node-dev. You must provide the following:

  1. TS_NODE_DEV_CACHE as an environment variable
  2. The same directory should be provided to ts-node-dev via --cache-directory

CLI example:

TS_NODE_DEV_CACHE=.ts-node tsnd --cache-directory $TS_NODE_DEV_CACHE --respawn index.ts

License

MIT

See also