P1: Frontend api.js does not handle CORS errors — generic error message shown #10

Open
opened 2026-05-13 20:39:37 -05:00 by null · 0 comments
Owner

Severity: P1 — High

File: src/lib/api.js ~line 8

Problem: If CORS blocks a request, fetch() throws TypeError but frontend catches it as a generic error. No distinction between network errors, CORS failures, and backend errors.

Impact: Developer confusion when CORS is misconfigured in production.

Fix: Add specific error type detection and user-friendly messages for CORS/network errors.

## Severity: P1 — High **File:** src/lib/api.js ~line 8 **Problem:** If CORS blocks a request, fetch() throws TypeError but frontend catches it as a generic error. No distinction between network errors, CORS failures, and backend errors. **Impact:** Developer confusion when CORS is misconfigured in production. **Fix:** Add specific error type detection and user-friendly messages for CORS/network errors.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: null/Queue-North-Website#10
No description provided.