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

jsonrpc-client-websocket

v1.5.5

Published

A simple JSON RPC 2.0 websocket client

Downloads

103

Readme

📦 Build License NPM downloads

jsonrpc-client-websocket

A simple JSON RPC 2.0 client over websockets

Open connection

const websocketUrl = 'ws://mywebsocketurl:port';
const requestTimeoutMs = 2000;
const websocket = new JsonRpcWebsocket(websocketUrl, requestTimeoutMs, (error: JsonRpcError) => {
  /* handle error */
});
await websocket.open();

Requests that do not receive a response within the specified timeout will fail with a REQUEST_TIMEOUT code. The callback (optional) is used for eventual errors, such as receiving a response that does not match any request id and connection errors. Furthermore, all errors that are sent to an eventual caller are also reported on the callback, e.g. if an rpc method is called with an invalid number of parameters, etc...

Close connection

await websocket.close();

Call RPC method

Considering that the server has a method sum(a: int, b: int)

with positional parameters

websocket.call('sum', [1, 2])
  .then((response) => {
    // handle response
  })
  .catch((error) => {
    // handle error
  });

with named parameters

websocket.call('sum', { b: 1, a: 2 })
  .then((response) => {
    // handle response
  })
  .catch((error) => {
    // handle error
  });

Send notification

Considering that the server has a method log(message: string)

websocket.notify('log', ['a log message']);

Define RPC method

websocket.on('sum', (a: number, b: number) => {
  return a + b;
});

The defined RPC methods can also be called with both positional and named parameters.

Minification/Obfuscation

When using code minification/obfuscation the parameter names may change, which can cause calls using named parameters to fail. To mitigate this you can do one or a combination of the following:

  • do not minify/obfuscate the code where on is used, so the function registration does not get modified
  • use positional parameters
  • register functions as following:
websocket.on('sum', (params: { a: number; b: number }) => {
  return params.a + params.b;
});

and then call the function using positional parameters using the object:

websocket.call('sum', [{ a: 1, b: 2 }])
  .then((response) => {
    // handle response
  })
  .catch((error) => {
    // handle error
  });

Remove RPC method

websocket.off('sum');