Call methods on any object over RPC with minimal fuss.
Create a "mirror" of an object on the server in the client. You can call any methods on the server object by calling the same method name on the client object. You can also subscribe to events on the client as if you were subscribing to events on the original API. Synchronous methods on the server object become asynchronous methods on the client-side. Properties on the server object become asynchronous getter methods on the client, e.g. for a server object { foo: 'bar' } the property foo can be read on the client via await clientApi.foo().
Unlike other RPC libraries, this does not require any boilerplate to define methods that are available over RPC. All methods and properties on the server object are "reflected" in client API automatically. Any method called on the client object will return a Promise, but methods that are not defined on the server will throw with a ReferenceError.
Most RPC libraries I could find require a lot of boilerplate to define the methods that are available over RPC. I wanted an easy way for an API on the server to be used from a client in exactly the same way as it is on the server, without needing to setup any RPC methods. Under-the-hood this uses a Proxy object.
npm install rpc-reflectorimport { createClient, createServer } from 'rpc-reflector'
import DuplexPair from 'native-duplexpair'
const myApi = {
syncMethod: () => 'result1',
asyncMethod: () =>
new Promise((resolve, reject) => {
setTimeout(() => resolve('result2'), 200)
}),
}
// Create two duplex sockets linked together
const { socket1, socket2 } = new DuplexPair({ objectMode: true })
const serverStream = socket1
const clientStream = socket2
const { close } = createServer(myApi, serverStream)
const myApiOnClient = createClient<typeof myApi>(clientStream)
;(async () => {
const result1 = await myApiOnClient.syncMethod()
const result2 = await myApiOnClient.asyncMethod()
console.log(result1) // 'result1'
console.log(result2) // 'result2'
})()api can be any object with any properties, methods and events that you want reflected in the client API.
channel can be a Duplex Stream, a browser MessagePort, a Node Worker MessagePort or a MessagePort-like object that defines a postMessage() method and implements an EventEmitter that emits an event named 'message'.
If channel is a MessagePort you will need to manually call port.start() to start sending messages queued in the port.
close() is used to remove event listeners from the channel. It will not close or destroy the MessagePort or Stream used as the channel.
channel: see above for createServer()
Returns clientApi which can be called with any method on the api passed to createServer(). Events on api can be subscribed to via clientApi.on(eventName, handler) on the client. Properties/fields on the server api can be access by calling a method with the same name on the client API, e.g. to access the property api.myProp, on the client call await clientApi.myProp().
When using Typescript, you can pass the type of the server API as a generic e.g.
const clientApi = createClient<ServerApi>(channel)The returned clientApi will be correctly typed, with synchronous functions converted to synchronous.
The static method close() will remove all event listeners from the channel used to create the client. It will not close or destroy the MessagePort or Stream used as the channel.
createServer() and createClient() write messages to the Stream or MessagePort as objects, and they expect the messages read from the Stream or MessagePort to be objects. If you are using a socket or TCP stream as a transport for RPC messages, you will need to encode the objects as buffers. The createEncodeDecodeStream() helper will encode and decode messages over the duplex stream using MessagePack.
opts.encoding An encoding object that contains encode(value) and decode(buffer) functions for encoding values to and from buffers. Defaults to MessagePack encoding with support for encoding/decoding Buffers. See the default implementation
PRs accepted.
Small note: If editing the README, please conform to the standard-readme specification.
MIT © 2020 Gregor MacLennan