Therefore, as npm's config help page says, it is set to whatever your http_proxy (case-insensitive) environment variable is. In your case (assuming it is still the same over a year later), it looks like you never set the proxy option in npm. Additionally, if that option is the only explicitly set option, it looks like ~/.npmrc is deleted, too, and recreated if you set anything else later. When I ran npm config set, the file ~/.npmrc seemed to be created automatically, with the option & its value as the only non-commented-out line.Īs for deleting options, it looks like this just sets the value back to the default value, or does nothing if that option was never set or was unset & never reset. None of the files were there yet, such as ~/.npmrc (on a Windows 8.1 machine with Git Bash), yet I could run npm config get and, if it was a correct npm option, it returned a value. I had never touched my npm config stuff before today, even though I had had it for months now. This is why you can still get options with npm config get : having those files only overrides the defaults, it doesn't create the options from scratch. It looks like the files npm uses to edit its config files are not created on a clean install, as npm has a default option for each one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |