elysiajs

Scaffold a project with bun create elysia app, then define routes by chaining methods like .get() and .post() on a new Elysia instance. Attach TypeBox schemas in route options to validate body, params, and query with full type inference.

Install @elysiajs/jwt and register it with .use(jwt({ name: 'jwt', secret })). Then call jwt.sign() to issue tokens and jwt.verify() in protected routes, typically storing the token in a signed cookie.

Yes. Use the @elysiajs/node adapter for Node.js, or the CloudflareAdapter from elysia/adapter/cloudflare-worker with .compile() for Workers. Deno, Vercel, Expo, and Next.js API routes are also supported via Web Standard Request/Response.

TypeBox is Elysia's native schema library accessed via the t export, offering the tightest type inference and features like t.File and t.Cookie. Zod, Valibot, and ArkType are supported through Standard Schema for teams preferring those ecosystems.

Elysia encapsulates lifecycle hooks and decorations by default, so they do not leak between instances. Declare dependencies explicitly with .use(plugin), and set hook scope to 'scoped' or 'global' when you need shared behavior.

Compile to a single binary with bun build --compile --target bun, then run it directly or inside a distroless Docker image. Enable health check routes, graceful shutdown handlers, and environment-based configuration for production readiness.