nodejs / nodejs/node-core-utils
current issues with network
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 314
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
- node-fetch not working on 18 (maybe only with proxy)
- proxy only support http, sock5 not working
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 reproducing the reported node-fetch failure on Node 18 with a proxy, then test the proxy behavior described for HTTP and SOCKS5. The issue names no files or tests, so trace the CLI's network entry point and identify the affected dependency or configuration. Done means the supported proxy cases work reliably and are covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100