elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.3.6 to 1.3.7
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.3.7
- 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 property starts witha number
- Fixed
7 other lines we could not sort, mostly version bumps
- 1.3.7
Coerce TransformDecodeError to ValidationError
- 1.3.7
onRequest not firing
- 1.3.7
webSocket fails to connect when inside group and guard
- 1.3.7
Encode is not called when using dynamic handler
- 1.3.7
Remove response body from HTTP 101, 204, 205, 304, 307, 308
- 1.3.7
Update exact mirror to 0.1.3
- 1.3.7
Warn when stop is called instead of throwing an error
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.