#1 — Unnamed cluster cluster
#2 — Unnamed cluster cluster
Support useEvent (async context) in cloudflare workers
preset:cloudflarepending triage
Add cloudflare-workflows preset for durable execution
pending triage
#3 — Unnamed cluster cluster
cache.maxAge and swr are not working
enhancementdiscussioncache
#4 — Unnamed cluster cluster
Use custom runtime environmental variables (instead of NITRO_ prefix)
enhancementdiscussion
Support `updateRuntimeConfig()` to update global runtime config
enhancementdiscussion
Allow access to runtime config from build time (kit)
enhancementpendingdiscussion
Compute runtimeConfig at startup
enhancementdiscussionpending triage
#5 — Unnamed cluster cluster
Types in the Server Utilities example not working
pending triagetypes
Add a way to distinguish between server error/nonerror responses for client types
nuxtpending triagetypes
#6 — Unnamed cluster cluster
`nitro/vite` will break down unocss in `tanstack start RC`
needs reproductionpending triagevite plugin
using `vite-plugin-legacy` with `nitro` breaks build
pending triage
#7 — Unnamed cluster cluster
Support bundling `.node` modules
enhancementworkaround availablep2-nice-to-have
Broken build if a dependency's package.json uses the production export condition
bugneeds investigation
#8 — Unnamed cluster cluster
Unable to use nitro routes types from another package
pending triage
#9 — Unnamed cluster cluster
Nitro `service-worker` preset not working with Nuxt 3
bugneeds reproduction
Security improvement: Static $HOST and $PORT in production build
bugpreset:node-serverpreset:node-clustersecurity
Nuxt 3.7.0 with Nitro 2.6.2 build server cause port problem when deploy on azure app service
bugpreset:azurenuxtnuxt reproduction
#10 — Unnamed cluster cluster
Caching with Nitro `routeRules` breaks server/routes
pending triage
Show error during dev/build when routeRules are missing a leading slash
enhancementroute-rulesp2-nice-to-have
Fallback handler to requests outside of baseURL
enhancementdiscussiondx