●Change8

Migrating to Axios v1.16.0

Version v1.16.0 introduces 3 breaking changes. This guide details how to update your code.

Released: 5/2/2026

3
Breaking Changes
2
Migration Steps
19
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

fetch adapterproxy requestsHost headersBasic auth credentialsparseProtocolunescape()transformRequestQUERY HTTP MethodECONNREFUSEDAxiosErrorencode helperbuildURLbeforeRedirectAbortSignalcancelTokendispatchRequestsettleRawAxiosHeaderscreate

Breaking Changes

●Issue #1

Fetch adapter now enforces `maxBodyLength` and `maxContentLength`. Previously, these limits were silently ignored on the fetch adapter, removing a safety net for DoS protection or large uploads.

●Issue #2

`parseProtocol` now strictly requires a colon in the protocol separator. Strings that loosely parsed as protocols before may no longer match.

●Issue #3

Deprecated `unescape()` usage was replaced with modern UTF-8 encoding. Consumers depending on legacy `unescape()` quirks may see different output bytes due to spec-correct non-ASCII URL handling.

Migration Steps

  1. 1
    Review code that relies on loose protocol parsing in `parseProtocol`; ensure protocols now explicitly contain a colon separator.
  2. 2
    If relying on the previous behavior of the fetch adapter ignoring `maxBodyLength`/`maxContentLength`, update code to respect these limits or remove them if they are no longer desired safety measures.

Release Summary

Version 1.16.0 introduces support for the QUERY HTTP method and the ECONNREFUSED error constant, alongside significant bug fixes across HTTP, fetch, and XHR adapters concerning redirects, headers, and timeouts. Several observable behaviors have changed, particularly around content length enforcement and protocol parsing strictness.

Need More Details?

View the full release notes and all changes for Axios v1.16.0.

View Full Changelog