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

rpc-over-ws

v1.2.1

Published

A simple RPC-over-WebSockets server

Downloads

16

Readme

A simple RPC-over-WebSockets server

Installation

npm i rpc-over-ws

Usage

require('rpc-over-ws')({
  greet: function ({name}) {
    return new Promise(resolve => resolve(`Hello, ${name || 'anon'}`))
  }
})

$ wscat -c ws://localhost:8080
> {"id": 0, "rpc": "greet", "args": { "name": "brian" } }
< {"id":0,"rpc":"greet","result":"Hello, brian"}

API

const createServer = require('rpc-over-ws')

const { server, emitter, clients } = createServer(handlers, options)

  handlers = {
    $rpc: function (args, { server, clients, id, rpc }) -> Promise<result>
  }

  options = {
    port: int,            default: 8080
    pingTimeout: int,     default: 29000
    maxPings: int         default: 3
  }

"this" to a handler is the client WebSocket making the request.

If you wish to lookup other connected clients by some identifier, set this.clientId to something unique in one of your handlers and the client will be tracked in clients.

"result" must be encodable as JSON.

Events

  • 'server-ready' (server)
  • 'server-error' (error))
  • 'client-connect' (client)
  • 'client-disconnect' (client)
  • 'client-protocol-error' (client, error)
  • 'client-raw-message' (client, message)
  • 'client-io-error' (client, error)
  • 'client-identity' (client, clientId)

Protocol

Clients send JSON-encoded text frames of the form:

{ id: any, rpc: string, args: any }

The client creates the request id.


The request is routed to a handler.


The client is sent

{ id: same, rpc: same, result: any }

or

{ id: same, rpc: same, error: string }

The server matches the same request id so the client can route the result/error to a client-local callback.