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
Is your feature request related to a problem? Please describe.
The current build process for Azure Static Web Apps uses Node.js version 16.20.2, but Next.js requires a minimum version of 18.17.0. This results in build failures for Next.js-based applications deployed to Azure Static Web Apps.
Describe the solution you'd like
I would like to request that the build process for Azure Static Web Apps be updated to use Node.js version 18 + (or the latest LTS version) when building Next.js applications. This would allow Next.js-based applications to be successfully built and deployed to Azure Static Web Apps without encountering version incompatibility issues.
Describe alternatives you've considered
As a workaround, I've found 2 solutions that work:
I've added a step to my GitHub Actions workflow to manually set the Node.js version to 18 before running the build.
I've specified the Node version I require in my package.json file with the engines property.
"engines": {
"node": ">=18.7.1"
}
Both solutions resolve the issue, but it would be better if the build process handled this automatically for all Next.js-based applications.
Additional context
Successful Build after the workarounds above:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current build process for Azure Static Web Apps uses Node.js version 16.20.2, but Next.js requires a minimum version of 18.17.0. This results in build failures for Next.js-based applications deployed to Azure Static Web Apps.
Describe the solution you'd like
I would like to request that the build process for Azure Static Web Apps be updated to use Node.js version 18 + (or the latest LTS version) when building Next.js applications. This would allow Next.js-based applications to be successfully built and deployed to Azure Static Web Apps without encountering version incompatibility issues.
Describe alternatives you've considered
As a workaround, I've found 2 solutions that work:
package.json
file with theengines
property.Both solutions resolve the issue, but it would be better if the build process handled this automatically for all Next.js-based applications.
Additional context
Successful Build after the workarounds above:
The text was updated successfully, but these errors were encountered: