Reaching out to ecosystem client package maintainers
Open
Nobody has claimed this yet.
question
Status: help-wanted
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
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):
- got (@szmarczak)
- axios
- node-fetch
- superagent
- needle
- elastic
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked “Future of the Node HTTP Client” issue and the package checklist in this issue. Determine which listed maintainers still need outreach about switching to the Node core client under the hood, then update the checklist with the resulting contact status; completion would mean the outreach work and package list are up to date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100