Pattern: Which Angular dev-server executor should be used for apps th...

Documentation for Sessions

🎨 Pattern: Which Angular dev-server executor should be used for apps th...

Date: 2026-02-05
Time: 04:58:18 UTC
Session: editor2-91.5
Agent: angular
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

Which Angular dev-server executor should be used for apps that need proxy support?

Task: Standardize dev-server executor across apps

🎯 Decision Made

Chosen:

Use @angular-devkit/build-angular:dev-server for all apps requiring proxy support

Options Considered:

@angular/build:dev-server (new Application Builder)
@angular-devkit/build-angular:dev-server (traditional)
Mix of both depending on app

💭 Reasoning

CRITICAL: When creating new Angular apps that need to proxy API calls to a backend, ALWAYS use @angular-devkit/build-angular:dev-server executor. The newer @angular/build:dev-server (Application Builder) has known issues with proxyConfig handling where requests return 404 instead of being proxied. All apps in our workspace (gograb-space, gograb-admin, gograb-dev) should use the same executor for consistency and to ensure proxy works correctly. Include host: localhost, hmr: true, liveReload: true in options for optimal DX.

📁 Files Involved

apps/gograb-space/project.json
apps/gograb-admin/project.json
apps/gograb-dev/project.json

🔗 Related

Decision ID: dev_1770267498621_fhfhhiv
Session: 91
Workspace: editor2

Auto-generated by MCP Smart Consolidation