elixir-ts-rpcTyped RPC, Elixir ↔ TypeScript

Define procedures in Elixir with ordinary @spec typespecs and a small router DSL. The fully typed TypeScript client is generated from them. No separate schema language, no hand-written TypeScript.

Get started

How it works

View on GitHub

🧬

Types from your typespecs

Input, output, and error types are read straight from your Elixir typespecs. No separate schema language, no TypeScript types to keep in sync.

🔌

HTTP transport included

A Plug pipeline validates input, runs your handler, validates output, and serializes, all with request-scoped middleware.

🛟

Typed errors end-to-end

Your Elixir error unions become typed, catchable errors in TypeScript. The failure path stays as typed as the happy path.

⚙️

Codegen that fits your loop

Regenerate the client on every compile, on file change, or on demand in CI. The client never drifts from your types.

🏷️

Custom & branded wire types

Control how values cross the wire. Send branded strings and numbers, epoch-millis datetimes, and your own custom types.

🧪

Real, full-stack examples

A React SPA on a Plug backend, and the same typed RPC on a stock Phoenix app reusing its auth and CSRF.

Status: early release (0.0.1), pre-1.0. APIs may change before 1.0. The HTTP Plug transport and TypeScript codegen are working and tested end-to-end. Realtime transports and framework adapters are not built yet.

In one glance

Write a handler with a classic @spec:

elixir

@spec get_user(%{id: integer()}, RpcElixir.Context.t()) ::
        {:ok, %{id: integer(), name: String.t()}} | {:error, :not_found}
def get_user(%{id: id}, _ctx), do: ...

Run mix rpc.gen.ts, and call it from the browser with full inference and typed errors:

const user = await client.users.get({ id: 1 });
//    ^? { id: number; name: string }

That's the whole idea. Your Elixir typespecs are the contract.