ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Compare native fetch and Axios for modern JavaScript HTTP requests, covering bundle size, ergonomics, browser support, and concrete wrapper examples.
A decision guide for Mithril 2.x apps: compare built-in m.request against a custom fetch wrapper for predictable redraws, testable cancellation, and consistent error shapes.
This guide walks you through making reliable HTTP GET requests in JavaScript using async/await and fetch, covering error handling, JSON parsing, request cancellation, and environment setup for browsers and Node.js.
Stop stale network calls from breaking your UI. Learn how to use Fetch and AbortController to cancel requests and enforce timeouts in modern JavaScript.
AbortController gives a standard way to cancel in-flight fetches with one signal. Learn how to use it for timeouts, cleanup on unmount, and batch cancellation, plus how to distinguish AbortError from real failures.
Context The Fetch API throws an AbortError when a request is cancelled via AbortController . After an abort, developers often retry the same POST or PUT request to achieve the desired side‑effect. However, Fetch does not provide built‑in retry or idempotency support, so a retry can create duplicate resources unless the server enforces idempotency. Unresolved
Goal Determine how to programmatically detect whether Safari’s Fetch API will support request streaming (duplex: 'half') when issuing multiple concurrent uploads, rather than relying on ad‑hoc try/catch behavior. Constraints and Uncertainty Safari currently throws or falls back when a ReadableStream body is used with duplex: 'half' . No documented navigator
Goal Clarify whether identical, concurrent HTML5 Fetch API requests to the same URL should result in one network transaction or multiple transactions, and whether applications can rely on consistent behavior across browsers. Constraints and uncertainty The HTML5 specification leaves request deduplication to each browser implementation. Reported behavior vari
Runtime Request Handling Bun provides a native implementation of the Web Standard Fetch API alongside a compatibility layer for the Node.js http and https modules. While these coexist to support legacy migration, they utilize different underlying mechanisms for request execution and header management. Specification Consistency When migrating from Node.js-sty
axios
javascript
html5
bun