Ng command ran from angular/cli MCP server is failing on windows.
@amishne ci sta già lavorando.
Dal 4/2/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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
- Lingua principale
- TypeScript
- Stelle
- 27k
- Fork
- 11.8k
- Merge medio
- 16h 35m
- PR unite (30g)
- 176
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di angular/angular-cli
-
area: @angular/build gemini-triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
angular/angular-cli#33955 ·
-
area: @angular/cli gemini-triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
angular/angular-cli#33055 · 1 commento · 3 reazioni ·
-
unit-test: with --coverage, a setup file's hooks reach only the first spec file of each worker Apertaarea: @angular/build gemini-triaged
Difficoltà 4/5 3-5 giorni Idoneità per principianti 72/100
angular/angular-cli#34137 ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 assegnatario ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 assegnatario ·
Tutte le issue di angular/angular-cli
Issue simili
-
Browser Waiting for: Product Owner
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
getsentry/sentry-javascript#24577 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
agilepathway/label-checker#640 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
copse-dev/agent-pane#2953 ·
-
[aw] Upgrade available Apertaagentic-workflows
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
anomalyco/models.dev#7701 ·