Things to help out with to bring fetch out of experimental status.
- Types
- Docs (https://github.com/nodejs/undici/issues/915#issuecomment-893411363)
- Look for TODOs in https://github.com/nodejs/undici/blob/main/lib/api/api-fetch.js
-
Headers
and spec comments + fixes (https://github.com/nodejs/undici/issues/933) - Error types (https://github.com/nodejs/undici/issues/931)
- Review spec compliance https://fetch.spec.whatwg.org/
-
Blob.type
(https://github.com/nodejs/undici/issues/925) -
data:
uri (https://github.com/nodejs/undici/issues/929) - Improve
httpNetworkFetch
spec compliance. -
FormData
(https://github.com/nodejs/undici/issues/930) -
highWaterMark
browser compatibility (https://github.com/nodejs/undici/issues/923) - Enable/fix disabled test in https://github.com/nodejs/undici/tree/node-fetch/test/node-fetch and try to uncomment.
- WebSocket (https://github.com/nodejs/undici/issues/932)
- Fix
Request.clone
- Fix
Response.clone
(https://github.com/nodejs/undici/issues/945)
Tests
- Improve coverage
- Port tests from WPT (https://github.com/web-platform-tests/wpt/tree/master/fetch). See also https://github.com/nodejs/whatwg-stream/pull/3.
- Port tests from node-fetch (https://github.com/nodejs/undici/pull/928)
- Port tests from undici-fetch (#926)
Response
https://github.com/nodejs/undici/blob/main/lib/api/api-fetch/index.js#L158 https://github.com/nodejs/undici#parameter-response https://fetch.spec.whatwg.org/#response-class
-
clone()
(https://github.com/nodejs/undici/pull/921) -
statusText
- Extract, expose
Response
class (https://github.com/nodejs/undici/pull/928) - Document
Response
class
Request
- Extract, expose
Request
class (https://github.com/nodejs/undici/pull/928) - Document
Request
class
Headers
- Expose
Headers
class (https://github.com/nodejs/undici/pull/928) - Document
Headers
class
Spec
https://github.com/nodejs/undici/issues/958
- httpRedirectFetch
- setRequestReferrerPolicyOnRedirect
- httpFetch
- httpNetworkOrCacheFetch
- httpNetworkFetch
- fetchFinale
- finalizeResponse
- mainFetch
- fetching
- finalizeAndReportTiming
- fetch
- markResourceTiming
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Fetch, #1 Rewards App, Have Fun, Save Money - Fetch
Snap your grocery, shopping & restaurant receipts with Fetch, the #1 rewards app. Shop & dine, snap your receipts and easily get free...
Read more >Fetch Package: Multifamily's Package Management Solution
Fetch is an off-site package management solution for multifamily apartment communities. Eliminate the time and space devoted to resident packages and bring ...
Read more >Using the Fetch API - MDN Web Docs
The Fetch API provides a JavaScript interface for accessing and manipulating parts of the protocol, such as requests and responses.
Read more >Best Pet Insurance for Dogs & Cats | Fetch by The Dodo
Fetch provides the most comprehensive pet insurance for cats & dogs. We pay back up to 90% of your unexpected vet bills.
Read more >Fetch: Have Fun, Save Money - Apps on Google Play
America's Favorite Rewards App - data.ai □ #1 Best Cash Back App for 2022 - Motley Fool □ Must-Have Shopping App - Google...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think we should be ok in referring to MDN and documenting the difference/limitations… at least for now.
Looks great! I’ll take a deeper look at this when I can and try to pick something up