AzureStaticWebApp@0 insist of installing older node version which lead to failure
SH2015 opened this issue · 4 comments
Bug Report
-
At what date and time did you most recently experience the problem? 2024 /02/24
-
Where did you experience the problem? E.g. Azure Web Apps, Azure Functions, Azure Container Registry, or offline use.
Azure Static Web App step in pipeline -
If your repo is publicly available please share its URL:
no -
What happened?
the deployment of SWA is failing because the required node version is not installed. and it seem this is not the version for pipeline agent but the version of container that this step creates -
What did you expect or want to happen?
to pass this step successfully -
How can we reproduce it?
create angular app with the latest version and enable ssr , but keep in mind I am only diploying the "browser" folder from dist which mean only static files -
Do you have log output? Please include between the backticks:
yes
log9.txt
As a workaround, you can add this block to the project package.json
- worked for me after facing the same issue this week.
"engines": {
"node": "18.19.1"
},
As a workaround, you can add this block to the project
package.json
- worked for me after facing the same issue this week."engines": { "node": "18.19.1" },
:Working
It worked for me as well, thanks!
As a workaround, you can add this block to the project
package.json
- worked for me after facing the same issue this week."engines": { "node": "18.19.1" },
:Working
This worked for me as well