Ng command ran from angular/cli MCP server is failing on windows.
@amishne já está trabalhando nisso.
Desde 4/2/2026.
Avaliação
Esta issue ainda não foi avaliada.
Descrição
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
- Linguagem predominante
- TypeScript
- Estrelas
- 27k
- Forks
- 11.8k
- Merge médio
- 16h 35min
- PRs com merge (30d)
- 176
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de angular/angular-cli
-
area: @angular/build gemini-triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
angular/angular-cli#33955 ·
-
area: @angular/cli gemini-triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
angular/angular-cli#33055 · 1 comentário · 3 reações ·
-
unit-test: with --coverage, a setup file's hooks reach only the first spec file of each worker Abertaarea: @angular/build gemini-triaged
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 72/100
angular/angular-cli#34137 ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 responsável ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 responsável ·
Todas as issues de angular/angular-cli
Issues semelhantes
-
Browser Waiting for: Product Owner
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
getsentry/sentry-javascript#24577 · 1 comentário ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
agilepathway/label-checker#640 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
copse-dev/agent-pane#2953 ·
-
[aw] Upgrade available Abertaagentic-workflows
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
anomalyco/models.dev#7701 ·