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 🙏

© 2025 – Pkg Stats / Ryan Hefner

across

v0.0.1

Published

Node.js implementation of a multi-threaded map() function

Downloads

6

Readme

Welcome to Across

This tool is currently experimental, DO NOT USE UNDER PRODUCTION ENVIRONMENTS JUST YET.

This small tool was created as a way of processing large data sets in parallel by using Node's worker threads.

With it, most complexity related to multi-threading is abstracted, so you don't need to worry.

Most of this work is more of a proof-of-concept by now.

Basic Example

// Import our library
const { Distributed } = require('across')

// Let's create a sorta large array to process
const numberArray = Array.from(Array(1000000).keys())

// Our "processing" function will calculate the square-root of the numbers and return it as a string.
const iterator = (number) => `sqrt(${ number }) = ${ Math.sqrt(number).toFixed(2) }`

// Now let's process it!
Distributed.map(numberArray, iterator)
  // Since our map returns a Promise, we can wait for its result by using then()
  .then(results => {
    // Do something with them, in this case print them
    console.log('Results:', results)

    // Exit
    process.exit(0)
  })

By running the above snippet your function will be executed across multiple threads, by default, matching your CPU's core count.

Sure, with simple loads there's a big chance Node's built-in Array.map will be faster, since there will be no overhead regarding threads.

But, if you're doing something really CPU intensive and without any non-blocking options available, then you should expect your code to run much faster.

More Examples

Under the examples directory you should find some other examples for this. One of them is a small speed test using the bcrypt NPM module as reference.

This test will show you how long the processing takes by using the module's provided async version and the sync version, both with single-threaded and multi-threaded variations, plus a basic Array.map of it too.

To-do

  • Add new functions such as filter and reduce
  • Allow functions to be chained
  • Reduce Worker creation overhead
  • Work with Worker Pools