
Research
/Security News
DuckDB npm Account Compromised in Continuing Supply Chain Attack
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
@cruise-automation/rpc
Advanced tools
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.
// 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);
});
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.
FAQs
Add RPC to WebWorkers with transferrable object support
We found that @cruise-automation/rpc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.
Product
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.