Packages

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…

Other targets from 0.8.17Clears its 4 advisories1.4.29Latest1.4.32
The note of 1.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 0.8.17yours
  2. 1.0.0target
?
changes to make
0
advisories fixed
4
new
1
fix

Security

4 advisories still affect 1.0.0

Upgrading to 1.4.29 clears them.

Release by release

  1. 1.0.0

    16 Mar 20244 new · 1 fix
    • 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

30 other lines we could not sort, mostly version bumps
  • 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 error to handler

    1.0.0
  • Inline error has auto-completion and type checking based on status code

    1.0.0
  • Handler now check return type of error based on status code

    1.0.0
  • Utility Elysia._types for 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.Date now allow stringified date

    1.0.0

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.