nodejs/node

Document differences between Node.js fetch() implementations and the standard

Open

#52163 opened on Mar 20, 2024

View on GitHub
 (16 comments) (1 reaction) (0 assignees)JavaScript (117,218 stars) (35,535 forks)batch import
docgood first issue

Description

We should add a section in our docs documenting how/why Node.js fetch() differs from the standard.

A few notable differences

  • new Response(asyncIterable) is an addition to standard
  • cookies handling
  • no forbidden headers

@KhafraDev definitely know more

Contributor guide

Tech stack
javascriptnodejs
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic understanding of fetch APIfamiliarity with Node.jsability to write documentation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Identify the existing fetch documentation in Node.js repository (likely in doc/api/ directory). Review the differences mentioned in the issue and any further discussion in comments. Consult with maintainers, especially @KhafraDev, to get a comprehensive list. Then draft a new section for the docs.