#1 — Unnamed cluster cluster
Nuxt 3.7.0 with Nitro 2.6.2 build server cause port problem when deploy on azure app service
bugpreset:azurenuxtnuxt reproduction
#2 — Unnamed cluster cluster
Websocket does not work in vite dev mode with bun runtime
bunv3vite plugin
#3 — Unnamed cluster cluster
Caching with Nitro `routeRules` breaks server/routes
pending triage
Add a way to distinguish between server error/nonerror responses for client types
nuxtpending triagetypes
#4 — Unnamed cluster cluster
Use custom runtime environmental variables (instead of NITRO_ prefix)
enhancementdiscussion
Runtime config null/undefined values not overwritten by .env values
enhancementdiscussion
Support `updateRuntimeConfig()` to update global runtime config
enhancementdiscussion
#5 — Unnamed cluster cluster
Strange netlify deployment issues and bugs with monorepo
preset:netlifypending triagenuxt reproduction
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
#6 — Unnamed cluster cluster
cache.maxAge and swr are not working
enhancementdiscussioncache
#7 — Unnamed cluster cluster
Support bundling `.node` modules
enhancementworkaround availablep2-nice-to-have
#8 — Unnamed cluster cluster
Disallow `prerender: true` route rule for route rules having `*`
enhancementtypes
Fallback handler to requests outside of baseURL
enhancementdiscussiondx
Expose handlers list through the useNitroApp
enhancementdiscussion
#9 — Unnamed cluster cluster
Support useEvent (async context) in cloudflare workers
preset:cloudflarepending triage
Server Timing Should Be Configurable At Runtime
enhancementtiming
#10 — Unnamed cluster cluster
Experimental decorators support
enhancementworkaround available