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

lb-request-client

v1.0.1

Published

A loadbalancing http request client based vaguely on some ideas from netlfix's ribbon

Downloads

6

Readme

lb-request-client

Pretty much a wrapper around mikeal's request for now

Providers a slightly reduced interface where the host:ip is picked for you via a 'loadbalancer' which you specify at creation time.

The load balancer should probably be configured before supplying it to this object The load balancer provided only has to supply a "chooseServer" function which returns {hostname: XX, port:YY}

Some general http related bits are from Mafinstosh's etcd client https://github.com/mafintosh/etcdjs

Usage

Examples in 'examples/*'

Why

The idea is that you can create a client for a given service (e.g an internal account service), so that anything else can just use the client without bothering about balancing requests across multiple endpoints, or worrying about service discovery.


// Assume this is a previously constructed instance
var serviceClient;

serviceClient.request('/users/183764', myCallback)

The loadbalancer should hide away all the messy bits.

Todo

  • Write tests...
  • Allow settings timeouts and request defaults in the client constructor
  • Allow information passing back to loadbalancer from the Client

WARNING

This mostly just proof-of-concept (coming to a production enviroment near you soon).

While I'll try to be semver-ish about this, expect massive changes between major versions.

Any questions, let me know via github issues, twitter, or email