elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 0.8.17 to 1.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
Security
4 advisories still affect 1.0.0
- 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
mapResolve - New
Add
{ as: 'global' | 'scoped' | 'local' }to lifecycle event - New
Add ephemeral type
- New
Add test case for all life-cycle
- Fixed
Resolve, mapResolve, derive, mapDerive use ephemeral type to scope down accurately
- New
30 other lines we could not sort, mostly version bumps
- 1.0.0
fine-grained reactive cookie
- 1.0.0
Using single source of truth for cookie
- 1.0.0
Macro support for websocket
- 1.0.0
Inline
errorto handler - 1.0.0
Inline
errorhas auto-completion and type checking based on status code - 1.0.0
Handler now check return type of
errorbased on status code - 1.0.0
Utility
Elysia._typesfor types inference - 1.0.0
Provide user friendly error for failed parse
- 1.0.0
Handler now infers return type for error status for Treaty
- 1.0.0
t.Datenow allow stringified date
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.