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

a-pea-eye

v1.2.9

Published

A strongly-typed RPC framework for client-server applications written in TypeScript.

Downloads

7

Readme

A-Pea-Eye GitHub license npm version

A strongly-typed RPC framework for client-server applications written in TypeScript.

Motivation

It helps to have correctness guarantees from your compiler when writing your programs. This is applicable when writing client-server applications, but requires some tooling to achieve.

To this end, we can use an RPC client that is aware of the return type of the server response. We will encode the data type and error type into the return type of an RPC method. The client will infer the return type from the RPC method enabling the compiler to know about data and error types. The compiler will enforce appropriate error handling on the client: providing us strongly-typed client-server code.

Our error propagation is inspired by Rust's Result type, which returns a tuple of Result<T, E> from a function. Here T is your data type and E is your error type.

Features

  • [x] RPC Client that can propagate errors, data types, stack traces over a network boundary
  • [ ] Stack traces and errors are anonymized/hidden in production
  • [ ] Runtime type guards on client boundaries (with appropriate exception handling)

Usage

We define our server methods as functions with a return type of Result<T, E>. This is equivalent to Ok<T> | Err<E>.

Note: Our function's return type conforms with Ok(x/y) and Err('Divided by zero').

// methods.ts
import { Ok, Err, Result } from 'a-pea-eye'

// Define methods for your server logic
export const methods = {
  divide(
    _req: Request,
    x: number,
    y: number
  ): Result<number, 'Divided by zero'> {
    if (y === 0) {
      return Err('Divided by zero')
    } else {
      return Ok(x / y)
    }
  },
}

Create a client that is aware of the return types of your methods.

// client.ts
import { createClient } from 'a-pea-eye'
import { methods } from './methods'

// Create RPC client
const client = createClient<typeof methods>(`http://localhost:8080/rpc'`)

// Invoke method on RPC client
const result = await client.divide(10, 0)

// NOTE: TypeScript enforces error checking through type narrowing.
if (result.ok) {
  const quotient = val // compiler knows `val` is of type 'number'
} else {
  const err = val // compiler knows `val` is of type 'string'
}

Finally, this is what configuring your server looks like.

// server.ts
import { createMiddleware } from 'a-pea-eye'
import express from 'express'
import { methods } from './methods'

// Configure express server
const app = express()
app.use(express.json())
app.post('/rpc', createMiddleware(methods))

// Start server
app.listen(8080)

Alternatives

  • https://github.com/shekohex/jsonrpc-ts
  • https://github.com/aiden/rpc_ts
  • https://github.com/strongloop/loopback-next