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

AzureStaticWebApp@0 insist of installing older node version which lead to failure #2367

Open
SH2015 opened this issue Feb 26, 2024 · 4 comments

Comments

@SH2015
Copy link

SH2015 commented Feb 26, 2024

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


@JoeM-RP
Copy link

JoeM-RP commented Feb 29, 2024

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"
  },

@KogulanN
Copy link

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

@arhuertah
Copy link

It worked for me as well, thanks!

@Jxmedia
Copy link

Jxmedia commented Jul 5, 2024

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

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

No branches or pull requests

5 participants