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

websocketserver

v1.0.0

Published

A WebSocket Server implementation for Node.js

Downloads

139

Readme

WebSocketServer

A WebSocket server implementation for Node.js, various features to still implement such as support for wss:// and performance analytics centre.

Installation

Install using npm - https://npmjs.org/package/websocketserver

Basic Usage

In a project require the websocketserver module and create an instance of it:

This will create a WebSocket server that runs on 9000 (default 8080) and uses a sendMethod that sends recieved connections to all server connections. Four sendMethods can be used:

  1. all - will send received messages to all users

  2. others - will send messages to all users apart from the sender

  3. echo - will echo the message back to the sender

  4. none - will not automatically send any messages (useful for when more control is needed over message sending, use API to send messages)

Events

The server emits events on a new connection, message and a closed connection:

  1. connection event - use to built a list of connections
  1. message event - get hold of the message
  1. connectionclosed - log a connection has left (can also use id to remove from connectionList)

Functions

  1. WebSocketServer.sendMessage(people, data, id); - send a message to specified people (all, others or one), data supports strings and packaged WebSocket messages (use packageMessage function for packaging), id is relates to the connection that you would like (or not to if others has been selected for the people argument, id not required if all has been selected).

This example shows how new connections to the server can be welcomed with a message:

  1. WebSocketServer.unmaskMessage(frame); - unmasks a WebSocket frame recieved by the server - returns a JavaScript objects with two properties: opcode and message (message is an array of bytes holding character codes - use convertToString(message) function to get the string representation)

Example shows how a message could be logged to the console:

  1. WebSocketServer.convertToString(bytes); - converts an array of bytes containing character codes to a string.

  2. WebSocketServer.packageMessage(opcode, message); - packages a recieved WebSocket message into a sendable WebSocket message - this function is only really necessary after use of unmaskMessage() as it is only really necessary for data that needs to pass through the server (primarily binary messages)

Example shows how we may filter binary data to send straight through the server as most of the time we have no reason to log it.

  1. WebSocketServer.closeConnection(id); close a specific connection