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

Export unwrapped global fetch #124

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Conversation

DaniFoldi
Copy link
Contributor

Fixes #79

What this PR solves / how to test:

I recently ran into a somewhat similar situation as @Code-Hex where instrumenting a fetch caused all sorts of issues. For some cases, an uninstrumented fetch may be the only solution, so here's a PR exposing it as part of our API.

@ShravanSunder
Copy link

related to #126

Would be amazing to have this soon!

Copy link
Collaborator

@jahands jahands left a comment

Choose a reason for hiding this comment

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

It's a bit unfortunate that this is needed, but happy to add since it's blocking some folks. Thanks!

@jahands jahands merged commit 0bfd65c into evanderkoogh:main Apr 11, 2024
1 check passed
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.

feature request: export const unwrappedFetch = unwrap(fetch)
3 participants