Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Improved isAxiosHeaders validation to handle obfuscated code #60

Merged
merged 1 commit into from
Jan 16, 2024
Merged

fix: Improved isAxiosHeaders validation to handle obfuscated code #60

merged 1 commit into from
Jan 16, 2024

Conversation

joaolrpm
Copy link
Contributor

@joaolrpm joaolrpm commented Jan 15, 2024

Fixes #59

However, I've encountered an issue with the UMD build due to axios imports after modifying util.ts. To fix it, I added browser: true to the nodeResolve in rollup.config.js. Since I'm not well-versed in rollup configuration, could you provide guidance on the best way to proceed in this situation?

image

@@ -1,4 +1,5 @@
import { Transformable, TransformableObject } from './types';
import { AxiosHeaders } from 'axios';
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that AxiosHeaders can be imported in the latest version. thank you

@mpyw mpyw merged commit cdd9a02 into mpyw:master Jan 16, 2024
@joaolrpm joaolrpm deleted the fix/is-axios-headers branch January 16, 2024 03:15
@joaolrpm
Copy link
Contributor Author

Hi @mpyw 👋

I apologize for any inconvenience caused. The release wasn't published as it seems to have failed in the UMD build. I'll open a proposal PR to address this situation soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Response headers aren't being converted for axios 1.x
2 participants