CodeVetter · Repo Unpack · Contributor handoff
elysiajs/elysia
This brief is pinned to e037eca710e7ad193be09cc6615ab0dbe54af914 and comes from bounded public-source inspection of more than twelve source files. Tests and CI were inspected, not executed, and test existence does not establish passing behavior. Future edits should preserve execution parity, adapter boundaries and public inference. Repository contribution policies and script side effects need attention before moving beyond read-only analysis.
- Treat validation and routing conclusions as source-backed behavior, not execution results: tests and CI were inspected, not executed, and only selected tests were read.
- For routing changes, read add, its compile/cache closure, composeGeneralHandler and createDynamicHandler together; static tables and dynamic route stores use different representations.
- When checks are authorized, begin with a focused Bun test as CONTRIBUTING documents; relevant starting suites include dynamic-mode, native-static, cookie-signature and range tests.
- Preserve provider contracts: Standard Schema Check deliberately fails closed for Promise results, while asynchronous callers should use Validate and consume value/issues.
- Public API edits require inference review as well as runtime review: Elysia generics and MacroToContext feed route/context types, and test:types compiles the dedicated test/types project.
- Keep runtime checks specific: default adapter choice depends on Bun availability, WebStandard listen throws, Cloudflare precompiles routes, and Node fixtures only smoke-test app.handle.
- Match tabs, single quotes, no semicolons and no trailing commas; AGENTS requires surgical edits and reading exports/callers, while AI_POLICY requires human-reviewed contributions and rejects fully automated issue/PR creation.
- Do not treat scripts as harmless checks: build removes dist and shells out to tsc, Node/Cloudflare scripts install packages, Cloudflare testing spawns a server, and release publishes the package.