Skip to content
This repository has been archived by the owner on Nov 9, 2023. It is now read-only.

Feature Request: Add support for passing Request object #58

Closed
TillaTheHun0 opened this issue Sep 7, 2021 · 1 comment
Closed

Feature Request: Add support for passing Request object #58

TillaTheHun0 opened this issue Sep 7, 2021 · 1 comment

Comments

@TillaTheHun0
Copy link

Vanilla fetch supports passing a Request object as its first parameter. This works really great for flows that incrementally build out a Request object to then pass to fetch.

This API is also supported in node-fetch, which exports a Request implementation in its package. But when wrapping node-fetch with @vercel/fetch, and passing a Request object, an error is thrown: The "url" argument must be of type string. Received an instance of Request. This means none of our flows that worked with node-fetch and vanilla fetch will work with @vercel/fetch.

Is there any intention on supporting passing a Request object, as is described in the fetch spec?

@Ethan-Arrowood
Copy link
Contributor

Thank you for the report. We are archiving this project; you can read more details here: #83

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

No branches or pull requests

2 participants