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 🙏

© 2026 – Pkg Stats / Ryan Hefner

typed-remote-procedure-call

v2.1.1

Published

Library for typed RPC

Readme

workflow npm version

If you like this project, please support it with a star on Github 🌟

typed-remote-procedure-call

This library provides a convenient way to create transport-agnostic typed RPC It consists of two parts - caller and executor.

Possible use cases:

  • Frontend (caller) - HTTP - Backend (executor)
  • Frontend (caller) - Websocket - Backend (executor)
  • Backend (caller) - Websocket - Frontend (executor)
  • Host web app (caller) - Message bus - Iframe (executor)
  • Iframe (caller) - Message bus - Host web app (executor)

Installation

npm install --save typed-remote-procedure-call
# or
yarn add typed-remote-procedure-call

Usage

The fundamental entity in this library is Operation

type Operation = <Input, Output>(input: Input) => Promise<Output>;

First you need to declare your operations API

type Methods = {
    add: (input: { a: number; b: number }) => Promise<number>;
    createUser: (input: { name: string }) => Promise<{ age: number; name: string }>;
};

Executor

Executor is an engine that executes operations

import { createExecutor, ExecutionRequest, ExecutionResponse } from 'typed-remote-procedure-call';

const executor = createExecutor<Methods>({
    add: async (input: { a: number; b: number }) => input.a + input.b,
    createUser: async (input: { name: string }) => ({ age: 20, name: input.name }),
});
export const handleRequestFromCallerSide = async (request: ExecutionRequest): Promise<ExecutionResponse> =>
    executor.execute(request);

RPC

RPC is a wrapper that provides a convenient way to call operations

import { createRPC, ExecutionRequest } from 'typed-remote-procedure-call';

const rpc = createRPC<Methods>({
    send: async (request: ExecutionRequest) => sendRequestToExecutionSide(request), // Here you can use any transport
});

call

You can just call operations one by one

const user = await rpc.call.createUser({ name: 'John' });
const sum = await rpc.call.sum({ a: user.age, b: 2 });

chain

But you can also chain operations and execute them all in one batch

const sum = await rpc.chain((call) => {
    const user = call.createUser({ name: 'John' });
    return call.add({ a: user.age, b: 2 });
});

Here what's returned from call.operation(input) is not a promise but a reference to the operation result. You can use it to pass it to another operation. The returned reference is the final result of the chain of operations.