9 Commits

Author	SHA1	Message	Date
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	af57760260	more minor dep bumps	2014-06-06 17:26:01 -07:00
isaacs	e0048e940d	nopt@2.2.1	2014-04-28 15:00:27 -07:00
isaacs	62417bc1c9	nopt@2.2.0	2014-02-16 12:54:49 -08:00
isaacs	4309cdc7bf	nopt@2.1.2	2013-07-23 20:28:55 -07:00
isaacs	06b5e022df	nopt@2.1.1	2013-01-18 08:28:21 -08:00
isaacs	8bc57100f4	nopt@2.1.0	2013-01-17 12:26:57 -08:00
isaacs	c88c580a42	nopt@2.0.0	2012-07-23 15:40:07 -07:00
isaacs	c18fe966dd	check in node_modules	2012-01-13 08:41:06 -08:00