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

forkify

v0.1.3

Published

Run synchronous functions inside a forked child process

Downloads

2

Readme

Forkify

Forkify lets you run functions in a forked child process

Install

$ npm install forkify

Features

  • Distribute executions over multiple instances
  • Create new instances when existing ones are too busy
  • Buffers & streams are sent over a separate socket to bypass costly JSON serialization
  • Idle instances are reaped (by default after 30 seconds)
  • Events can be emitted from the fork

Todo

  • You should also be able to send events to the fork
  • Emitted event arguments should be serialized through the same process as a function execution or callback, so buffers & streams can also be emitted

Examples

Forkify a function

var forkify = require('forkify');

// Forkify the function
var fibonacci = forkify(function generateFibonacci(amount, callback) {
    var fib = [],
        res,
        i;

    fib[0] = 0;
    fib[1] = 1;

    for (i = 2; i <= amount; i++) {
        res = fib[0] + fib[1];

        fib[0] = fib[1];
        fib[1] = res;
    }

    // Callback with the response
    callback(null, res);
});

fibonacci(10, function gotResult(err, result) {
    console.log('Fibonacci result:', err, result);
});

Work with buffers

You can pass Buffer instances back and forth, without problems. These are not serialized using JSON, as that is a costly affair. Unfortunately, they are also not using "shared memory", rather the buffer contents are sent to the child over an extra stream.


var workWithBuffers = forkify(function(buffer, callback) {

    // Outputs 6 in this case
    console.log(buffer.length);

    callback(null, new Buffer(40));
});

workWithBuffers(new Buffer(6), function(err, buffer) {
    // Outputs 40 in this case
    console.log(buffer.length);
});

Set instance pool size

By default, up to 3 instances are created. This can be modified at any time like this:

forkify.limit = 5;

Create a new forkify pool

If you want to create a separate pool, you can do so like this:

var forkify2 = forkify.constructor();

Set minimum idle time before reaping

Forks are killed after idling for at least 30 seconds. This can be changed by setting the idle property:

forkify.idle = 45000; // 45 seconds

Do note: For now, the reaping function only runs once every 10 seconds.

Caveats

forkify functions run in a new scope and can not access anything outside of it, you will have to re-require modules you wish to use inside the function.

Arguments passed to the forkified function are converted using a modified version of JSON-DRY (which supports Dates, Infinity, Errors, Buffers, ...)

Because of the addition of Buffer support forkify will keep your application running until all instances have been reaped.

License

MIT