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 🙏

© 2026 – Pkg Stats / Ryan Hefner

collabor8

v0.0.6

Published

A simple consensus script for distributed systems relying on riak as a data store

Readme

Collabor8

A simple consensus script for distributed systems relying on riak as a data store

Work-In-Progress. This script was developed for a very specific personal use case. It may not work well for general use cases. It still needs you to do the work of configuring riak nodes for each computer.

Configuring riak on the master or the first computer to be setup

riak-admin bucket-type create consensus '{"props":{"datatype":"map"}}'

riak-admin bucket-type activate consensus

Things to do

Ensure that all riak nodes in the network are part of the same cluster i.e riak-admin cluster join riak@-master-node- Ensure riak master node has planned and committed the riak nodes

How to use

Add node details to riak node

Collabor8.updateNode( function (result) {
  if (result === true) {
    // We have updated riak with details of this computer.
    // We do this with other computers so that we create a sort of manifest of all computers to join the cluster
  }
})

Join a cluster

Collabor8.getPeers( function (peers) {
  Collabor8.joinNetwork( peers, function (skiff, riakClient, connected) {
    if (connected === true) {
      // We are connected to the cluster. 
      if (skiff._node._state.name === 'leader') {
        // We can do stuff as leader
      }
      if (skiff._node._state.name === 'follower') {
        // We can do stuff as follower
      }
      // We can use the riakClient object to update the riak key/value store. See basho-riak-client npm module for more details
      riakClient.ping(function (err, rslt) {
        if (err) {
          console.log('Riak node is down')
        } else {
          console.log('Riak node is up. We can update riak')
        }
      })
    }
  })
})