Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure preset should use node 18 for apiRuntime #1872

Closed
DaDlugosch opened this issue Oct 31, 2023 · 3 comments · Fixed by #2077
Closed

Azure preset should use node 18 for apiRuntime #1872

DaDlugosch opened this issue Oct 31, 2023 · 3 comments · Fixed by #2077

Comments

@DaDlugosch
Copy link

DaDlugosch commented Oct 31, 2023

Environment

Nitro v2.7
Nuxt v3.8.0

Reproduction

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

@pi0
Copy link
Member

pi0 commented Jan 16, 2024

Default is upgraded in nightly channel and will change in next Nitro release 👍🏼

@gps-lasrol
Copy link

@pi0 you know when the next release is planned for?

@pi0
Copy link
Member

pi0 commented Jan 29, 2024

This week as planed. You can use nightly channel btw in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants