Axios Request Cancellation: Migration Timing from CancelToken to AbortSignal in v0.22.0+

Migration Strategy and Error Handling

For a codebase pinned to Axios 0.x planning an upgrade to 1.x, the migration from CancelToken to AbortSignal should be timed with the major version upgrade itself. Because CancelToken remains available (though deprecated) in 1.x, there is no immediate breaking change forcing a migration. However, migrating during the 1.x transition prevents the accumulation of technical debt and allows you to leverage native browser/Node.js AbortController features.

Migration Criteria

Prioritize the migration to AbortSignal if any of the following apply:

• Upgrade Timeline: You are currently executing the jump from 0.x to 1.x.
• Feature Requirements: You need AbortSignal.timeout() for standardized deadline control across different request types.
• Runtime Modernization: Your target environments (Browser or Node.js) natively support AbortController, removing the need for Axios-specific cancellation logic.
• Code Cleanup: You are refactoring search-as-you-type or polling logic and want to move away from deprecated APIs.

Cross-Version Error Handling

To identify cancellations reliably across both 0.x and 1.x without checking for version-specific error codes (like ERR_CANCELED) or specific class instances (like CanceledError), use the built-in axios.isCancel() helper.

This method is designed to abstract the underlying error shape, returning true regardless of whether the request was canceled via a legacy CancelToken or a modern AbortSignal.

try {
  const response = await axios.get('/api/data', { signal: controller.signal });
} catch (err) {
  if (axios.isCancel(err)) {
    // Handle cancellation (e.g., ignore in search-as-you-type)
    console.log('Request canceled');
  } else {
    // Handle actual API or network errors
    handleError(err);
  }
}

Distinguishing Cancellations from Timeouts

It is critical to separate axios.isCancel() from timeout logic. While AbortSignal.timeout() triggers a cancellation, standard Axios timeout configurations produce different rejection shapes (typically ECONNABORTED). Treat isCancel() as a signal to ignore the request, while treating timeouts as a failure state that may require a retry or a user notification.

Verification Step: To confirm behavior before upgrading, run a test case that triggers a cancellation in your current 0.x environment and verify that axios.isCancel(err) returns true. Ensure your runtime supports AbortController or include a polyfill before switching to signal.