Skip to content
New issue

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

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

Already on GitHub? # to your account

feat!: Migrate to fetch #625

Open
1 task
danielbankhead opened this issue May 15, 2024 · 1 comment · May be fixed by #618
Open
1 task

feat!: Migrate to fetch #625

danielbankhead opened this issue May 15, 2024 · 1 comment · May be fixed by #618
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@danielbankhead
Copy link
Contributor

danielbankhead commented May 15, 2024

As we plan to support multiple environments and runtimes it makes sense to migrate from node-fetch to the Fetch API. Transitioning this library to a interface on top of fetch provides a ton of flexibility and will greatly decrease package size.

Additionally:

  • Update Github "about" section to:
An HTTP request client that provides a lightweight interface on top of `fetch`.
@unilynx
Copy link

unilynx commented Dec 6, 2024

This will also fix #640 and the deprecation warning reported by gaxios in node 22.1+

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants