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 🙏

© 2025 – Pkg Stats / Ryan Hefner

websocket-events

v2.0.0

Published

user events for WebSocket-Node

Readme

websocket-events

user events for WebSocket-Node connections.

NPM

Installation

npm i websocket-events

Usage

const websocket = require('websocket');
const events = require('websocket-events');

/* -- instance creation of http.Server is omitted -- */

const server = new websocket.server({httpServer: http});

server.on('request', request => {
	const connection = request.accept();

	connection.on('error', err => {
		if (err.userEventError) {
			console.log('user event error:', err);
		}
		else {
			console.log('error:', err);
		}
	});

	connection.on('close', (reasonCode, description) => {
		console.log('closed:', reasonCode, description);
	});

	// use here
	const options = {};
	events(connection, options);

	connection.on('user-event', data => {
		console.log('user-event:', data);
	});

	// this listener is only used when not set listeners
	connection.on('default', event => {
		console.log('default listener:', event.name, event.content);
	});

	// send user event as message of json data
	connection.send('user-event', { hoge: 'piyo' });

	// send normal text message
	connection.send('normal message');
});

:bulb: The example is used on the server, but it can also be used on the client.

Usable Options

eventKeyName

The name used as key of event name. Default value is @event.

defaultEventName

The name used when event listeners is not set. Default value is default.

License

MIT