docs: clarify fetch class compatibility#5549
Open
vibhor-aggr wants to merge 1 commit into
Open
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5549 +/- ##
=======================================
Coverage 93.44% 93.44%
=======================================
Files 110 110
Lines 37418 37418
=======================================
Hits 34967 34967
Misses 2451 2451 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
metcoder95
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3071.
This documents the supported pattern for fetch-related classes when Node.js' built-in Undici implementation and an installed
undicipackage are both present.The change clarifies that
fetch,Request,Response,Headers, andFormDatavalues should come from the same implementation:undicipackage, orundici.install().It also calls out the specific failure mode from the issue: a
Requestcreated by Node.js' built-in globalRequestis not guaranteed to work withfetchimported from a differentundicipackage version, and the reverse is unsupported too.Validation:
git diff --checknpm run lintnpm run test:typescript