Making Fetch Happen
summary
Fetch lands in Node.js core available in Node.js v18 after years of polyfills (node-fetch, cross-fetch) and experiments behind --experimental-fetch; the implementation uses the next‑generation HTTP client Undici implementation and shows dramatic speed improvements on basic HTTP/1.1 workloads. Streams, AbortController and URL standards are integrated to match browser behavior, many contributors iterate on edge cases, and the result runs without extra packages while preserving familiar fetch semantics across server and browser environments.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:22Making Fetch Happen
- 0:58Where Did It all Start
- 2:17Service Workers
- 6:34What Does this Mean for Javascript
- 7:04What Does this Mean for Fetch
- 8:33Simplicity
related talks
34mWhich Node.js HTTP client in 2024?
32mAligning Node.js with the Web Platform
39mNode.js - What's Next - Catalyzing Change in the Node.js Ecosystem
30mNode.js: What's Next?
40mNode.js: Where are we now, where are we going?
34mNode.js - What's Next - Catalyzing Change in the Node.js Ecosystem
25mNext-Gen Server JavaScript: Web Standards
22mWhat's New in Node.js Core?
