Elysia: a Bun-native TypeScript HTTP framework with end-to-end type safety
Ergonomic Framework for Humans
At a glance
- What is it?
- Elysia is an MIT-licensed TypeScript web framework for Bun, built around end-to-end type safety and type integrity. Here is what the repository shows, and where it stops.
- Who is it for?
- Adopt Elysia when your runtime is Bun and you want end-to-end type safety in TypeScript. Skip it if you are committed to Node.js or a large Express middleware stack, because the README documents no migration path and no Express compatibility layer.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- elysiajs/elysia19,357 ★ · +192
| Repository | 2026-09-21 | 2026-11-15 |
|---|---|---|
| elysiajs/elysia | 19.2k | 19.4k |
192 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What Elysia is for, and who it is not for
Elysia describes itself as an "Ergonomic Framework for Humans" and, in the README, as TypeScript with end-to-end type safety "Supercharged by Bun". The intended audience is developers already running Bun who want end-to-end type safety in TypeScript. The package publishes both ESM and CommonJS entry points through the exports map in package.json, with the main field pointing at ./dist/index.js and the module field at ./dist/index.mjs, so a bundler or a Node-style require can both resolve it. What the README does not do is argue for Elysia against anything else. There is no comparison table, no migration guide, and no statement about which Node.js versions work. If you are on Node.js and unwilling to move, the README gives you nothing to evaluate. That silence is itself the answer: the framework is positioned around Bun.
One schema, three outputs: the type system at the centre
The README's one-line pitch is TypeScript with end-to-end type safety and type integrity. The repository has example/nested-schema.ts and example/openapi.ts, and package.json exposes ./schema and ./type-system subpaths with their own dist output, so the type machinery is a separable module rather than something buried in the router. Other subpaths in the exports map are similarly self-describing: ./ws, ./ws/bun, ./compose, ./context, ./cookies, ./error, ./schema, ./sucrose and ./trace. The README does not explain what sucrose or trace do, and the documentation site is where that would live.
Installing Elysia and serving a first route
The README's own scaffolding command is bun create elysia app, shown as a bash block in the repository. Running it produces a project directory named app with Elysia already wired up, so you do not hand-write the entry point on the first run. The command assumes Bun is installed and on your PATH; the README does not list a minimum Bun version, so check the Bun release notes if your local install is old.
bun create elysia appThe repository also ships an example/ directory with small standalone files, including example/index.html, example/params.ts, example/body.ts, example/cookie.ts, example/headers.ts, example/error.ts, example/guard.ts, example/hook.ts, example/derive.ts and example/openapi.ts. These are the fastest way to see a single feature in isolation without reading the whole documentation site. The file names map to concepts rather than to a tutorial order, so treat example/ as a reference shelf: open example/body.ts when you need request body handling, example/derive.ts when you need per-request derived state, and example/openapi.ts when you need the generated specification. The README does not say whether these examples are covered by the test suite, and test/ exists as a separate top-level directory.
Where Elysia stops being the right tool
The clearest limitation is the runtime. The README's headline says "Supercharged by Bun". Nothing in the README describes a Node.js adapter, a Deno target, or a serverless entry point for a non-Bun platform. If your deployment target is a Node.js-only managed runtime, or a Lambda layer that pins a Node version, the README gives you no path. A second limitation is documentation depth in the repository itself. The README is largely a banner, a link to elysiajs.com, a Discord invite and a sponsors link, with the substantive sections commented out in the source file. That means the repository is not a self-contained reference: installation, routing, validation and plugin behaviour all live on the external site, and the README does not mirror them. Third, the release cadence visible in the repository is uneven rather than continuous. Version 1.4.30 is dated 2026-08-26, 1.4.29 is dated 2026-06-16, and 1.4.28 is dated 2026-03-16. Two gaps of roughly two and a half and three months sit between those tags, so a team that pins a minor version should expect to read the changelog rather than assume steady small patches. The last push to the default branch was on 2026-10-28, which is recent, but the tag dates are what a dependency pin actually tracks.
Elysia compared with Express and Hono
The real difference in approach is architectural rather than numeric. Express is a middleware chain: a request passes through a sequence of functions that mutate a request and response object, and types are supplied by the developer through DefinitelyTyped packages. Elysia's pitch, per its README, is end-to-end type safety on Bun. Hono is the closer comparison, because it also targets multiple runtimes and leans on Web standard Request and Response objects. The practical split is runtime breadth against type derivation: Hono's selling point is portability across runtimes, while Elysia's is end-to-end type safety. If portability matters more than end-to-end type safety on Bun, the trade runs the other way.
Maintenance, upgrade cost and the MIT licence
The repository is not archived. The last push to the default branch was on 2026-10-28, and the most recent release listed is 1.4.30 on 2026-08-26. The version field in package.json reads 1.4.30, matching that release tag, so the published package and the tagged release are aligned at the time of writing. The upgrade surface is wider than a typical library because Elysia ships many subpath exports: the root, ./ws, ./ws/types, ./ws/bun, ./compose, ./context, ./cookies, ./error, ./schema, ./sucrose, ./trace and ./type-system each have their own types, import and require entries in the exports map. A change to any of those subpaths is a potential breaking change for consumers that import from it directly, so read CHANGELOG.md before bumping a minor version rather than relying on semver alone. The repository carries an AGENTS.md, a CLAUDE.md and an AI_POLICY.md at the top level, which signals that contributions generated with AI tooling are governed by a written policy; read AI_POLICY.md before opening a pull request. The licence is MIT, which permits commercial use, modification and redistribution provided the copyright notice and permission notice are retained. That is a summary of the licence identifier, not legal advice; check the LICENSE file for the exact terms.
What the repository tells you that the README does not
The README is thin, but the file listing is informative. A build.ts at the top level alongside bun.lock indicates the package is built with Bun's own tooling rather than a separate bundler configuration. Three tsconfig files are present: tsconfig.json, tsconfig.dts.json and tsconfig.test.json, which suggests declaration output and test compilation are configured separately from the main build. A knip.json file indicates unused-export checking runs against the project, which matters for a library with this many subpath exports, because an export that nothing references and no test covers is easy to leave broken. .eslintrc.json and .prettierrc set the lint and format baseline. The example/ directory holds files spanning cookies, headers, guards, hooks, derivation, lazy modules, nested multipart files, proxying and HTML imports, which is a broader feature surface than the README's few lines suggest. None of this is documented in the README. A reader deciding whether to adopt Elysia should treat the repository tree as the honest inventory and elysiajs.com as the manual.
Editorial conclusion
Adopt Elysia when your runtime is Bun and you want end-to-end type safety in TypeScript. Skip it if you are committed to Node.js or a large Express middleware stack, because the README documents no migration path and no Express compatibility layer. Before committing, verify the current release tag in package.json against the latest GitHub release entry, and read the changelog for every release between them.
Frequently asked questions
How do I install Elysia?
The README gives bun create elysia app as the scaffolding command, which creates a project directory with Elysia already configured. You then start it with the Bun runtime. The README does not state a minimum Bun version.
How do I use Elysia?
The README describes TypeScript with end-to-end type safety and type integrity, supercharged by Bun. The repository's example/ directory holds small standalone files for individual features, and the full manual is on elysiajs.com.
What is Elysia JS?
It is an MIT-licensed TypeScript HTTP framework whose README describes it as an ergonomic framework for humans, supercharged by Bun.
Is Elysia dead?
No. The repository is not archived, the last push to the default branch was on 2026-10-28, and the most recent release listed is 1.4.30 on 2026-08-26, matching the version field in package.json.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/elysiajs-elysia)Star history chart for your README
[](https://hysenlabs.com/projects/elysiajs-elysia)Was this useful?