You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2023. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
Vanilla
fetch
supports passing aRequest
object as its first parameter. This works really great for flows that incrementally build out aRequest
object to then pass tofetch
.This API is also supported in
node-fetch
, which exports aRequest
implementation in its package. But when wrappingnode-fetch
with@vercel/fetch
, and passing aRequest
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 withnode-fetch
and vanillafetch
will work with@vercel/fetch
.Is there any intention on supporting passing a
Request
object, as is described in thefetch
spec?The text was updated successfully, but these errors were encountered: