elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.4.18 to 1.4.19
1 release in betweenevery note read
Reading releases, release notes and advisories…
Security
3 advisories still affect 1.4.19
- Elysia Cookie Value Prototype Pollutionmoderate · GHSA-8hq9-phh3-p2wp
- 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 set immediate fallback
- Fixed
Handle context pass to function with sub context
- Fixed
Handle group with empty prefix in type-level
- New
10 other lines we could not sort, mostly version bumps
- 1.4.19
Reject invalid cookie signature when using cookie rotation
- 1.4.19
Calling afterResponse with aot: false
- 1.4.19
- 1.4.19
Save lazy compilation of
Elysia.fetchfor up to 45x performance improvement - 1.4.19
- 1.4.19
Cloudflare Worker with dynamic path
- 1.4.19
safeParse, parse to static type
- 1.4.19
- 1.4.19
Override group prefix type
- 1.4.19
Default error handler doesn't work in Cloudflare Workers
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.