You can't npm install <foo> without getting an error message about the self-signed cert. At least until you update npm, which you usually do with npm update -g

You can't npm install <foo> without getting an error message about the self-signed cert. At least until you update npm, which you usually do with npm update -g npm, but that will also fail with the same error. Fun! The blog post doesn't mention deleting the config change after updating, which (I'm not an expert) might be important. I think this is a full fix: http://stackoverflow.com/a/22099006/2708274 http://stackoverflow.com/a/22099006/2708274