BREAKING 0.19 API Errors not populating correctly

API Error breaks existing code. The error object is no longer populated.

To Reproduce catch an error from an api.

Expected behavior I didn’t expect a minor version change to break existing code.

Is there any further guidance or documentation regarding these changes?

• Makes Axios error generic to use AxiosResponse (#1738) - Suman Lama
• Adding isAxiosError flag to errors thrown by axios (#1419) - Ayush Gupta

Environment:

• Axios Version [0.19.0]
• OS: [Windows 10 ]
• Browser [ Chrome ]
• Browser Version [75.0.3770.80 (Official Build) (64-bit)]
• Additional Library Versions [React 16.8.6]

Additional context/Screenshots const apirequest = (options) => { return authService.fetchAccessToken() .then((accessToken) => { if (!options.headers) options.headers = {};

  options.headers['Authorization'] = `bearer ${accessToken}`;

  return client(options)
    .then(response => {
      return response.data;
    })
    .catch(error => { console.error(error); });
});

}

[danielmcq]

Not trying to be pedantic, but you should never expect a module with a major version “0” to have a stable API. Until the author(s) put it at 1, it’s not considered stable. https://semver.org/#spec-item-4

[chinesedfan]

Closed due to lack of enough information and stale. Nobody gives a reproducible code example.