It seems that it's a real problem on the NPM servers. I see the same error when navigating to https://registry.npmjs.org/http-server
in a browser. The server indeed doesn't have a valid certificate. Nothing Windows-specific.
NPM reports there's an issue with incorrect DNS information being cached, here: https://status.npmjs.org/incidents/v22ffls5cd6h
Until the cache clears up, they suggest doing the following:
dig registry.npmjs.com @1.1.1.1
- Add the IP found to your /etc/hosts file.
Update: A bit unrelated, for ones using yarn
: Yarn's mirror of the NPM registry seems to be affected by this problem too, so it seems that at the moment all we can do is wait until the issue resolves itself or the Yarn team applies a workaround on the server.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…