8 Commits

Author	SHA1	Message	Date
isaacs	7c71c8d09b	upgrade npmconf and init-package-json ... Adds support for 'init.version' config, and falling back to _auth config as default auth when using default registry.	2014-07-18 14:17:19 -07:00
Forrest L Norvell	1b6e84161c	npmconf@npm/npmconf#othiym23/new-credentials	2014-07-01 18:43:16 -07:00
isaacs	bea190c745	bump nopt and npmconf ... Fixes #5591 The root cause here is that a change from 022 (a number in octal literal format) to '022' (a string) caused the string to later be interpreted as a decimal number, making for some wacky umask values. Solution is multipart. First, use the actual process.umask() value from the user's environment. This is almost certainly what they want anyway. Second, validate all default values just like we do with user- supplied values, rather than trusting them to never be wrong. This would've found the problem much sooner, while in dev. This second part requires that we allow a value of null for 'path' type args, allow 'undefined' for the 'local-address' config, and avoid looking up a cafile of 'null', all of which are good hygenic things to add defense-in-depth anyway.	2014-07-01 10:30:33 -07:00
isaacs	91733e2881	npmconf@1.1.2	2014-06-27 15:05:09 -07:00
isaacs	2dac42eb67	npmconf@1.1.1	2014-06-26 14:22:21 -07:00
isaacs	137ea44542	npmconf@1.0.5	2014-06-12 17:34:37 -07:00
isaacs	b1dd58e4ac	npmconf@1.0.4 ... Fix #5459	2014-06-12 16:16:37 -07:00
isaacs	1707fcedb7	npmconf@1.0.0, Refactor config/uid/prefix loading process ... Closes #4751	2014-05-14 12:41:32 -07:00