nodejs / corepack

Zero-runtime-dependency package acting as bridge between Node projects and their package managers
MIT License
2.57k stars 169 forks source link

Updating DNS troubleshooting to mention ipv6 #263

Closed SpencerKaiser closed 1 year ago

SpencerKaiser commented 1 year ago

This issue is more widespread than I initially thought and some issues arise directly from DNS resolution of ipv6 domains, so I wanted to update the docs to call that out specifically

markojak commented 1 year ago

I want to add here that this is not a corner issue. There are over 32m spectrum customers and so far it seems all spectrum customers who have IPv6 enabled on their routers will be affected

Evidently my router updated its firmware and then turned on IPv6 and then I had to stumble around for two days trying to figure out why Node18+ doesn't want to connect to the registry

Even simple documentation like this can be helpful but I strongly suggest network level information on installs, ping and doctor

SpencerKaiser commented 1 year ago

Evidently my router updated its firmware and then turned on IPv6 and then I had to stumble around for two days trying to figure out why Node18+ doesn't want to connect to the registry

.... you don't have an Eero router, do you? 🤨 That is literally what happened to me... overnight ipv6 got turned on, Spectrum as my provider, yarn + npm failures all over the place that were nearly impossible to debug.