Package surface

The core barrel

Everything is a named export from the core barrel (s200) — tree-shaking starts at the import statement (defineMiddleware, the third-party battery authoring hook, lives there too).

Package entries

Each below is a separate package entry — importing one pulls exactly it. Every name links to its section in the API Reference:

• Core barrel: s200 — createApp, the router primitives; the barrel's respond helpers, body readers, and serveStatic
• Adapters: s200/node, s200/bun, s200/cloudflare, s200/aws-lambda, s200/vercel
• Security: s200/cors, s200/csrf, s200/auth, s200/jwt, s200/oauth, s200/secure-headers, s200/rate-limit, s200/trust-proxy
• Request intake: s200/validate, s200/query, s200/accepts, s200/multipart, s200/upload
• Response batteries: s200/serialize, s200/etag, s200/compress, s200/streaming, s200/response-check
• Cookies & sessions: s200/cookies, s200/session
• Observability: s200/logger, s200/request-id, s200/timing, s200/otel, s200/version
• Data & config: s200/cache, s200/config, s200/events, s200/schedule
• Realtime: s200/websocket, s200/websocket/node, s200/websocket/bun, s200/websocket/cloudflare
• OpenAPI & tooling: s200/route-table, s200/meta, s200/openapi, s200/swagger, s200/codegen, s200/client, s200/test, s200/mcp
• Lifecycle: s200/lifecycle, s200/health, s200/timeout, s200/dev
• Ambient context: s200/als — als, currentCtx (node/bun only; no async_hooks on edge)
• Sharding & execution: s200/shard, s200/gateway, s200/shard-dev, s200/executor, s200/unit-metrics, s200/proxy

Dependencies

The core and every battery except s200/events are zero-dependency; s200/events adds @for-fun/event-emitter as its single dependency.

Every entry's exports, signatures, and options are documented in the API Reference.