Start with a small Fetch API server, then grow into validator, typed RPC, OpenAPI, and production middleware without switching mental models.
If this is your first time with orva, use this order:
If you are moving from another Node or Fetch framework, read Migrate from Express or Hono early.
orva is good at Every request enters through the Fetch API shape, and adapters only bridge host-specific request objects into that model.
JSON, form, query, param, header, cookie, and text inputs can all flow through one type-safe validation path.
Context, middleware, and route composition stay readable, so business logic can stay concentrated inside handlers.
Validation metadata can keep flowing into RPC and OpenAPI, reducing drift between runtime code, docs, and clients.
import { createOrva } from 'orvajs';
import { serveNode } from 'orvajs/adapters/node';
import { requestId, secureHeaders } from 'orvajs/middlewares';
const app = createOrva()
.use(requestId(), secureHeaders())
.get('/health', (c) => c.json({
ok: true,
requestId: c.get('requestId'),
}));
serveNode(app, { port: 3000 });import { createOrva } from "orvajs";
import { serveNode } from "orvajs/adapters/node";
import { requestId, secureHeaders } from "orvajs/middlewares";
const app = createOrva().use(requestId(), secureHeaders()).get("/health", (c) => c.json({
ok: true,
requestId: c.get("requestId")
}));
serveNode(app, { port: 3e3 });| Goal | Go here |
|---|---|
| Run the first service | Quickstart |
| Understand the request model | Context and Responses |
| Understand contract propagation | Type Flow |
| Build a REST API | REST API Recipe |
| Build a typed client workflow | Typed RPC App Recipe |
| Assemble a production middleware stack | Middleware Cookbook |
| Port an existing service from another framework | Migration Guide |
| Look up exports and modules | Reference |
| Area | Entry |
|---|---|
| Core framework | Reference overview |
| Validator | Validator |
| RPC | RPC |
| OpenAPI | OpenAPI |
| Middleware | Middleware catalog |
| Adapters | Adapters |