Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reaching out to ecosystem client package maintainers #837

Open
2 of 6 tasks
ronag opened this issue Jun 17, 2021 · 2 comments
Open
2 of 6 tasks

Reaching out to ecosystem client package maintainers #837

ronag opened this issue Jun 17, 2021 · 2 comments
Labels
question [Use a Discussion instead] Status: help-wanted This issue/pr is open for contributions

Comments

@ronag
Copy link
Member

ronag commented Jun 17, 2021 •
edited
Loading

Should we try to reach out the the maintainers of popular http client ecosystem packages about switching node core client to undici under the hood?

Future of the Node HTTP Client

Some popular packages I can think might be interested (please add to the list of you can thing of additional ones):
@ronag ronag added the question [Use a Discussion instead] label Jun 17, 2021
@ronag ronag added the Status: help-wanted This issue/pr is open for contributions label Jun 29, 2021
@GrosSacASac
Copy link

What is the difference between node-fetch and undici's fetch ? Can I switch from one to another without breaking changes ?

@delvedor
Copy link
Member

FYI: @elastic/transport which is the engine of the elasticsearch client uses undici by default from v8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question [Use a Discussion instead] Status: help-wanted This issue/pr is open for contributions
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ronag @delvedor @GrosSacASac