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

@spiff/forker

v1.0.0

Published

A system for managing inter process communication between generic interconnected modules. Its api is eventually going to be used in the [purity browser](https://github.com/purityapp/purity).

Downloads

4

Readme

forker

A system for managing inter process communication between generic interconnected modules. Its api is eventually going to be used in the purity browser.

Right now I'm going to call it a nodejs based userland microkernel framework.

usage

git clone https://github.com/purityapp/forker
cd forker
npm test

This will run an interactive nodejs console with the forker and manager objects pre-loaded. To run the example module, enter manager.spawn('example') a couple times. The example's ping message should be called a couple times, and the messages should be logged to the console.

documentation

API documentation is located in the docs foler.

example system

var system = new forker.System();

system.on('peer-found', function(peer) {
  peer.messages.ping(null, function(args) {
    console.log(args);
  });
});

system.messages.ping = function() {
  return {ping: 'pong'};
}

system.register('example', 'an example module');

After the forker.System object is created, a peer-found callback is set along with the ping message. When a new module recieves a peer, it is passed through the peer argument of the peer-found event. The recieving system can then inspect and call the peer's messages through the peer.messages object.

example manager

var manager = new forker.Manager();

manager.on('message', function(args) {
  args.to.process.send({from: args.from.process.pid, path: args.path, args: args.args});
});

Here the message event listener passes all messages to their intended recipient.