Native Fetch is available in modern Node.js, making it possible to reduce an HTTP dependency in some backend projects. The migration is still a behavioral change: Fetch and Axios do not represent errors, timeouts, headers, and parsed responses in exactly the same way.
The safest strategy is to keep a stable application-facing HTTP client and replace the implementation behind it. Controllers and services should not need to know which low-level library sends the request.
Normalize the differences
Fetch does not reject the promise for every non-2xx response, so the wrapper must check response.ok and throw a consistent application error. Add AbortController-based timeouts, central header injection, and explicit JSON parsing before moving callers.
- Map network, timeout, HTTP, and parsing errors separately.
- Preserve request IDs and tracing headers.
- Define retry rules only for safe, repeatable operations.
Migrate by integration, not by file count
Move one external service at a time and compare request payloads, status handling, and logs in staging. This provides a clear rollback point and avoids changing every integration before the wrapper has been proven under real conditions.
Native Fetch can simplify the dependency graph, but the real engineering value comes from a well-defined HTTP boundary that keeps transport details away from business logic.