s200Data + functions, on the Web Standard

Data + functions server framework on the Web Standard: koa-style onion middleware, hono-style multi-runtime portability, replaceable modules, fully tree-shakable. Zero dependencies.

Get Started

API Reference

GitHub

🧩

Data + functions paradigm

An application is plain data — routes, middlewares, config. Behavior never hangs off it: every capability is a top-level function taking the app (or request context) as its first argument.

🪶

Zero dependencies

No runtime dependencies at all. The core only touches Web Standard Request/Response.

✂️

Fully tree-shakable batteries

cors, logger, compress, websocket, jwt and friends live in separate entries — importing one pulls only it, the core stays lean.

🌍

Multi-runtime

node · bun · edge. Adapters for s200/node, s200/bun and s200/cloudflare; the core consumes Web Standard Request/Response directly.

🛡️

Typed client from the route table

createClient(app) derives a type-safe fetch client from the app's own route table — paths restricted to registered pattern literals, params typed from them, bodies typed from schema inputs, declared error branches unioned into json() and status.

🌲

Indexed trie router

Dispatch runs over a static-prefix trie indexed by every static segment — matching cost tracks URL depth, not route count.

⚡

Opt-in light fast path

serve(app, { light: true }) swaps in duck-typed request/response objects and writes byte-backed bodies straight to the socket — ~1.35–1.4× with zero global patching.

🧯

In-chain error boundary

404/405/500 fallbacks and error responses are materialized inside the chain — loggers, CORS and request-id stamp the real response on the unwind, never a phantom one.

🔌

Zero-dependency WebSocket

An in-house RFC 6455 server for node and Bun — subprotocols, permessage-deflate, heartbeat, and WSS over TLS. No ws, no bridge package.