Skip to content

Improve terminology and comments. - #57

Open
davidlehn wants to merge 2 commits into
fix/undici-consistent-fetchfrom
fix/undici-consistent-fetch-2
Open

Improve terminology and comments.#57
davidlehn wants to merge 2 commits into
fix/undici-consistent-fetchfrom
fix/undici-consistent-fetch-2

Conversation

@davidlehn

Copy link
Copy Markdown
Member
  • Uses installed/built-in vs bundled/runtime. Seems clearer to me. Other suggestions welcome.
  • The big comment was split up. Hopefully more understandable.

davidlehn and others added 2 commits July 28, 2026 23:09
The code used "bundled" for the npm-installed undici and "runtime"/"native"
for the one built into node, which reads backwards and made
`bundledMajor === runtimeMajor` hard to follow. Standardize on "installed"
and "built-in" throughout.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The comment above `builtinFetchCompatible` had grown to explain the
background, the constant, both branches, and the guarded version reads all
at once. Hoist the background to a module-level note, leave the constant
with only its own meaning, and move the note about `ky` forwarding
`dispatcher` to the branch that relies on it. Drop the `Request` rebuild
explanation, which `createFetch` already documents.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@davidlehn
davidlehn requested review from applesnort and dlongley July 29, 2026 00:42

@dlongley dlongley left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with this. An alternative to built-in might be platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants