Axios Request Cancellation: Transitioning from CancelToken to AbortController

Answer in a Nutshell

Yes – when you use AbortController in Axios 1.x, the library throws an error that follows the same interception chain as the legacy CancelToken. The error object carries code: 'ERR_CANCELED' and message: 'canceled', which lets your .catch() and response‑interceptor error handlers treat it exactly like a CancelToken rejection.

To differentiate a user‑initiated abort from a network‑level timeout, inspect the err.code (or err.message) that Axios surfaces. A manual abort yields ERR_CANCELED, whereas a timeout or connection failure typically produces ECONNABORTED or ETIMEDOUT depending on the adapter.

Step‑by‑Step Migration

1. Update Axios – ensure axios@^0.22.0 (or newer) is installed.
2. Create a controller – const controller = new AbortController();
3. Attach the signal – pass { signal: controller.signal } in the request config.
4. Abort when needed – call controller.abort();.
5. Handle the error – in .catch() or a response interceptor, check err.code === 'ERR_CANCELED'.
6. Update interceptors – replace any source.token checks with signal.aborted or err.code === 'ERR_CANCELED'.
7. Remove legacy CancelToken usage – delete imports and any fallback logic.

Distinguishing Abort from Timeout

• Manual abort – err.code === 'ERR_CANCELED'
• Timeout / network failure – err.code === 'ECONNABORTED' || err.code === 'ETIMEDOUT'
• Other errors – check err.response or err.request fields for additional context.

What You Still Need to Know

To give a definitive recommendation about adapter‑specific behavior, I’d like to confirm which Axios adapter you’re using (e.g., fetch vs xmlhttprequest). This detail can affect how the abort signal is propagated internally.

Quick Test

const controller = new AbortController();
axios.get('/slow-endpoint', { signal: controller.signal })
  .catch(err => {
    console.log(err.code); // should log 'ERR_CANCELED' after abort
  });
setTimeout(() => controller.abort(), 100);

Run the snippet in your environment and verify the err.code value. If you see anything other than ERR_CANCELED, double‑check the adapter and your Axios version.