Is the breaking change in the type definition of AxiosError as intended?

Describe the bug

The definition of AxiosError had been updated at v0.27.0.

https://github.com/axios/axios/pull/3645/files#diff-7aa4473ede4abd9ec099e87fec67fd57afafaf39e05d493ab4533acc38547eb8L124-R124

It seems compatible with the previous code, but this changeset is not based on #4186.

In v0.26.1, AxiosError defined as <T = any, D = any> extends Error.

https://github.com/axios/axios/blob/v0.26.1/index.d.ts#L139

As a result, AxiosError has a different type definition than AxiosPromise or AxiosResponse. The former <T=unknown>, the latter <T=any>. I think these inconsistent definitions are undesirable.

It seems to me that this breaking change is unintentional, isn’t it?

To Reproduce

if (axios.isAxiosError(e)) {
  console.log(e.response.data.message)
}

Got an error on e.response.data.

Object is of type ‘unknown’.ts(2571)

Expected behavior

No errors occur.

Environment

• Axios Version: 0.27.2

[dimbslmh]

The following seems to work with v0.27:

if (e instanceof AxiosError) {
  console.log(e.response.data.message)
}

[martinfoakes]

If this is intentional behaviour then what is the preferred way of handling these error responses? Currently I have an app that frequently accesses the response data/messages for error logging and error message displaying, like so:

...
  } catch (e) {
    if (axios.isAxiosError(e)) {
      datadogLogs.logger.error(e.response?.data);
      message.error(e.response?.data?.message);
    }
  }