elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.1.27 to 1.2.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 2
- changes to make
- 0
- advisories fixed
- 7
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.2.0
- Breaking1.2.0
Security
4 advisories still affect 1.2.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
- Breaking
Remove router internal property static.http.staticHandlers
- Breaking
Router history compile now link with history composed
- New
Bun
- New
Web Standard (WinterCG) eg. Deno, Browser
- Breaking
7 other lines we could not sort, mostly version bumps
- 1.2.0
file- Return a file response - 1.2.0
form- Return a formdata response - 1.2.0
server- A port of Bun'sServertype declaration - 1.2.0
Event Listener now infers path parameter automatically based on scope
- 1.2.0
content-lengthnow accept number - 1.2.0
Use 16-degit hexadecimals for
idintrace - 1.2.0
Disable
minifyin production build for better debugging/error reporting
8 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.