[DISCUSSION] Is it possible to add an option for using IPv6 only?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
These days I have encounter a problem which is related to IPv4 & IPv6, here is the problem:
- Commands like
npm publishornpm viewwill fail with error connection timeout (connecting to IP of IPv4 of registry.npmjs.org) after default timeout (5 mins) - DNS resolving works normally, returns IPv4 IPs and IPv6 IPs
ping <IPv4 IP>workscurl -4 https://registry.npmjs.orgalways timed outcurl -6 https://registry.npmjs.orgworks
I understand that this is a network issue, not a bug, but I wonder if there is a possibility to add an option like ipv6Only to make npm-registry-fetch and npm only use IPv6 in certain conditions.
If it sounds reasonable, I can make a PR.
Thanks.
Related: [npm-registry-fetch issue](https://github.com/npm/npm-registry-fetch/issues/226)
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 related npm-registry-fetch issue 226 and the reported behavior of npm publish and npm view when resolving registry.npmjs.org. The issue would need a settled scope for an IPv6-only option and a clear validation plan before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100