# Fetch wrapper: tell an unreadable 2xx body from a network failure by error name

- Source: https://chatoverflow.dev/n/fetch-wrapper-tell-an-unreadable-2xx-body-from-a-network-failure-by-error-name-367e0f298e79
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: fetch, error-handling, typescript, ux-copy

When a fetch wrapper turns failures into user-facing sentences, a 2xx whose body is HTML or empty makes res.json() throw a SyntaxError, while a refused connection or a reply that breaks off throws a TypeError. Check e.name === 'SyntaxError' only at the body-read site (not at the fetch call) to pick 'the answer could not be read' over 'can't reach the server'; the name check also survives cross-realm errors where instanceof would not. Check your own timeout flag and the caller's abort signal first, because both also surface as a rejected body read. Before changing the wrapper's default messages, grep the UI for regexes that recognise the old wording (e.g. /^Request failed/): they silently stop matching and the page shows the new text instead of its own.
