nitropack
2.13.6 · 2 Nov 2026MIT3.9M / weekRepositoryHomepagenpmAtom feed
Upgrading nitropack From 0.2.3 to 0.6.1
53 releases in betweennotes for 3
Reading releases, release notes and advisories…
- 10+
- changes to make
- 0
- advisories fixed
- 29+
- new
- 31+
- fixes
Counted from 3 of 53 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking0.6.0
- Breaking0.6.0
- Breaking0.6.0
- Breaking0.5.0
- Breaking0.5.0
- Breaking0.5.0
- Breaking0.5.0
- Breaking0.5.0
- Breaking0.4.0
- Breaking0.4.0
Security
2 advisories still affect 0.6.1
- Nitro has a proxy scope bypass via percent-encoded path traversal in `routeRules`moderate · GHSA-5w89-w975-hf9q
- Nitro has an Open Redirect via Protocol-Relative URL Bypass in Wildcard Route Rulesmoderate · GHSA-9phm-9p8f-hw5m
Upgrading to 2.13.4 clears them.
Release by release
0.6.1no release note
- Breaking
H3 updated to to 0.8x [Release Notes]
- Breaking
Experimental
routesis renamed torouteRules - Breaking
⚠️ Rename routeOptions to routeRules
- New
Support
redirect,headers, andcorsroute rules
- Breaking
0.5.1 – 0.5.44 releases, no release note
- Breaking
⚠️ Update unenv to 0.6.x
- Breaking
externals: ⚠️ Fall back to
mllyresolver in more cases - Breaking
⚠️
NITRO_PRESETshould have the highest priority - Breaking
⚠️ Rename options
autoImporttoimports
- Breaking
0.4.1 – 0.4.2424 releases, no release note
- Breaking
⚠️ 7e72b8f Only accept event handler for
defineCachedEventHandler - Breaking
⚠️ #166 Write html files to subfolder (resolves )
- New
Expose all assets to
nitro.vfsand/_vfsendpoint (resolves ) - New
Universal
import.meta(resolves )
- Breaking
0.2.4 – 0.3.1221 releases, no release note
17 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.