What I Wanted to Do
NPM install in IPv6 networks.
What Happened Instead
NPM resolve the IPv4 of the registry and try to reach directly the IPv4.
Get an IPv6 machine,
NPM install anything
It’s a design problem, because NPM talk directly to the IPv4, which is really bad.
If NPM talk to the hostname instead, it will work on IPv4/v6 and if the registry exist in IPv4-only, you can reach it out using NAT64 mechanisms.
This issue seem ignored from more than 3 years, and issue related to this bug are close by the Bot on Github.
It would be awesome (or normal ) to fix that with high priority…