Bugfix: Why is the proxy not working for gograb-admin and gograb-dev...

Documentation for Sessions

🐛 Bugfix: Why is the proxy not working for gograb-admin and gograb-dev...

Date: 2026-02-05
Time: 04:58:09 UTC
Session: editor2-91.4
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Why is the proxy not working for gograb-admin and gograb-dev apps, causing 404 errors on API calls?

Task: Fix proxy configuration for gograb-admin authentication

🎯 Decision Made

Chosen:

Changed the serve executor from @angular/build:dev-server to @angular-devkit/build-angular:dev-server

Options Considered:

Keep using @angular/build:dev-server with different config
Change to @angular-devkit/build-angular:dev-server (same as gograb-space)
Create custom proxy middleware

💭 Reasoning

The new Angular Application Builder's dev-server (@angular/build:dev-server) handles proxyConfig differently than the traditional dev-server (@angular-devkit/build-angular:dev-server). When using the new builder, proxy requests were returning 404 'Cannot POST /api/auth/login' errors instead of being forwarded to the backend. Testing confirmed that gograb-space (using the traditional builder) correctly proxied requests while gograb-admin/dev (using the new builder) did not. The fix was to align all apps to use the same executor that's known to work with proxyConfig.

📁 Files Involved

apps/gograb-admin/project.json
apps/gograb-dev/project.json
libs/libs-foundational/api-config/proxy.conf.json

🔗 Related

Decision ID: dev_1770267489113_kd52yvg
Session: 91
Workspace: editor2

Auto-generated by MCP Smart Consolidation