elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.4.19 to 1.4.20
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 3
- new
- 0
- fixes
Security
3 advisories still affect 1.4.20
- 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
ModelValidator.schemafor accessing raw schema - New
Add
subscriptionstoElysia.wscontext - New
Add null check for object properties (t.Record)
- New
6 other lines we could not sort, mostly version bumps
- 1.4.20
Unref Sucrose gc
- 1.4.20
Use constant-time comparison for signed cookie verification
- 1.4.20
compose: ReferenceError: "_r_r is not defined" when onError returns plain object & mapResponse exists
- 1.4.20
Update Exact Mirror to 0.2.6
- 1.4.20
Enforce fetch to return MaybePromise<Response>
- 1.4.20
Elysia.modelsbroke when referencing non typebox model
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.