isaacs
3f24755c8f
include readdir-scoped-modules sub-dependency
2014-08-13 09:48:07 -07:00
isaacs
151cd2ff87
read-installed@3.1.0
2014-08-12 13:46:18 -07:00
Forrest L Norvell
d987707442
move fetch into npm-registry-client
...
The primary purpose is so that everything doing network requests
includes auth, if so required. Sends bearer token by default, will send
HTTP Basic auth with `always-auth` set in the config.
2014-08-07 17:56:53 -07:00
isaacs
9b318e2155
read-installed@3.0.0
...
Fixes extraneous peer dependent looping devDependencies in --production mode.
CC @davglass
2014-07-31 18:02:32 -07:00
isaacs
9d73de7f8a
remove unnecessary mkdirps
2014-07-31 18:02:00 -07:00
isaacs
c0119f8095
merge v1.4
2014-07-31 17:54:38 -07:00
isaacs
8dd11d1347
update several dependencies
...
The quest to avoid SemVer '0.x' magic continues.
2014-07-31 15:42:26 -07:00
isaacs
d9a9e8448f
read-package-json@1.2.4
2014-07-31 10:24:25 -07:00
isaacs
86f0340fd0
github-url-from-git@1.2.0
2014-07-31 10:22:41 -07:00
isaacs
a94136a8a5
fstream@0.1.29
2014-07-31 10:22:05 -07:00
isaacs
bb82d18443
glob@4.0.5
2014-07-31 10:21:45 -07:00
isaacs
5b6bcf461e
cmd-shim@1.1.2
2014-07-31 10:20:57 -07:00
isaacs
63fe0eef51
init-package-json@1.0.0
...
Defaults package versions in 'npm init' to 1.0.0 instead of 0.0.0
2014-07-30 15:42:01 -07:00
isaacs
ea547e29f1
Bump semver to version 3
...
This makes the '^' operator stricter for 0.x.y versions, even if 'x' is
not 0.
As a direct result, several *other* deps had to be updated, because they
either depended on semver 2.x, or because the new stricter rules meant
that they (or their deps) were no longer valid.
The update to 'read-installed', in particular, causes a test failure.
That update must be rolled back, or the test made to pass, prior to a
stable npm 2.0.0 release going out.
2014-07-24 17:52:02 -07:00
isaacs
48fd23398a
npm-package-arg@2.0.1
2014-07-23 13:54:54 -07:00
Forrest L Norvell
2e768216de
github-url-from-git@1.2.0
2014-07-22 18:43:49 -07:00
Forrest L Norvell
b4f2ad3ade
mkdirp@0.5.0
2014-07-22 14:04:22 -07:00
Forrest L Norvell
99fa03b52b
fstream@0.1.29
2014-07-22 13:36:56 -07:00
Forrest L Norvell
77de5a1ef9
npmconf@2.0.3
2014-07-18 23:11:57 -07:00
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
18a3385bcf
npm-registry-client@3.0.2
2014-07-17 00:53:28 -07:00
Forrest L Norvell
88f51aa27e
npm-registry-client@2.0.3
2014-07-14 17:27:55 -07:00
Forrest L Norvell
54cf62534e
npm-registry-client@3.0.1
2014-07-14 16:35:08 -07:00
Forrest L Norvell
113765bfb7
npm-registry-client@3.0.0
2014-07-01 18:49:46 -07:00
Forrest L Norvell
a964f65ab6
npmconf@2.0.1
...
There was no npmconf 2.0.0. Don't even ask.
2014-07-01 18:49:46 -07:00
Forrest L Norvell
9ef8fe4d6e
replace some.js with (Zalgo-safe) async-some@1.0.0
2014-07-01 18:49:46 -07:00
Forrest L Norvell
719d8adb90
fs-vacuum@1.2.1
2014-07-01 18:49:46 -07:00
Forrest L Norvell
3fb6b7288a
dedupe normalize-package-data
2014-07-01 18:49:45 -07:00
Forrest L Norvell
9e1460e6ac
read-package-json@1.2.3
2014-07-01 18:49:45 -07:00
Forrest L Norvell
4f54043709
npm-package-arg@2.0.0
2014-07-01 18:49:45 -07:00
Forrest L Norvell
481f5f95dc
npm-package-arg@1.0.1
2014-07-01 18:43:16 -07:00
Forrest L Norvell
f34878fc4c
username and email are now always scoped to a registry
2014-07-01 18:43:16 -07:00
Forrest L Norvell
1b6e84161c
npmconf@npm/npmconf#othiym23/new-credentials
2014-07-01 18:43:16 -07:00
Forrest L Norvell
cfcbf34fe4
chasing down errant uses of old auth, part 1
2014-07-01 18:43:16 -07:00
Forrest L Norvell
0689ba249b
use --scope to map scope to registry
2014-07-01 18:43:16 -07:00
Forrest L Norvell
4441ea1ca1
update read-package-json to othiym23/scoped
2014-07-01 18:16:44 -07:00
Forrest L Norvell
3dcbb930be
update npm-registry-client
2014-07-01 18:16:43 -07:00
Forrest L Norvell
33dd0afcb3
scope token to the registry
2014-07-01 18:16:43 -07:00
Forrest L Norvell
0df7e16c02
publish to scoped registries
2014-07-01 18:16:43 -07:00
Forrest L Norvell
c08906f079
update npm-registry-client othiym23/multi-registry
2014-07-01 18:16:43 -07:00
Forrest L Norvell
eda697119f
install working version of npm-registry-client
2014-07-01 18:16:43 -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
9652678045
glob@4.0.3
2014-06-29 10:26:48 -07:00
isaacs
91733e2881
npmconf@1.1.2
2014-06-27 15:05:09 -07:00
isaacs
1cf5ad06a5
npmconf: Float patch to remove 'scope' from config defs
2014-06-26 14:22:47 -07:00
isaacs
2dac42eb67
npmconf@1.1.1
2014-06-26 14:22:21 -07:00
isaacs
4562f9dd56
bump tar and fstream deps
2014-06-24 13:52:55 -07:00
isaacs
0da350ad7b
npm-registry-client@2.0.2
2014-06-13 17:34:15 -07:00
isaacs
3ebee0e474
fstream@0.1.27
2014-06-13 17:20:06 -07:00
isaacs
d197b4dbd1
sha@1.2.4
2014-06-13 17:08:51 -07:00
