eipiai

The simplest way to connect a client to a server while bypassing any HTTP features designed for server-side rendering.

• 🎓 End-to-end server/client type safety with TypeScript
• 🪶 Tiny client footprint 0.2 kB for v0.3.1
• 💯 Server adapters for Elysia
• 🌳 Custom variables automatically shared among routes

import { client } from 'eipiai'
import type { routes } from './server'

const data = client<typeof routes>({ url: 'http://localhost:3000/api' })

const { error, data } = await data.getPost(3)

On the client you'll import only the type definitions from the server. This way you'll get the most up-to-date types without anything ending up in the resulting client bundle.

import { Elysia } from 'elysia'
import { api, route, z } from 'eipiai'
import { eipiai } from 'eipiai/elysia'

export const routes = api({
  getPost: route(z.number())((_, id) => { return id * 2 })
})

new Elysia().use(eipiai(routes, { path: 'api' })).listen(3000)

On the server, in this case implemented with Bun's Elysia you define the routes with their types and the handler. The plugin will then inject the required POST endpoint on the desired path.

Vercel

While not perfectly suited for Vercel Serverless functions it can still work. All routes will be handled by a single function inside the /api folder of your project. For this export the server as a POST variable. Regular TypeScript Serverless functions won't be able to handle a TypeScript dependency like this one unfortunately, so you'll have to bundle the file and inline all eipiai imports. To configure the route path, place the file at that location in the file system.

import { vercel } from 'eipiai/vercel'
import { routes } from './server'

export const POST = vercel(routes)