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

json-rpc-ws

v7.0.1

Published

json-rpc websocket transport

Downloads

175

Readme

json-rpc-ws

Greenkeeper badge

A websocket transport for json-rpc. Allows for asynchronous bi-directional requests and responses.

Build Status

-- Method handlers are registered via the expose method. Results are routed through id via the callback passed to the send method.

For a simple example see the files in ./example

How to Use

Note: ws removed client code as of 1.0.0, so browser-based implementations of this work differently now

Node

var JsonRpcWs = require('json-rpc-ws');

var server = JsonRpcWs.createServer();

server.expose('mirror', function mirror (params, reply) {

    console.log('mirror handler', params);
    reply(null, params);
});

server.start({ port: 8080 }, function started () {

    console.log('Server started on port 8080');
});
var JsonRpcWs = require('json-rpc-ws');
var client = JsonRpcWs.createClient();

client.connect('ws://localhost:8080', function connected () {

    client.send('mirror', ['a param', 'another param'], function mirrorReply (error, reply) {

        console.log('mirror reply', reply);
    });
});

Browser

var JsonRpcWs = require('json-rpc-ws/browser');
var client = JsonRpcWs.createClient();

client.connect('ws://localhost:8080', function connected () {

    client.send('mirror', ['a param', 'another param'], function mirrorReply (error, reply) {

        console.log('mirror reply', reply);
    });
});

API

Server

start(options) - Start the server, options are passed straight into the ws server options. See the ws documentation for further info

Client

connect(url) - Connect to given url (should start with ws:// or wss://). Like the server, this parameter is passed straight into a ws WebSocket object.

Shared

Both the client and server have the following methods:

expose(method, handler) - Add a handler for a given named rpc method. Only one handler per method is allowed, as each request can only have one reply. The handler will be passed two parameters, the parameters from the rpc call and a callback in which to send the response. The callback takes two paramters error and reply. Because this is json-rpc only one of error and reply can be non-null.

License

MIT