elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
1.4.32 is the newest release of 1.x.
In short
1 new2 fixed8 changed
Security
5 advisories affect 1.4.6; 1.4.29 fixes them
- CriticalElysia vulnerable to prototype pollution with multiple standalone schema validationGHSA-hxj9-33pp-j2cc · 9 Dec 2025Fixed in 1.4.17
- 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
What's changed
Improvement:
Strictly check for 200 inline status code
Coerce union status value and return type
Add
BunHTMLBundleLiketo Elysia inline handlerPrevent Elysia from being a dependency of itself
Check if object is frozen before merging, add try-catch to prevent crash
Guard doesn't apply scoped/global schema to object macro
DELETE doesn't inherit derive/resolve type
Change:
onTransform now doesn't include type as it isn't validated yet, creating confusion
Bug fix:
Handle union derive/resolve property
Probably fix mergeDeep attempted to assign to readonly property
derive/resolve inherit type in inline handler
In 1.4.5, we accidentally published Elysia as a dependency of beta Elysia, causing an unexpected debug log
We have fixed that and add a dependency check in the build pipeline to prevent that from happening again
so sowwy 'bout that 👉👈
Me (literally) asking you for forgiveness
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.