
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
The simplest way to connect a client to a server while bypassing any HTTP features designed for server-side rendering.
The simplest way to connect a client to a server while bypassing any HTTP features designed for server-side rendering.
0.2 kB
for v0.3.1
import { client } from 'eipiai'
import type { routes } from './server'
const server = client<typeof routes>({ url: 'http://localhost:3000/api' })
const { error, data } = await server.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.
[!TIP] Enable TypeScript
"strict": true
mode in yourtsconfig.json
to allow for optimal object schema inference.
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)
A websocket connection client can be used for real-time communication with the server.
import { Elysia } from 'elysia'
import { api, route, subscribe, z } from 'eipiai'
import { eipiai } from 'eipiai/elysia'
import { socket } from 'eipiai/socket'
export const routes = api({
// Subscribe to any changes to posts.
subscribePosts: subscribe()
// Subscribe to updates for a specific post.
subscribePost: subscribe(z.object({ id: z.number() })),
// Can be mixed with regular routes, also sent through socket.
allPosts: route()((_) => { return [{ id: 0, text: 'Hello World' }] })
})
const path = 'data'
const { inject, subscriptions } = socket(methods, { path })
new Elysia().use(inject).listen(port)
const url = new URL(path, `ws://localhost:${port}`).toString()
console.log(`Websocket running on ${url}!`)
subscriptions.subscribePosts([{ id: 0, text: 'Hello World' }, { id: 1, text: 'Hello Again!' }])
subscriptions.subscribePost({ id: 0, text: 'Hello Again!' })
On the client make sure to use socketClient
to start a websocket connection.
import { socketClient } from 'eipiai'
import type { routes } from './server'
const server = socketClient<typeof routes>({ url: 'ws://localhost:3000/api' })
await server.subscribePosts((posts) => console.log(posts))
await server.subscribePost((post) => console.log(post.id === 0), { id: 0 })
const { error, data } = await server.allPosts()
For the client, all you need from the server are the types. Because of this, it is possible to conditionally import these from an external location that is only available locally using the following trick. This will ensure that the types are available locally where you actually need them, without causing an error in the CI or when running the client separately in production.
import { client } from 'eipiai'
let routes: typeof import('../server/routes').routes | undefined
export const server = client<typeof routes>()
Thanks to early-return
it's possible to handle errors in routes while preserving type inference. There is no need to call return
as a call to error will stop execution of the route handler and return an error.
import { Elysia } from 'elysia'
import { api, route, z } from 'eipiai'
import { eipiai, error } from 'eipiai/elysia'
function callGlobalContext() {
error('Error without passing context!')
}
export const routes = api({
withError: route(z.boolean())(({ error }, shouldError) => {
if (shouldError) {
error(`Custom error ${id} with ${uid}.`)
}
return 123
}),
withGlobalError: route(z.boolean())((_, shouldError) => {
if (shouldError) {
callGlobalContext(id)
}
return 345
}),
})
new Elysia().use(eipiai(routes)).listen(3000)
FAQs
The simplest way to connect a client to a server while bypassing any HTTP features designed for server-side rendering.
The npm package eipiai receives a total of 22 weekly downloads. As such, eipiai popularity was classified as not popular.
We found that eipiai demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.