Dmitriy Mozgovoy

@ttomasini This is a known issue in Axios 0.x. Axios 1.x fixes a batch of issues related to response decompression in node.js, including this one. (#5306, #4701)

The `lib` folder is exported as `unsafe` to highlight this is at your risk, since you will import private modules where the semver stability of the interfaces is not guaranteed....

> Starting from which version ? v1.4.0 (#5677) > Well, what's a non-risky way to create adapters that the maintainers won't add inside Axios ? There are no good enough...

@ralph7777 just add the following line to your package.json: "type": "module", https://stackoverflow.com/questions/58384179/syntaxerror-cannot-use-import-statement-outside-a-module Of course, you can still use require() with axios if you want

I'm going to close this as it seems the issue [has been fixed](https://github.com/axios/axios/blob/726f1c8e00cffa0461a8813a9bdcb8f8b9d762cf/lib/adapters/http.js#L468) with another PR. Thanks for your contribution!

I believe this issue has been fixed so I'm going to close this.

@guoyunhe Manual adapter switching without the need for direct import will be provided by #5277 PR.

Perhaps we can export the lib folder with some prefix in the path to highlight this as an unsafe operation. I would like to avoid potential situations when we change...

Axios currently uses the XMLHttpRequest transport, which always follows redirects under the hood with no option to turn them off, so you can't manually handle the location header before the...

@IchordeDionysos I'll deal with this tomorrow. This seems to have happened more than once, people forget that Axios is cross-platform and add PRs with strict DOM-related types https://github.com/axios/axios/pull/4675/files.