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

asyncme

v0.1.0

Published

Turn blocking code to asynchronous functions

Downloads

5

Readme

AsyncMe

Turn blocking code to asynchronous functions

Usage

const asyncme = require("asyncme")({poolSize: 1, disposable: true});

asyncme.run(function(start) {
    //blocking code
    for (var i=0; i<=100000000; i++) {
        start += i;
    }
    return start; //always return the result
}, 10) //that's how you pass parameters
.then(function(result) {
    console.log("total:", result);
})
.catch(function(err) {
    console.error(err);
});

console.log("I am unblocked!");

Options

poolSize How many workers to spawn. Defaults to cpu core count. Pass 0 for none.
disposable Kill each worker as soon as its work is completed. Defaults to false

Methods

run(task<function>, [...args]) => <Promise>
Pass a function with the blocking code plus any optional arguments.
Always return the result from inside the function.
spawn([count=1]<Number>) => <asyncMeInstance>
Add workers on demand. Defaults to 1. Returns the instance.
exit() => <Promise>
Gracefully kill all the workers when their work is completed. The promise is resolved when all the workers have been killed. exitNow() => <Promise>
Immediately kill all the workers without waiting. The promise is resolved when all the workers have been killed.

Properties

_workers
The internal pool of workers (child processes).

Examples

There are many examples in the examples folder showing many possible situations like running parallel tasks, throwing errors, killing the workers and limitations.

Notes

The workers are child processes spawned with process.fork() and the communication is made using standard node process messaging.
The task functions are serialized and then executed on the child process using the Function constructor which will practically eval() the function, so keep that in mind and don't pass unsafe code.
Tested on the current node LTS (v6.9.5). Uses many es6 features so older node versions might not work.

Limitations

Doesn't work on the browser.
Can't use require() inside the tasks.
External scope is not transfered.
Asynchronous code won't be properly handled (the promise will resolve and/or the worker might be dead before it is completed).
Check the examples/wontWork.js

License

MIT