@jasonsaayman Could you also have a look at this please? 😃

I’m also tagging @TimWolla because of their involvement in #2797

This forces TypeScript users to use objects whose values are strings as headers. I.e., currently the following is allowed:

import axios from 'axios';

axios.post('', {}, { headers: 'Invalid' })
axios.post('', {}, { headers: 13 })
axios.post('', {}, { headers: [] })
axios.post('', {}, { headers: { authorization: [] } })
// etc…

This changes the types, so only proper authorization headers are allowed, and the response header types are correct as well.

import axios from 'axios';

axios.post('', {}, { headers: { authorization: 'A string :)' } })

I don’t consider this to be a breaking change, as it still works the same for proper usage.