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

node-ws-rpc

v2.4.0

Published

Rpc client built on persistent ws connections

Downloads

35

Readme

node-ws-rpc

Rpc client built on persistent ws connections. Uses http status codes.

Getting Started

npm install --save node-ws-rpc

Basic Usage

const { Client, Server } = require('node-ws-rpc');

// Create a server
const methods = {
	createUser(req) {
		const user = { name: req.body.name };
		req.reply(201, { user });
	},
};

const server = Server({ port: 3000 }, methods);


// Create a client
const client = Client('ws://localhost:3000');

client.call('createUser', { name: 'Dan' })
	.then((resp) => {
		console.log('Status:', resp.statusCode);
		console.log('User:', resp.body.user);
	})
	.catch((err) => {
		console.log(err.statusCode);
		console.log(err.body);
	});


// Detect when the persistent connection is closed
client.on('close', () => {
	console.log('Connection closed...');
});


// Later on... Manually close the connection
client.close();

Client

wsRpc.Client(address, socketOptions, rpcOptions)

address and socketOptions will be passed directly to the ws module when creating the socket.
rpcOptions:

  • connectionTimeout: how long to wait before closing the socket if the server is not responding to heartbeats.
  • heartbeatPeriod: how often to ping the server.

client.call(methodName, body, options)

Send a message to the server. Returns a promise. options:

  • Takes all options from rxjs-backoff.
  • timeout: Time to wait before throwing an error on a given attempt. If maxRetries is zero (default) then this will be the total time.
// Default options
initialDelay: 200,
maxDelay: 1000,
maxRetries: 0,
multiplier: 2,
retryWhen: () => true,
timeout: 5000,

client.on(eventName, callback)

Subscribe to an event. Valid event names: ['close', 'error'].

client.close()

Close the socket. Will fire the close event if it hasn't already fired.

Server

wsRpc.Server(socketOptions, methods, rpcOptions)

socketOptions will be passed directly to the ws module when creating the socket.
methods is a dictionary containing all the callable functions. A client will get a 404 if they call a function that is not defined here. rpcOptions:

  • connectionTimeout: how long to wait before closing the socket if the client is not responding to heartbeats.
  • heartbeatPeriod: how often to ping the client.

server.close()

Close the server. Server will stop accepting new sockets. All existing sockets will be disconnected.