Axios advantages over fetch

WHAT THIS TESTS Whether you understand fetch's default behavior and can articulate concrete ergonomic and reliability gains from Axios, rather than preferring it by habit.

A GOOD ANSWER COVERS fetch resolves the promise for any HTTP response, including 404 and 500, and rejects only on network-level failures, so you must manually inspect response.ok and explicitly parse with await response.json(). Axios automatically serializes request bodies and parses JSON responses into response.data, and it rejects the promise for non-2xx statuses, so a single catch handles HTTP errors. Axios also provides interceptors to attach auth tokens or log centrally, a built-in timeout option, request cancellation, automatic retries via plugins, and createable instances with a baseURL and default headers. These reduce repetitive boilerplate across a React Native codebase.

COMMON WRONG ANSWERS Saying fetch rejects on 4xx or 5xx, claiming fetch cannot set headers or send JSON, or asserting Axios is mandatory. Overlooking that fetch can now cancel via AbortController, narrowing one historical Axios advantage, also shows shallow knowledge.

LIKELY FOLLOW-UPS How do you replicate Axios interceptors with a fetch wrapper? When is fetch preferable to avoid an extra dependency? How does Axios handle timeouts compared with AbortController?

ONE CONCRETE EXAMPLE With fetch you write const res = await fetch(url); if (!res.ok) throw new Error(res.status); const data = await res.json();. With Axios the same call is const { data } = await axios.get(url);, and a 500 automatically lands in catch. An interceptor configured once injects the bearer token into every request, eliminating the need to set the Authorization header on each call manually.