spawn gcloud ENOENT

[ibrahimxcool]

Version info

Angular: 12.2.15

Firebase: 9.4.0

AngularFire: 7.2.0

nguniversal/express-engine: 12.1.3

Problem

On installing Angular fire with ng add @angular/fire and choosing Cloud Run for my SSR. It gives me an error when running ng deploy .

✔ Prerendering routes to C:\Users\x\Desktop\my-project\dist\my-project\browser complete.
📦 Deploying to Cloud Run
Error when trying to deploy:
spawn gcloud ENOENT

Where I think the problem lies is at dist/my-project/run/package.json

{
  "name": "functions",
  "description": "Angular Universal Application",
  "main": "dist\\my-project\\server\\main.js",
  "scripts": {
    "start": "node dist\\my-project\\server\\main.js"
  },
  "engines": {
    "node": "16.13"
  },
  "dependencies": {},
  "devDependencies": {},
  "private": true
}

Where it should be a single slash \ instead of a double slashes \\

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.

[vladimir-barsuchenko]

@ibrahimxcool How did you end up resolving this issue?

[fr-esco]

Same problem here on Windows.

I put gcloud in the Path variable and logged in. Then made sure that gcloud works if called from PowerShell, Command line and Git bash. Bt it still seems unavailable to this schematic run process...

[DavidWeiss2]

Same here

[fr-esco]

Just created a PR with a fix for Windows users.

[walterjjoyce]

I found a similar historical Windows issue in AngularFire where spawn gcloud ENOENT was not caused by gcloud being missing, but by Windows child-process/env handling. That thread included a later fix described as “give child processes proper access to env.”

My repro looks similar:

• gcloud version works in PowerShell
• where.exe gcloud finds the binary
• Node spawn('gcloud', ...) fails with ENOENT
• Node spawn('gcloud.cmd', ..., { shell: true }) works

This suggests the OpenClaw Windows path may need different child_process handling for gcloud.