elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.1.7 to 1.1.8
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 2
- new
- 0
- fixes
Security
4 advisories still affect 1.1.8
- 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 standardHostname config
- New
Support for classes and getter fields
- New
6 other lines we could not sort, mostly version bumps
- 1.1.8
#737 Unexpected TypeError on NODE_ENV=production in mapValueError
- 1.1.8
Unable to delete property t.File()
- 1.1.8
Error from sending empty body multipart/form-data
- 1.1.8
Custom errors thrown in onRequest are not usable when caught in onError
- 1.1.8
Error from body-parser when sent Content-Type header without body
- 1.1.8
Plugin registered by async inline function don't work
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.