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

hunting-websocket

v0.0.4

Published

WebSocket with automatic reconnection and client side failover.

Downloads

5

Readme

#Overview This is a WebSocket, or really, it is an array of WebSockets that acts as one websocket that provides client side failover and reconnection. The idea is you use this from single page applications with worldwide deployment of WebSocket servers to get the best performance and geographic failover.

You can also use it server to server. We ♥ you.

#Use It It works like, and has the events of, a WebSocket. One exception, you connect to an array of host names.

A fun way to test this is with our buddy program, which sets up a totally unreliable websocket that randomly closes on clients to simulate disconnection:

npm install -g the-waffler
waffler 8000 &
waffler 8001 &
var HuntingWebSocket = require('hunting-websocket');
var socket = new HuntingWebSocket([
  'ws://localhost:8000',
  'ws://localhost:8001']);

socket.onopen = function(evt) {
  //called on the first open, and only once
}

socket.onserver = function(evt) {
  //called any time the socket server has changed, either from a
  //failover or a reconnect
  //evt.server
}

socket.onerror = function(err) {
  //badness detected!
}

socket.onmessage = function(evt) {
  //message in evt.data
}

socket.onclose = function(evt) {
  //by-bye, called on if you really call .close()
}

socket.send('hi');
socket.send('mom');

socket.close()

#Browserify! This package is set up to use with browserify from npm, though it is fundamentally designed to be client side.