Supported backend frameworks:

• Hono - exceptional performance, runs on Node/Deno/Bun/edge platforms unchanged.
• H3 - similar to Hono in performance and multi‑runtime support, focus on Web standards.
• Koa - battle-tested, mature ecosystem, elegant async/await middleware, Node-focused.

Route organization, middleware composition, and validation are identical between frameworks. The difference is the context API inside handlers - each framework has its own.

Defining Endpoints

Every API route exports a defineRoute definition as its default export. The factory function receives HTTP method builders and use for middleware, and returns an array of handlers. Destructure only what you need:

api/users/[id]/index.ts

import { defineRoute } from "_/api";

export default defineRoute<"users/[id]">(({ GET }) => [
  GET(async (ctx) => {
    // handle GET /users/:id
  }),
]);

Multiple methods in one route:

api/users/index.ts

export default defineRoute(({ GET, POST, PUT, DELETE }) => [
  GET(async (ctx) => { /* retrieve */ }),
  POST(async (ctx) => { /* create */ }),
  PUT(async (ctx) => { /* update */ }),
  DELETE(async (ctx) => { /* delete */ }),
]);

Handler order doesn't matter - requests are dispatched by HTTP method. Undefined methods return 405 Method Not Allowed automatically.

Available builders: HEAD, OPTIONS, GET, POST, PUT, PATCH, DELETE.

This method-based routing style draws inspiration from Sinatra - the Ruby framework that pioneered it back in 2007.

Type Safety

Parameters, payloads, and responses are all typed through type arguments - the same definitions drive both compile-time checking and runtime validation. No separate schema language, no DSL switching. Details ›

Middleware

The use function gives you fine-grained middleware control at the route level, complementing global and cascading middleware. Details ›