elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 0.7.31 to 0.8.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 4
- new
- 0
- fixes
Security
4 advisories still affect 0.8.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 stack trace to plugin checksum configurable by
config.analytic(default to false) - New
resolve: derive after validation - New
mapResponse: custom response mapping - New
Add content-range header to
FileandBlobby default if etag is not used
- New
14 other lines we could not sort, mostly version bumps
- 0.8.0
headersinitialization function - 0.8.0
Static content
- 0.8.0
Default property
- 0.8.0
Error function
- 0.8.0
Lazy query reference
- 0.8.0
Override lifecycle response of
beandaf - 0.8.0
afterHandleno longer early return - 0.8.0
Change validation response to JSON
- 0.8.0
Differentiate derive from
decorator['request']asdecorator['derive'] - 0.8.0
derivenow don't show infer type in onRequest
2 internal lines (docs, tests, tooling) left out.
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.