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

@cruise-automation/rpc

v0.0.2

Published

Add RPC to WebWorkers with transferrable object support

Downloads

3,568

Readme

@cruise-automation/rpc

An RPC layer to make it easier to communicate between a WebWorker and the main thread. Has support for sending and responding with transferable objects to avoid structured cloning of large array buffers. It also propagates errors thrown in receivers back to the calling thread.

Example

// worker.js
import Rpc from '@cruise-automation/rpc'

const rpc = new Rpc(global);

rpc.receive('message', async ({ url }) => {
  const res = await fetch(url);
  if (!res.ok) {
    throw new Error('Bad response ' + res.status);
  }
  const json = await res.json()
  return { body: json }
});
// ui-thread.js
const worker = new WebWorker('./worker.js')
const rpc = new Rpc(worker);
rpc.send('message', { url }).then(({ body }) => {
  console.log('I got a response', body);
});

API

The Rpc constructor takes a MessagePort as its constructor argument. In a WebWorker you generally would use global and on the UI thread you would use the instance of the WebWorker as the MessagePort.

rpc.send<TResult>(topic: string, data: any, transferables: Transferable[]): Promise<TResult>

The send method takes a topic name and any data. This data is sent over the MessagePort and can be received on the other end with a registered rpc.receive() receiver on the same topic. You may also specify an optional array of transferable objects. This returns a promise which resolves with whatever the handler registered on rpc.receive returns.

const rpc = new Rpc(new WebWorker('/worker-script.js'))

rpc.send('fetch-and-parse', { url: '/lots-of-binary-data' }).then(({ result }) => {
  console.log(result);
});

rpc.receive<T, TOut>(topic: string, handler: (T) => TOut): void

The receive method registers a function to be called whenever a message is received on the specified topic. This function's return value can be waited on by a promise from the caller. To return an object with a list of transferable objects in the graph you can add the list with a special key to the response from your receiver.

// worker-script.js
rpc.receive('fetch-and-parse', async ({ url }) => {
  const res = await fetch(url);
  if (!res.ok) {
    throw new Error('Bad response ' + res.status);
  }
  const arrayBuffer = await res.arrayBuffer();
  const result = doLongRunningParseOperation(arrayBuffer);
  return {
    result,
    [Rpc.transferables]: [result]
  }
});

If the handler throws or rejects the error message will be sent through the MessagePort and calling thread's promise will reject.

Rpc.transferable

This is a static property on the Rpc class that contains the magic string you must use as a key when responding to a message in a receiver and attaching transferables to the response.