fix problem with named export axios

[akphi]

Instructions

Fixes #5101

I also chucked in a small fix for the default export to work with NodeNext, a bit of context here

microsoft/TypeScript#49298
microsoft/TypeScript#50690

Basically, I will make it so people can import axios as a named import rather than having to do something like:

import { default as axios } from 'axios';

---

UPDATE: I saw you have already taken care of #5101 by updating exports in package.json, but the problem with named exports remains. Please see my repro here akphi/issue-repo#12

I don't think import { axios } from 'axios'; work at all.

[akphi]

@jasonsaayman is there anything else you need me to do/explain?

[jasonsaayman]

Looks good 👍

[jasonsaayman]

Actually, this should not be necessary you can already do this:

import { axios } from 'axios';

[akphi]

Please see my updated PR description. You can check out my repro at akphi/issue-repo#12
There are 2 problems:

1. For ESM import, I don't think import { axios } from 'axios'; work
2. For TS, we need to update the typings to have the named export - I just updated the PR with this change

[akphi]

@jasonsaayman hi, could you please take a look at this again when you have time? Thanks!

[kr99]

My team is also interested in this fix.

[jasonsaayman]

Sure going to close this one in favour of #5162

[akphi]

@jasonsaayman I don't believe #5162 fixed the issue, as in akphi/issue-repo#12 I used axios@1.1.3. This is still the reasonable fix I believe

[akphi]

@jasonsaayman Hi, could you please take a look at this again? Thanks!

[akphi]

@jasonsaayman Could you let me know what else I can do for this PR? Do you want me to file a bug instead to be more formal and then resubmit my solution as a new PR?