Static Web App with Angular Build failed, Node version still v18.20.8

[laurentknafo]

Static Web App with Angular Build failed with Node v24.3.0 and Angular CLI v20.0.4

When creating a Static Web App on Azure with Angular build, it generates this yaml:

Then this error:

[cap10tech]

I'm having a similar issue, I'd even be good with Node 20

[Callum-Thomas-DOJ]

Same here. Tried to add this step before the Oryx build step and it still only picked up Node 18.

    - name: Set up Node.js
      uses: actions/setup-node@v4
      with:
        node-version: '22.18.0'

[valterss]

Similar issue to me building React application with outdated node 18.20.8 while 20.19.0+ is required. Partial output of Build And Deploy job:

Downloading and extracting 'nodejs' version '18.20.8' to '/tmp/oryx/platforms/nodejs/18.20.8'...
Detected image debian flavor: bullseye.
Downloaded in 1 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: nodejs...
Done in 2 sec(s).

Removing existing manifest file
Creating directory for command manifest file if it does not exist
Creating a manifest file...
Node Build Command Manifest file created.

Using Node version:
v18.20.8

Using Npm version:
10.8.2

Running 'npm install'...

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@vitejs/[email protected]',
npm warn EBADENGINE   required: { node: '^20.19.0 || >=22.12.0' },
npm warn EBADENGINE   current: { node: 'v18.20.8', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '[email protected]',
npm warn EBADENGINE   required: { node: '>=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.20.8', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '[email protected]',
npm warn EBADENGINE   required: { node: '^20.19.0 || >=22.12.0' },
npm warn EBADENGINE   current: { node: 'v18.20.8', npm: '10.8.2' }
npm warn EBADENGINE }

added 214 packages, and audited 215 packages in 4s

52 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Running 'npm run build'...

[judeiwuji]

After specify this in package.json the deployment worked.

"engines": { "node": "22.x" }

[Callum-Thomas-DOJ]

After specify this in package.json the deployment worked.

"engines": { "node": "22.x" }

This worked for me as well, thanks @judeiwuji