elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 0.7.26 to 0.7.27
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 0
- fixes
Security
4 advisories still affect 0.7.27
- 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.
13 other lines we could not sort, mostly version bumps
- 0.7.27
Default params type suggestion for WebSocket
- 0.7.27
Preserve original hostname when using
.mount() - 0.7.27
T.RegExp doesn't work due to requiring default value
- 0.7.27
T.Numeric should not convert empty string to 0
- 0.7.27
Elysia({ scoped: true }) should still expose defined routes on type level
- 0.7.27
Using a hook/guard/schema with a handler function and request without body results in a "Unexpected end of JSON input"-error
- 0.7.27
Missing request.path parameter in .onRequest
- 0.7.27
Ability to localize TypeBox errors
- 0.7.27
onError handler has error property as undefined on Cloudflare Workers
- 0.7.27
T.Numeric not validating properly
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.