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

statemon

v0.5.2

Published

Facilitates cross server `socket.io-client` connections for the purpose of syncing `stdout`, `stderr`, latency, probing server frontends and of course sharing *state*.

Downloads

13

Readme

StateMon

Facilitates cross server socket.io-client connections for the purpose of syncing stdout, stderr, latency, probing server frontends and of course sharing state.

One Hub, many Leafs. Leafs connect to the Hub.

Examples

{ Leaf } = require 'statemon'

new Leaf()
##################################################

The Hub

	hubConfig =
		secret: 'password'

	# These two examples are equivilent
	hub = statemon { hub: hubConfig }

	{ Hub } = statemon
	hub = new Hub hubConfig
	hub =
		server: [SocketIo Server] # Emits events from Leafs

The hub should normally only exist once.

The Leaf


	leafConfig =
		secret : 'password'
		host   : 'http://someplace.com:1337'
		name   : 'Server 2'

	# These two examples are equivilent
	leaf = statemon { leaf: leafConfig }

	{ Leaf } = statemon
	leaf = new Leaf leafConfig
	leaf:
		socket   : [SocketIoClient Socket] # Emits events from the Hub
		###
			Modifiable listeners for Hub events, each bound to the leaf instance with .bind()
			Modify this only BEFORE .listen() is called to overwrite default listeners.
		###
		listeners : {}

Leafs exist on seperate processes/servers to other leafs/the hub. Leafs communicate with only the hub, and the hub to them.

TODO

  • Need to flesh out commands for leafs.
  • Hub LeafSession event listener flexibility/flesh out and documentation