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

client-state

v1.1.2

Published

Manage Redis connections with a Finite State Machine

Downloads

3

Readme

client-state

Manage event-emitting clients using a state machine.

install

npm install client-state

Usage

The goal is to provide a Finite State Machine that reflects various states of availability for a given endpoint or service (which I will call a client, such as a Redis database.

An instance of this module's interface emits events corresponding to events in the client.

For example, assume that a client emits the following events:

  • connect (a connection has been established)
  • ready (the connection is ready to receive commands)
  • reconnecting
  • end (a connection has been lost)
  • error (some sort of error with the connection has occurred)
  • warning (some non-critical warning has been emitted by the client)

If you pass this client to client-state:

let cs = require('client-state');
let stateM = cs(someclient);

You can query the current state of the client like so:

stateM.state() // `ready`, for example

You can listen for state changes (again, reflecting events emitted by client)

stateM.on('ready', data => {
    // See below for breakdown of what `data` is
});

The redis module emits all of the above events.