Cannot set property 'raxConfig' of undefined
See original GitHub issueThe line below in the function onError
sometimes throws error “Cannot set property ‘raxConfig’ of undefined”
It happened when an axios call encountered a 401 error.
// Put the config back into the err
err.config.raxConfig = config;
Looks like the err.config
could be undefined
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
TypeError: Cannot set property 'raxConfig' of undefined #380
I have am not able to find similar issue, please help me to come out thanks. This is TypeError: Cannot set property 'raxConfig'...
Read more >Override retry-axios default config - Stack Overflow
This code which you can find in the npm library usage doesn't work properly: const myAxiosInstance = axios.create(); myAxiosInstance.defaults.
Read more >Axios Async/Await with Retry - DEV Community
Now, I'm going to rig this HTTP request by setting an unreasonably low timeout. ... TypeError: Cannot read property 'data' of undefined.
Read more >metropolis/dev: 203fb610fb36
+ */ + private static final Set<Cleaner> CLEANERS = Collections. ... + throw new IllegalStateException("Cannot find 'include' folder in JDK.
Read more >Cannot set property 'raxConfig' of undefined - Giters
Environment details node --version v13.9.0 @googlemaps/google-maps-services-js": "^2.6.0 package.json: "type": "module" Code example import { createRequire } ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sorry should have shared it in the first post.
I’m running retry-axios 2.1.1, axios 0.19.2. Both should be the latest versions.
🎉 This issue has been resolved in version 2.2.1 🎉
The release is available on:
Your semantic-release bot 📦🚀