elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
0.8.17 is the newest release of 0.7.x.
In short
13 changed
Security
4 advisories affect 0.7.27; 1.4.29 fixes them
- Highelysia has Inefficient Algorithmic Complexity and Interpretation ConflictGHSA-9643-4qgh-g8mx · 23 Sep 2026Fixed in 1.4.29
- HighElysia has a string URL format ReDoSGHSA-f45g-68q3-5w8x · 10 Mar 2026Fixed in 1.4.26
- HighElysia affected by arbitrary code injection through cookie configGHSA-8vch-m3f4-q8jf · 9 Dec 2025Fixed in 1.4.18
- ModerateElysia Cookie Value Prototype PollutionGHSA-8hq9-phh3-p2wp · 17 Mar 2026Fixed in 1.4.27
Release note
Bug fix:
Default params type suggestion for WebSocket
Preserve original hostname when using
.mount()T.RegExp doesn't work due to requiring default value
T.Numeric should not convert empty string to 0
Elysia({ scoped: true }) should still expose defined routes on type level
Using a hook/guard/schema with a handler function and request without body results in a "Unexpected end of JSON input"-error
Missing request.path parameter in .onRequest
Ability to localize TypeBox errors
onError handler has error property as undefined on Cloudflare Workers
T.Numeric not validating properly
Status codes of the error classes don't match the response through onError
Plugin hierarchy messes up derive function in child plugin
Websocket definition in groups
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.