elixir-ts-rpcTyped RPC, Elixir ↔ TypeScript

Your Elixir functions callable from TypeScript. The function is the contract.

Get started

Try the playground

🧬

No schema, anywhere

No GraphQL SDL, no OpenAPI document, no Zod mirror. There is a function, and the compiler already knows its shape.

🛟

Typed errors end-to-end

Elixir error unions become typed, catchable errors in TypeScript.

🔗

Click through to the handler

Every generated method links to the Elixir line that produced it. Hover the call, follow the link, land on the handler.

🔥

Fits your Phoenix app

Mount one plug in your existing endpoint. Keep mix phx.gen.auth, CSRF, and your session exactly as they are.

⚙️

Codegen that fits your loop

Regenerate on every compile, on file change, or on demand in CI.

🧪

Real, full-stack examples

A React SPA on Plug. The same on a stock Phoenix app, with auth and CSRF.

See it run

A guided tour of the playground. Edit a @spec, watch the client regenerate, follow a method back to the handler that produced it, then rename a field and watch the TypeScript break. That is the real codegen running in the browser, compiled to WebAssembly. Try it yourself →

How it looks

A procedure is an ordinary function. Its @spec is how you tell the compiler its shape today:

elixir

defmodule MyApp.Users do
  use RpcElixir.Handler

  @spec get(%{id: String.t()}, RpcElixir.Context.t()) ::
          {:ok, %{id: String.t(), email: String.t()}} | {:error, :not_found}
  def get(%{id: id}, _ctx), do: ...
end

Expose the module on a router: