CodeVetter · Repo Unpack · Behavior traces
elysiajs/elysia
The inspected flows cover server startup, request validation and cookie persistence across HTTP boundaries. Additional traces follow shared counter state, native constant responses, WebSockets and file ranges. Execution order includes early returns and adapter-specific conditions. These walkthroughs describe source behavior and test intent; they are not recorded runtime executions.
- Startup: example/counter constructs Elysia, calls state then get, and listen delegates to BunAdapter.listen; that calls compile, builds serving options, invokes Bun.serve, then start hooks and the callback.
- AOT first request: handle accesses fetch, composeGeneralHandler builds dispatch and installs the error handler, request hooks precede routing, and a route's lazy compile closure calls composeHandler and caches its result.
- Dynamic POST: createDynamicHandler constructs context, runs request hooks, finds the route, parses JSON, runs transform hooks, validates body, runs beforeHandle, invokes handle and maps its response.
- Invalid-input branch: validateStandardSchema awaits Validate and throws on issues; dynamic dispatch catches the error and delegates to handleError, whose dynamic implementation runs error hooks before its status/message fallback.
- Cookie persistence: the /create example assigns name.value; the jar records outgoing changes, AOT encodeCookie signs selected cookies with the first configured key, handleSet serializes them, and later parseCookie verifies keys before decoding values.
- Shared counter: state('counter', 0) populates singleton.store, createContext passes that same store into the request, and the GET handler returns the previous counter value while incrementing it in memory.
- Native constant response: add asks createNativeStaticHandler for a literal handler, that helper rejects nonempty pipeline hooks, and BunAdapter refuses native static route assembly when request hooks, tracing or higher-order wrappers exist.
- File range request: mapResponse dispatches Blob/File to handleFile; a bytes range is parsed and clamped, invalid positions return 416, and valid positions produce a sliced 206 response with range/length headers.