An eco-system for infrastructure around REST API. @apie/kit is made for 
- Endpoints that validate JSON and URLSearchParams (query) via Zod
- Easy to read Responses
- Accessible frontend API with generated types
[!NOTE]
Documentation incomplete.
bun add -D @apie/kit @apie/responses @apie/pipe
vite.config.ts
import { defineConfig } from 'vite'
import { sveltekit } from '@sveltejs/kit/vite'
import { watchAPI } from '@apie/kit'
export default defineConfig({
plugins: [sveltekit(), watchAPI()]
})svelte.config.js
/** @type {import('@sveltejs/kit').Config} */
const config = {
kit: {
alias: {
api: './src/api.ts',src/routes/api/users
import z from 'zod'
import { OK, BadRequest } from '@apie/responses'
import { endpoint } from '@apie/kit'
import getUsers from '...'
const query = z.object({
limit: z.number()
})
export const GET = endpoint({ /* body, */ query }, pipe => pipe(
async e => {
const users = await getUsers({ limit: e.query.limit })
if(!users) {
return BadRequest({
error: 'Too many users!... :D'
})
}
return OK({ users })
}
))src/routes/+page.svelte
<script>
import api from '$api'
const result = api.users.GET({ query: { limit: 5 } })
.any(res => console.log(res))
.$ // return the output of the following functions in order:
.OK(res => res.json()) // result = [this, ...]
.BadRequest(async res => (await res.json()).error) // result = [..., this]
</script>
{#await result}
loading users...
{:then [userList, error]}
...
{/await}
Make your life easier, and learn how to utilize @apie/pipe.
This enables code-splitting patterns, inspired by the functional programming paradigm.
This is optional, but a powerful one at that.