Packages

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…

Other targets from 1.0.20Newest 1.x, Latest1.4.32Clears its 4 advisories1.4.29
  1. 1.0.20yours
  2. 1.0.21target
0
changes to make
0
advisories fixed
1
new
0
fixes

Security

4 advisories still affect 1.0.21

Upgrading to 1.4.29 clears them.

Release by release

  1. 1.0.21

    21 May 20241 new
    • New

      Add errors: ValueError to t.type({ error({ errors }) {} })

6 other lines we could not sort, mostly version bumps
  • t.type({ error }) now accepts (error: ({ type, validator, value, errors }) => unknown) instead of (error: (type, validator, value) => unknown)

    1.0.21
  • t.type({ error }) accepts string | number | boolean | Object instead of string

    1.0.21
  • t.type({ error }) return string | number | boolean | Object | void instead of string

    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

    1.0.21

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.