Ng command ran from angular/cli MCP server is failing on windows.

Offen

#32,407 erstellt am 02.2.2026 1 Kommentar 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

@amishne arbeitet bereits daran.

Seit 04.2.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

area: @angular/cli freq1: low severity3: broken type: bug/fix

Command

version

Is this a regression?

Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

I am just reporting a bug I experienced on windows when trying the new experimental tools of the angular/cli mcp server.

On the latest angular/cli 21.1.2 when using the mcp server with experimental tools like modernize or build the mcp server fails to run the "ng" command on windows.
I don't experience any issues on linux systems.

The ng command is working fine in cmd or powershell with local or global angular/cli installation.

I asked my AI agent for feedback on the actual error and i got this :

{
  "status": "failure",
  "logs": [
    "Process failed with error: spawn ng ENOENT"
  ]
}

It seems to be related to the spawn method not working properly on windows when shell option is set to false.

I hope it helps.

Minimal Reproduction

Use experimental tools with the angular/cli mcp server that involves the ng command with spawn (like modernize or build) on windows.

Exception or Error

{
  "status": "failure",
  "logs": [
    "Process failed with error: spawn ng ENOENT"
  ]
}

Your Environment

Angular CLI       : 21.1.2
Node.js           : 24.12.0
Package Manager   : npm 11.6.2
Operating System  : win32 x64

Anything else relevant?

No response

Vorherrschende Sprache: TypeScript
Sterne: 27k
Forks: 11.8k
Ø Merge: 16 Std. 35 Min.
Gemergte PRs (30 T.): 176

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus angular/angular-cli

Can't use an array of hostnames in --allowedHosts cli parameter in @angular/build:dev-server Offen

area: @angular/build gemini-triaged

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100

angular/angular-cli#33955 · Erstellt am 28.8.2026
Allow tests to pass without any test files (e.g. via Vitest `passWithNoTests`) Offen

area: @angular/cli gemini-triaged

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

angular/angular-cli#33055 · 1 Kommentar · 3 Reaktionen · Erstellt am 26.4.2026
unit-test: with --coverage, a setup file's hooks reach only the first spec file of each worker Offen

area: @angular/build gemini-triaged

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 72/100

angular/angular-cli#34137 · Erstellt am 21.9.2026
library builder: tslib is not added to the output package.json Offen

angular/build:library area: @angular/build gemini-triaged

angular/angular-cli#34131 · 1 zugewiesene Person · Erstellt am 20.9.2026
library builder: a name re-exported through two "export *" paths is dropped from the bundle Offen

angular/build:library area: @angular/build gemini-triaged

angular/angular-cli#34130 · 1 zugewiesene Person · Erstellt am 20.9.2026

Alle Issues in angular/angular-cli