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

seaport-cache

v0.0.2

Published

A caching layer for seaport that lets you run nicely even if the seaport server dies.

Downloads

3

Readme

seaport-cache

A caching layer for seaport that lets you run nicely even if the seaport server dies.

This library takes a connected seaport object and caches all the results so that if the connection with seaport is lost, we can still run using the cached data.

Also adds some nice functions to automatically select a host based on random or round-robin principles.

example

Run the seaport service and register a server as normal.

On the client use like this:

var request = require('request');
var seaport = require('seaport');
var spcache = require('seaport-cache');

var ports = seaport.connect(9090, { secret : 'beep boop' });
var cache = spcache.getCache(ports);

setInterval(function () {
  cache.getRoundRobin('[email protected]', function (h) {
    var u = 'http://' + h.host + ':' + h.port;

    request(u).pipe(process.stdout);
  });
}, 1000);

methods

var seaportcache = require('seaport-cache');

seaportcache.getCache(ports)

Takes the ports object returned from seaport.connect and returns the cache object which you can query directly.

cache.get(role, cb)

Request an array of host/port objects through cb(services) that fulfill role

If there are no services that match the callback will be queued until some fulfilling role gets allocated.

cache.getFirst(role, cb)

As with get, but returns just the first host/port object instead of the whole array, equive to using services[0] in the callback.

cache.getAny(role, cb)

As with get but returns a random host/port object from the array.

cache.getRoundRobin(role, cb)

As with get but returns the first entry from the array on the first call, the second entry from the array on the second call, etc.

The round robin is based on the exact role string used, so different role queries get different sequences even if they match the name sequence of servers.