refactor(eas-cli): use built-in Node fetch instead of undici #2419
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.
Why
This is a follow-up PR of #2414, to try and fall-back to the built-in Node
fetch
support as much as possible. This is an attempt, as likely more things will pop up that require refactoring.Unfortunately, we still require
undici
as advanced "non-spec" features are used, likeimport { ProxyAgent } from 'undici'
. But, this tries to use all built-in features as much as possible.How
fetch
globals instead fromundici
nock
workaround from refactor(eas-cli): swapnode-fetch
forundici
to support Node 22 better #2414 as wellTest Plan
See GitHub Actions, and manual testing (everything)