nitropack
2.13.6 · 2 Nov 2026MIT3.9M / weekRepositoryHomepagenpmAtom feed
2.13.6 is the newest release of 2.x.
In short
12 new1 faster6 fixed14 internal
Security
2 advisories affect 2.4.0; 2.13.4 fixes them
- ModerateNitro has an Open Redirect via Protocol-Relative URL Bypass in Wildcard Route RulesGHSA-9phm-9p8f-hw5m · 6 May 2026Fixed in 2.13.4
- ModerateNitro has a proxy scope bypass via percent-encoded path traversal in `routeRules`GHSA-5w89-w975-hf9q · 6 May 2026Fixed in 2.13.4
Release note
How to Upgrade?
If you are directly using Nitro, make sure to recreate lockfile as well in order to receive all UnJS ecosystem updates.
If you are using Nitro via Nuxt, simply use npx nuxi@latest upgrade --force.
What is new?
isr route rule
Vercel and Netlify route rules support a dedicated isr flag to enable Incremental Static Regeneration.
For backward compatibility, we keep converting swr and static route rules to isr for these two presets. If you were previously depending on swr and static route rules, we highly recommend to upgrade nitro and switch to isr flag:
routeRules: {
-- '/blog/**': { swr: 3000 },
++ '/blog/**': { isr: 3000 },
}If you like to leverage Nitro Native SWR cache (stored in storage), you can opt-in using future.nativeSWR: true (nuxt: nitro.future.nativeSWR) config.
Vercel KV Storage
In collaboration with the Vercel team, Nitro now supports seamless integration with Vercel KV Store. See docs for usage information.
Cloudflare Module Worker Preset
You can opt-in to the new Cloudflare Module Worker output format.
The cloudflare pages preset is also upgraded to the worker format with this release
First-class static targets
While Nitro is a server builder, it can be also used to prerender all routes using a renderer and output only static output. New static ,vercel-static, netlify-static and github-pages presets are now available to only output prerender and skip the production server build.
Config HMR support
You can now directly edit route rules and runtime config within nitro.config without the need to restart the nitro server! See #1175 for more information.
Dynamic App Config and Runtime Config
Previously, both useAppConfig() and useRuntimeConfig() were returning a frozen object. Now using useAppConfig(event) and useRuntimeConfig(event) you can have a fully dynamic interface, enabling dynamic, per-request config and support for environments such as Cloudflare where env is only available during the request lifecycle.
If you were previously using useAppConfig() and useRuntimeConfig() in an ambient context (outside of event handlers and composable functions, we highly recommend to migrate to the new API:
-- const appConfig = useAppConfig()
export default eventHandler(event => {
++ const appConfig = useAppConfig(event)
})See #1154 for more information.
Experimental Swagger and Open API support
Swagger and OpenAPI are de facto standard tools for documenting server API routes. You can now see all auto-generated API docs by enabling experimental.openAPI: true (nuxt: nitro.experimental.openAPI: true) and opening /_nitro/swagger UI.
See #1162 for more information.
We are working to bring route-level meta definition for an even better and more detailed docs generator.
New Documentation and Branding
Nitro docs and logo are live with a new fancier design at nitro.unjs.io
Enhancements
Add Cloudflare module worker support
vercel, netlify: Introduce
isrroute ruleAdd
staticpresetAdd
vercel-staticandnetlify-staticpresetsAdd
github-pagespresetPass resolved config to
rollup:beforehookConfig reload support for
nitro devConfig hmr support for
routeRulesandrutimeConfigSupport dynamic app config and runtime config
Experimental
/_nitro/openapi.jsonand/_nitro/swaggerfor dev modevercel: Add support for specifying edge regions
future.nativeSWR
Performance
Export
defineNitroConfigfromnitro/config
Fixes
Separate
typesDirfromtsConfigDircloudflare: Expose env from module context
proxy: Append request query params for single proxy route rules
vercel, netlify: Keep default behavior for
staticandswrtoisrmappingApply
chunkFileNameson windowspkg: Allow installing on node v20 and above
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.