elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.0.0 to 1.0.1
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 1
- fix
Security
4 advisories still affect 1.0.1
- Elysia Cookie Value Prototype Pollutionmoderate · GHSA-8hq9-phh3-p2wp
- Elysia affected by arbitrary code injection through cookie confighigh · GHSA-8vch-m3f4-q8jf
- elysia has Inefficient Algorithmic Complexity and Interpretation Conflicthigh · GHSA-9643-4qgh-g8mx
- Elysia has a string URL format ReDoShigh · GHSA-f45g-68q3-5w8x
Upgrading to 1.4.29 clears them.
Release by release
- Fixed
Handle
return errorontransform
- Fixed
7 other lines we could not sort, mostly version bumps
- 1.0.1
mapHandlernow check passthrough once instead of twice - 1.0.1
Exclude return type of
ELYSIA_RESPONSEtype fromderiveandresolve - 1.0.1
Throw error if
erroris return inderiveandresolve - 1.0.1
Merge response schema from parent scope
- 1.0.1
Explicit
type: 'json'with body schema throw unexpectedbody.Checkis not a function - 1.0.1
Await the .modules of nested Elysia instances
- 1.0.1
Accessing all query params using property name (ctx.query) doesn't work anymore
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.