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 🙏

© 2026 – Pkg Stats / Ryan Hefner

express-ws-rpc

v0.0.3

Published

Simple JSON RPC over ws or simple-websocket

Readme

express-ws-rpc

Simple JSON RPC over ws or simple-websocket

Installation

npm install --save express-ws-rpc

Server

var express = require('express');
var wsrpc = require('express-ws-rpc');

// create app
var app = express();

// add websocket support to express app
var wss = require('express-ws')(app).wss;

// on websocket request to the root
app.ws('/', function(ws, req) {
	// this function gets called on each connection
	
	// extend ws to decode messages
	wsrpc(ws);
	
	// define method that can be called from the client
	ws.on('addServer', function (a, b, result) {
		result(null, a + b);
	});
	
	// define method depending on the state
	// each connected client owns its own `curr`
	var curr = 0;
	ws.on('next', function (result) {
		result(null, curr++);
	});
	
	// call method that is defined on the client
	ws.call('addClient', 1, 2, function(err, sum) {
		console.log('Client: 1 + 2 = ', sum, err);
	});
});

Client (browserify)

// convert relative WebSocket URL to the absolute one
function getWsAbsoluteUrl(relative) {
	var loc = window.location;
	var proto = loc.protocol === "https:" ? "wss://" : "ws://";
	var port = loc.port || (loc.protocol === "https:" ? 443 : 80);
	return proto + loc.hostname + ":" + port + relative;
}

// create WebSocket client
// I'm not using `ws` here, because it doesn't support
// EventEmitter interface (i.e. the one that lets you call `on`)
var WebSocket = require('simple-websocket');
var ws = new WebSocket(getWsAbsoluteUrl('/'));

// extend ws to decode messages
require('express-ws-rpc')(ws);

// method definition
ws.on('addClient', function (a, b, result) {
	result(null, a + b);
});

// when we get connected
ws.on('connect', function () {
	// call method that is defined on the server
	ws.call('addServer', 10, 20, function (err, sum) {
		console.log('Server: 10 + 20 = ', sum, err);
	});
});

License

MIT

Contribution

Everybody loves issues. You should probably create one.