You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reproduction is not available now, because I fixed it by replacing node:16 with node:18.
Describe the bug
When using Azure Static Web Apps as a hosting provider for the app which uses server folder for routes / middleware, and you are using there $fetch with default preset for Azure Functions runtime, which is node:16, you encountered an error, that _fetch is not available.
It is caused by major update in Nitro 2.7, which uses native fetch for fetch requests (#1724) which is only supported in node engines 18+.
It would be great to replace default node:16 value for apiRuntime Azure property with node:18 which is still in public preview, however instead of errors responses, fetch requests will start work on Azure Static Web Apps.
Also, after update, it needs to be replaced in docs for Azure preset.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Nitro v2.7
Nuxt v3.8.0
Reproduction
Reproduction is not available now, because I fixed it by replacing
node:16
withnode:18
.Describe the bug
When using Azure Static Web Apps as a hosting provider for the app which uses
server
folder for routes / middleware, and you are using there$fetch
with default preset for Azure Functions runtime, which isnode:16
, you encountered an error, that_fetch is not available
.It is caused by major update in Nitro 2.7, which uses native
fetch
for fetch requests (#1724) which is only supported in node engines 18+.It would be great to replace default
node:16
value forapiRuntime
Azure property withnode:18
which is still in public preview, however instead of errors responses, fetch requests will start work on Azure Static Web Apps.Also, after update, it needs to be replaced in docs for Azure preset.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: