Last 12 weeks · 3 commits
4 of 6 standards met
Hi there, I've currently hit by a bug in another software (Gitpod) which uses 'is-reachable' to test the reachability of hosts, digging into the source codes leads me here, I'm not sure if it's relevant so I opened up an issue to discuss it a bit, feel free to close it if inappropriate. The situation is one of my services is hosted in a home lab setup which IP address is exact , which by 'router-ips' is considered an router IP, and 'is-reachable' thought the router IPs are 'unreachable' and returned a to the caller, thus, my host is determined to be 'not reachable' while it's perfectly reachable. Relevant code here: https://github.com/sindresorhus/is-reachable/blob/main/index.js#L55 I'm not sure I understand the rationale behind the decision, maybe logically 'is-reachable' should only check the 'reachability', whether it's an internal router IP or a normal external IP should be irrelevant, or am I missing something here?
Repository: sindresorhus/is-reachable. Description: Check if servers are reachable Stars: 383, Forks: 42. Primary language: JavaScript. Languages: JavaScript (94.4%), TypeScript (5.6%). License: MIT. Topics: browser, connectivity, detect, internet, network, nodejs, online, ping, reachability. Latest release: v6.1.0 (1mo ago). Open PRs: 0, open issues: 0. Last activity: 1mo ago. Community health: 85%. Top contributors: sindresorhus, silverwind, kevva, genbandbrent, danielmahon, BendingBender, jleft, johno, arthurvr, mmalecki and others.
JavaScript