elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.0.22 to 1.0.23
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 1
- new
- 0
- fixes
Security
4 advisories still affect 1.0.23
- 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
- New
Add
toResponsefor mapping custom response
- New
7 other lines we could not sort, mostly version bumps
- 1.0.23
Object encoding in query parameters
- 1.0.23
Set correct normalization behavior for addtional properties
- 1.0.23
Cookie decode value might be null
- 1.0.23
"default" option is not being applied on validation
- 1.0.23
Ctx.query doesn't work in some case
- 1.0.23
Aot does not recognize the use of ctx.body within a try catch
- 1.0.23
Accessing ctx.query directly breaks the object
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.