Axios auth refresh doesn't work with axios v1.1.3

[SuryaNelakanti]

Whenever i run a build it gives this Writable is not defined error.

I have downgraded axios to version 1.1.2 and it works fine.

[shurco]

I stopped working even on version 1.0.0

[3tw]

Whenever i run a build it gives this Writable is not defined error.

Perhaps you re missing 'stream' module inside your build

// node-modules/follow-redirects/index.js`
var Writable = require("stream").Writable;`

Are you using Vite or Webpack?

[brenjt]

I have this same problem using Vite

[aichichang]

Had the same issue, upgrade to axios 1.2.2 fixed it.

The refresh logic function was called when hitting a 401 but the response.config.headers.Authorization bearer token is not attached to the API call correctly. I got [Object object]: undefined and so the call failed again with 403...

[alex-moiseenko]

i have the same problem when using Vite.

I've spent several hours looking for a solution, this problem is related to node modules. In my case it was 'url' and 'stream' modules.

I'm found this plugin https://github.com/voracious/vite-plugin-node-polyfills and it fixed problem.

[prateekinfi]

@aichichang

I think i know the cause of your issue specifically. There is a problem here:

axios-auth-refresh/src/utils.ts

Line 143 in 6ea5f96

return instance(error.response.config);

In the older Axios versions, error.response.config and error.response.config.headers used to be a plain objects but the later versions have seemed to changed something.

The class of error is now AxiosError and the class of error.response.config.headers is AxiosHeaders. These are directly being passed back to the axios instance without sanitising the input config. I don't think Axios is able to correctly parse such objects and that's why you see '[Object object]' in your header.

It is debatable whether this could be considered a problem with axios or axios-auth-refresh.

[prateekinfi]

Did anyone figure out a way to work around the problem I mentioned above?
@aichichang did the solution mentioned by @alex-moiseenko work for you?

My security team needs me to upgrade axios and I can't delay it anymore. Just realized it's exactly one year since my comment 😄 . Didn't expect this thread to be this quiet 🤪