elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.0.20 to 1.0.21
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 1
- new
- 0
- fixes
Security
4 advisories still affect 1.0.21
- 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
errors: ValueErrortot.type({ error({ errors }) {} })
- New
6 other lines we could not sort, mostly version bumps
- 1.0.21
t.type({ error })now accepts(error: ({ type, validator, value, errors }) => unknown)instead of(error: (type, validator, value) => unknown) - 1.0.21
t.type({ error })acceptsstring | number | boolean | Objectinstead ofstring - 1.0.21
t.type({ error })returnstring | number | boolean | Object | voidinstead ofstring - 1.0.21
Redirect doesn't work with
aot: false - 1.0.21
Cookie schema validation doesn't work with
aot: true - 1.0.21
Highlight derive and resolve when using
onError
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.