Merge remote-tracking branch 'ry/v0.6' into v0.6-merge

Conflicts: ChangeLog Makefile deps/npm/AUTHORS deps/npm/html/api/bin.html deps/npm/html/api/bugs.html deps/npm/html/api/commands.html deps/npm/html/api/config.html deps/npm/html/api/deprecate.html deps/npm/html/api/docs.html deps/npm/html/api/edit.html deps/npm/html/api/explore.html deps/npm/html/api/help-search.html deps/npm/html/api/init.html deps/npm/html/api/install.html deps/npm/html/api/link.html deps/npm/html/api/load.html deps/npm/html/api/ls.html deps/npm/html/api/npm.html deps/npm/html/api/outdated.html deps/npm/html/api/owner.html deps/npm/html/api/pack.html deps/npm/html/api/prefix.html deps/npm/html/api/prune.html deps/npm/html/api/publish.html deps/npm/html/api/rebuild.html deps/npm/html/api/restart.html deps/npm/html/api/root.html deps/npm/html/api/run-script.html deps/npm/html/api/search.html deps/npm/html/api/shrinkwrap.html deps/npm/html/api/start.html deps/npm/html/api/stop.html deps/npm/html/api/submodule.html deps/npm/html/api/tag.html deps/npm/html/api/test.html deps/npm/html/api/uninstall.html deps/npm/html/api/unpublish.html deps/npm/html/api/update.html deps/npm/html/api/version.html deps/npm/html/api/view.html deps/npm/html/api/whoami.html deps/npm/html/doc/README.html deps/npm/html/doc/adduser.html deps/npm/html/doc/bin.html deps/npm/html/doc/bugs.html deps/npm/html/doc/build.html deps/npm/html/doc/bundle.html deps/npm/html/doc/cache.html deps/npm/html/doc/changelog.html deps/npm/html/doc/coding-style.html deps/npm/html/doc/completion.html deps/npm/html/doc/config.html deps/npm/html/doc/deprecate.html deps/npm/html/doc/developers.html deps/npm/html/doc/disputes.html deps/npm/html/doc/docs.html deps/npm/html/doc/edit.html deps/npm/html/doc/explore.html deps/npm/html/doc/faq.html deps/npm/html/doc/folders.html deps/npm/html/doc/help-search.html deps/npm/html/doc/help.html deps/npm/html/doc/index.html deps/npm/html/doc/init.html deps/npm/html/doc/install.html deps/npm/html/doc/json.html deps/npm/html/doc/link.html deps/npm/html/doc/list.html deps/npm/html/doc/npm.html deps/npm/html/doc/outdated.html deps/npm/html/doc/owner.html deps/npm/html/doc/pack.html deps/npm/html/doc/prefix.html deps/npm/html/doc/prune.html deps/npm/html/doc/publish.html deps/npm/html/doc/rebuild.html deps/npm/html/doc/registry.html deps/npm/html/doc/removing-npm.html deps/npm/html/doc/restart.html deps/npm/html/doc/root.html deps/npm/html/doc/run-script.html deps/npm/html/doc/scripts.html deps/npm/html/doc/search.html deps/npm/html/doc/semver.html deps/npm/html/doc/shrinkwrap.html deps/npm/html/doc/star.html deps/npm/html/doc/start.html deps/npm/html/doc/stop.html deps/npm/html/doc/submodule.html deps/npm/html/doc/tag.html deps/npm/html/doc/test.html deps/npm/html/doc/uninstall.html deps/npm/html/doc/unpublish.html deps/npm/html/doc/update.html deps/npm/html/doc/version.html deps/npm/html/doc/view.html deps/npm/html/doc/whoami.html deps/npm/man/man1/npm.1 deps/npm/man/man3/npm.3 deps/npm/package.json doc/api/url.markdown lib/http.js src/node_version.h test/simple/test-fs-sync-fd-leak.js
13 years ago · 01d146c29f
302 changed files with 3102 additions and 3789 deletions
--- a/5
+++ b/5
@ -301,3 +301,8 @@ Mustansir Golawala <mgolawala@gmail.com>
 fukayatsu <fukayatsu@gmail.com>
 Domenic Denicola <domenic@domenicdenicola.com>
 Bryan Cantrill <bryan@joyent.com>
 lrn@chromium.org <lrn@chromium.org>
 Dane Springmeyer <dane@dbsgeo.com>
 Sambasiva Suda <sambasivarao@gmail.com>
 Vincent Voyer <v@fasterize.com>
 ANDO Takahiro <takahiro.ando@gmail.com>
--- a/48
+++ b/48
@ -255,7 +255,53 @@
 * Bug fixes
-2012.04.09 Version 0.6.15 (stable)
+2012.05.04 Version 0.6.17 (stable), 4ced23deaf36493f4303a18f6fdce768c58becc0
 * Upgrade npm to 1.1.21
 * uv: Add support for EROFS errors (Ben Noordhuis, Maciej Małecki)
 * uv: Add support for EIO and ENOSPC errors (Fedor Indutny)
 * windows: Add support for EXDEV errors (Bert Belder)
 * http: Fix client memory leaks (isaacs, Vincent Voyer)
 * fs: fix file descriptor leak in sync functions (Ben Noordhuis)
 * fs: fix ReadStream / WriteStream double close bug (Ben Noordhuis)
 2012.04.30 Version 0.6.16 (stable), a1d193963ddc80a27da5da01b59751e14e33d1d6
 * Upgrade V8 to 3.6.6.25
 * Upgrade npm to 1.1.19
 * Windows: add mappings for UV_ENOENT (Bert Belder)
 * linux: add IN_MOVE_SELF to inotify event mask (Ben Noordhuis)
 * unix: call pipe handle connection cb on accept() error (Ben Noordhuis)
 * unix: handle EWOULDBLOCK (Ben Noordhuis)
 * map EWOULDBLOCK to UV_EAGAIN (Ben Noordhuis)
 * Map ENOMEM to UV_ENOMEM (isaacs)
 * Child process: support the `gid` and `uid` options (Bert Belder)
 * test: cluster: add worker death event test (Ben Noordhuis)
 * typo in node_http_parser (isaacs)
 * http_parser: Eat CRLF between requests, even on connection:close. (Ben Noordhuis)
 * don't check return value of unsetenv (Ben Noordhuis)
 2012.04.09 Version 0.6.15 (stable), f160a45b254e591eb33716311c92be533c6d86c4
 * Update npm to 1.1.16
--- a/3
+++ b/3
@ -64,7 +64,8 @@ test-valgrind: all
 node_modules/weak:
 	@if [ ! -f node ]; then make all; fi
 	@if [ ! -d node_modules ]; then mkdir -p node_modules; fi
-	./node deps/npm/bin/npm-cli.js install weak --prefix="$(shell pwd)"
+	./node deps/npm/bin/npm-cli.js install weak \
 		--prefix="$(shell pwd)" --unsafe-perm # go ahead and run as root.
 test-gc: all node_modules/weak
 	$(PYTHON) tools/test.py --mode=release gc
--- a/deps/npm/.npmignore
+++ b/deps/npm/.npmignore
@ -11,7 +11,3 @@ npm-debug.log
 ./npmrc
 .gitignore
 release/
 # don't ignore .npmignore files
 # these are used in some tests.
 !.npmignore
--- a/deps/npm/AUTHORS
+++ b/deps/npm/AUTHORS
@ -51,16 +51,3 @@ Stephen Sugden <glurgle@gmail.com>
 Gautham Pai <buzypi@gmail.com>
 David Trejo <david.daniel.trejo@gmail.com>
 Paul Vorbach <paul@vorb.de>
 George Ornbo <george@shapeshed.com>
 Tim Oxley <secoif@gmail.com>
 Tyler Green <tyler.green2@gmail.com>
 atomizer <danila.gerasimov@gmail.com>
 Rod Vagg <rod@vagg.org>
 Christian Howe <coderarity@gmail.com>
 Andrew Lunny <alunny@gmail.com>
 Henrik Hodne <dvyjones@binaryhex.com>
 Adam Blackburn <regality@gmail.com>
 Kris Windham <kriswindham@gmail.com>
 Jens Grunert <jens.grunert@gmail.com>
 Joost-Wim Boekesteijn <joost-wim@boekesteijn.nl>
 Dalmais Maxence <github@maxired.fr>
--- a/deps/npm/LICENSE
+++ b/deps/npm/LICENSE
@ -1,4 +1,4 @@
-Copyright 2009-2012, Isaac Z. Schlueter (the "Original Author")
+Copyright 2009, 2010, 2011 Isaac Z. Schlueter (the "Author")
 All rights reserved.
 MIT +no-false-attribs License
@ -20,9 +20,9 @@ by the recipients as they would use the unmodified Software,
 containing modifications that substantially alter, remove, or
 disable functionality of the Software, outside of the documented
 configuration mechanisms provided by the Software, shall be
-modified such that the Original Author's bug reporting email
+modified such that the Author's bug reporting email addresses and
-addresses and urls are either replaced with the contact information
+urls are either replaced with the contact information of the
-of the parties responsible for the changes, or removed entirely.
+parties responsible for the changes, or removed entirely.
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
@ -36,7 +36,7 @@ OTHER DEALINGS IN THE SOFTWARE.
 Except where noted, this license applies to any and all software
 programs and associated documentation files created by the
-Original Author, when distributed with the Software.
+Author, when distributed with the Software.
 "Node.js" and "node" trademark Joyent, Inc. npm is not officially
 part of the Node.js project, and is neither owned by nor
@ -49,11 +49,13 @@ and are not covered by this license.
 "npm Logo" created by Mathias Pettersson and Brian Hammond,
 used with permission.
 This program includes a BSDTar/LibArchive version 2.8.3-1 binary,
 originally distributed as part of the MinGW suite, compiled for
 Win32, according to the terms of the BSD license.
 See deps/basic-bsdtar-2.8.3-1-ming32-bin/basic-bsdtar.LICENSE.
 This program uses "node-uuid", Copyright (c) 2010 Robert Kieffer,
 according to the terms of the MIT license.
 This program uses "request", Copyright (c) 2011 Mikeal Rogers,
 according to the terms of the Apache license.
 This program uses "mkdirp",  Copyright (c) 2010 James Halliday,
 according to the terms of the MIT/X11 license.
--- a/deps/npm/Makefile
+++ b/deps/npm/Makefile
@ -123,7 +123,7 @@ doc-publish: doc
 	rsync -vazu --stats --no-implied-dirs --delete html/api/ npmjs.org:/var/www/npmjs.org/public/api
 zip-publish: release
-	scp release/* npmjs.org:/var/www/npmjs.org/public/dist/
+	scp release/*.zip npmjs.org:/var/www/npmjs.org/public/dist/
 release:
 	@bash scripts/release.sh
--- a/deps/npm/bin/npm-cli.js
+++ b/deps/npm/bin/npm-cli.js
@ -49,13 +49,6 @@ if (conf.version) {
  return
 }
 if (conf.versions) {
  var v = process.versions
  v.npm = npm.version
  console.log(v)
  return
 }
 log.info("npm@"+npm.version, "using")
 log.info("node@"+process.version, "using")
--- a/deps/npm/bin/npm-get-uid-gid.js
+++ b/deps/npm/bin/npm-get-uid-gid.js
@ -0,0 +1,16 @@
 var argv = process.argv.slice(2)
  , user = argv[0] || process.getuid()
  , group = argv[1] || process.getgid()
 if (!isNaN(user)) user = +user
 if (!isNaN(group)) group = +group
 console.error([user, group])
 try {
  process.setgid(group)
  process.setuid(user)
  console.log(JSON.stringify({uid:+process.getuid(), gid:+process.getgid()}))
 } catch (ex) {
  console.log(JSON.stringify({error:ex.message,errno:ex.errno}))
 }
--- a/deps/npm/bin/npm.cmd
+++ b/deps/npm/bin/npm.cmd
@ -1,6 +1,6 @@
 :: Created by npm, please don't edit manually.
-@IF EXIST "%~dp0\node.exe" (
+@IF EXIST "%~dp0"\"node.exe" (
-  "%~dp0\node.exe" "%~dp0\.\node_modules\npm\bin\npm-cli.js" %*
+  "%~dp0"\"node.exe"  "%~dp0\.\node_modules\npm\bin\npm-cli.js" %*
 ) ELSE (
-  node "%~dp0\.\node_modules\npm\bin\npm-cli.js" %*
+  node  "%~dp0\.\node_modules\npm\bin\npm-cli.js" %*
 )
--- a/deps/npm/doc/api/ls.md
+++ b/deps/npm/doc/api/ls.md
@ -21,12 +21,6 @@ It will print out extraneous, missing, and invalid packages.
 If the silent parameter is set to true, nothing will be output to the screen,
 but the data will still be returned.
 Callback is provided an error if one occurred, the full data about which
 packages are installed and which dependencies they will receive, and a
 "lite" data object which just shows which versions are installed where.
 Note that the full data object is a circular structure, so care must be
 taken if it is serialized to JSON.
 ## CONFIGURATION
 ### long
--- a/deps/npm/doc/cli/changelog.md
+++ b/deps/npm/doc/cli/changelog.md
@ -3,50 +3,6 @@ npm-changelog(1) -- Changes
 ## HISTORY
 ### 1.1.3, 1.1.4
 * Update request to support HTTPS-over-HTTP proxy tunneling
 * Throw on undefined envs in config settings
 * Update which to 1.0.5
 * Fix windows UNC busyloop in findPrefix
 * Bundle nested bundleDependencies properly
 * Alias adduser to add-user
 * Doc updates  (Christian Howe, Henrik Hodne, Andrew Lunny)
 * ignore logfd/outfd streams in makeEnv() (Rod Vagg)
 * shrinkwrap: Behave properly with url-installed deps
 * install: Support --save with url install targets
 * Support installing naked tars or single-file modules from urls etc.
 * init: Don't add engines section
 * Don't run make clean on rebuild
 * Added missing unicode replacement (atomizer)
 ### 1.1.2
 Dave Pacheco (2):
      add "npm shrinkwrap"
 Martin Cooper (1):
      Fix #1753 Make a copy of the cached objects we'll modify.
 Tim Oxley (1):
      correctly remove readme from default npm view command.
 Tyler Green (1):
      fix #2187 set terminal columns to Infinity if 0
 isaacs (19):
      update minimatch
      update request
      Experimental: single-file modules
      Fix #2172 Don't remove global mans uninstalling local pkgs
      Add --versions flag to show the version of node as well
      Support --json flag for ls output
      update request to 2.9.151
 ### 1.1  
 * Replace system tar dependency with a JS tar
 * Continue to refine
 ### 1.0  
 * Greatly simplified folder structure 
 * Install locally (bundle by default) 
--- a/deps/npm/doc/cli/coding-style.md
+++ b/deps/npm/doc/cli/coding-style.md
@ -59,8 +59,8 @@ Don't use them except in four situations:
 * `for (;;)` loops.  They're actually required.
 * null loops like: `while (something) ;` (But you'd better have a good
  reason for doing that.)
-* `case "foo": doSomething(); break`
+* case "foo": doSomething(); break
-* In front of a leading `(` or `[` at the start of the line.
+* In front of a leading ( or [ at the start of the line.
  This prevents the expression from being interpreted
  as a function call or property access, respectively.
--- a/deps/npm/doc/cli/config.md
+++ b/deps/npm/doc/cli/config.md
@ -115,8 +115,6 @@ The following shorthands are parsed on the command-line:
 * `-l`: `--long`
 * `-desc`: `--description`
 * `-S`: `--save`
 * `-D`: `--save-dev`
 * `-O`: `--save-optional`
 * `-y`: `--yes`
 * `-n`: `--yes false`
 * `ll` and `la` commands: `ls --long`
@ -220,28 +218,6 @@ See also the `strict-ssl` config.
 The location of npm's cache directory.  See `npm-cache(1)`
 ### cache-max
 * Default: Infinity
 * Type: Number
 The maximum time (in seconds) to keep items in the registry cache before
 re-checking against the registry.
 Note that no purging is done unless the `npm cache clean` command is
 explicitly used, and that only GET requests use the cache.
 ### cache-min
 * Default: 0
 * Type: Number
 The minimum time (in seconds) to keep items in the registry cache before
 re-checking against the registry.
 Note that no purging is done unless the `npm cache clean` command is
 explicitly used, and that only GET requests use the cache.
 ### color
 * Default: true on Posix, false on Windows
@ -360,13 +336,6 @@ user.
 A proxy to use for outgoing https requests.
 ### user-agent
 * Default: npm/{npm.version} node/{process.version}
 * Type: String
 Sets a User-Agent to the request header
 ### ignore
 * Default: ""
@ -384,7 +353,7 @@ The value `npm init` should use by default for the package version.
 ### init.author.name
-* Default: ""
+* Default: "0.0.0"
 * Type: String
 The value `npm init` should use by default for the package author's name.
@ -403,17 +372,6 @@ The value `npm init` should use by default for the package author's email.
 The value `npm init` should use by default for the package author's homepage.
 ### json
 * Default: false
 * Type: Boolean
 Whether or not to output JSON data, rather than the normal output.
 This feature is currently experimental, and the output data structures
 for many commands is either not implemented in JSON yet, or subject to
 change.  Only the output from `npm ls --json` is currently valid.
 ### link
 * Default: false
@ -586,24 +544,6 @@ Save installed packages to a package.json file as dependencies.
 Only works if there is already a package.json file present.
 ### save-dev
 * Default: false
 * Type: Boolean
 Save installed packages to a package.json file as devDependencies.
 Only works if there is already a package.json file present.
 ### save-optional
 * Default: false
 * Type: Boolean
 Save installed packages to a package.json file as optionalDependencies.
 Only works if there is already a package.json file present.
 ### searchopts
 * Default: ""
@ -742,16 +682,6 @@ If true, output the npm version and exit successfully.
 Only relevant when specified explicitly on the command line.
 ### versions
 * Default: false
 * Type: boolean
 If true, output the npm version as well as node's `process.versions`
 hash, and exit successfully.
 Only relevant when specified explicitly on the command line.
 ### viewer
 * Default: "man" on Posix, "browser" on Windows
--- a/deps/npm/doc/cli/developers.md
+++ b/deps/npm/doc/cli/developers.md
@ -27,23 +27,12 @@ A package is:
 * d) a `<name>@<version>` that is published on the registry with (c)
 * e) a `<name>@<tag>` that points to (d)
 * f) a `<name>` that has a "latest" tag satisfying (e)
 * g) a `git` url that, when cloned, results in (a).
 Even if you never publish your package, you can still get a lot of
 benefits of using npm if you just want to write a node program (a), and
 perhaps if you also want to be able to easily install it elsewhere
 after packing it up into a tarball (b).
 Git urls can be of the form:
    git://github.com/user/project.git#commit-ish
    git+ssh://user@hostname:project.git#commit-ish
    git+http://user@hostname/project/blah.git#commit-ish
    git+https://user@hostname/project/blah.git#commit-ish
 The `commit-ish` can be any tag, sha, or branch which can be supplied as
 an argument to `git checkout`.  The default is `master`.
 ## The package.json File
 You need to have a `package.json` file in the root of your project to do
--- a/deps/npm/doc/cli/index.md
+++ b/deps/npm/doc/cli/index.md
@ -170,10 +170,6 @@ npm-index(1) -- Index of all npm documentation
 The semantic versioner for npm
 ## npm-shrinkwrap(1)
 Lock down dependency versions
 ## npm-star(1)
 Mark your favorite packages
@ -327,10 +323,6 @@ npm-index(1) -- Index of all npm documentation
 Search for packages
 ## npm-shrinkwrap(3)
 programmatically generate package shrinkwrap file
 ## npm-start(3)
 Start a package
--- a/deps/npm/doc/cli/install.md
+++ b/deps/npm/doc/cli/install.md
@ -7,17 +7,14 @@ npm-install(1) -- Install a package
    npm install <tarball file>
    npm install <tarball url>
    npm install <folder>
-    npm install <name> [--save|--save-dev|--save-optional]
+    npm install <name>
    npm install <name>@<tag>
    npm install <name>@<version>
    npm install <name>@<version range>
    npm install <name>@<version range>
 ## DESCRIPTION
-This command installs a package, and any packages that it depends on. If the
+This command installs a package, and any packages that it depends on.
 package has a shrinkwrap file, the installation of dependencies will be driven
 by that. See npm-shrinkwrap(1).
 A `package` is:
@ -36,116 +33,88 @@ after packing it up into a tarball (b).
 * `npm install` (in package directory, no arguments):
  Install the dependencies in the local node_modules folder.
-    Install the dependencies in the local node_modules folder.
+  In global mode (ie, with `-g` or `--global` appended to the command),
-
+  it installs the current package context (ie, the current working
-    In global mode (ie, with `-g` or `--global` appended to the command),
+  directory) as a global package.
    it installs the current package context (ie, the current working
    directory) as a global package.
 * `npm install <folder>`:
-
+  Install a package that is sitting in a folder on the filesystem.
    Install a package that is sitting in a folder on the filesystem.
 * `npm install <tarball file>`:
  Install a package that is sitting on the filesystem.  Note: if you just want
  to link a dev directory into your npm root, you can do this more easily by
  using `npm link`.
-    Install a package that is sitting on the filesystem.  Note: if you just want
+  Example:
    to link a dev directory into your npm root, you can do this more easily by
    using `npm link`.
    Example:
-          npm install ./package.tgz
+        npm install ./package.tgz
 * `npm install <tarball url>`:
  Fetch the tarball url, and then install it.  In order to distinguish between
  this and other options, the argument must start with "http://" or "https://"
-    Fetch the tarball url, and then install it.  In order to distinguish between
+  Example:
    this and other options, the argument must start with "http://" or "https://"
    Example:
          npm install https://github.com/indexzero/forever/tarball/v0.5.6
 * `npm install <name> [--save|--save-dev|--save-optional]`:
    Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See
    `npm-config(1)`.)
-    In most cases, this will install the latest version
+        npm install https://github.com/indexzero/forever/tarball/v0.5.6
    of the module published on npm.
-    Example:
+* `npm install <name>`:
  Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See
  `npm-config(1)`)
-          npm install sax
+  Example:
-    `npm install` takes 3 exclusive, optional flags which save or update
+        npm install sax
    the package version in your main package.json:
-    * `--save`: Package will appear in your `dependencies`.
+  **Note**: If there is a file or folder named `<name>` in the current
-
+  working directory, then it will try to install that, and only try to
-    * `--save-dev`: Package will appear in your `devDependencies`.
+  fetch the package by name if it is not valid.
    * `--save-optional`: Package will appear in your `optionalDependencies`.
    Examples:
          npm install sax --save
          npm install node-tap --save-dev
          npm install dtrace-provider --save-optional
    **Note**: If there is a file or folder named `<name>` in the current
    working directory, then it will try to install that, and only try to
    fetch the package by name if it is not valid.
 * `npm install <name>@<tag>`:
  Install the version of the package that is referenced by the specified tag.
  If the tag does not exist in the registry data for that package, then this
  will fail.
-    Install the version of the package that is referenced by the specified tag.
+  Example:
    If the tag does not exist in the registry data for that package, then this
    will fail.
    Example:
-          npm install sax@latest
+        npm install sax@latest
 * `npm install <name>@<version>`:
  Install the specified version of the package.  This will fail if the version
  has not been published to the registry.
-    Install the specified version of the package.  This will fail if the version
+  Example:
    has not been published to the registry.
-    Example:
+        npm install sax@0.1.1
          npm install sax@0.1.1
 * `npm install <name>@<version range>`:
  Install a version of the package matching the specified version range.  This
  will follow the same rules for resolving dependencies described in `npm-json(1)`.
-    Install a version of the package matching the specified version range.  This
+  Note that most version ranges must be put in quotes so that your shell will
-    will follow the same rules for resolving dependencies described in `npm-json(1)`.
+  treat it as a single argument.
    Note that most version ranges must be put in quotes so that your shell will
    treat it as a single argument.
-    Example:
+  Example:
-          npm install sax@">=0.1.0 <0.2.0"
+        npm install sax@">=0.1.0 <0.2.0"
 * `npm install <git remote url>`:
-    Install a package by cloning a git remote url.  The format of the git
+  Install a package by cloning a git remote url.  The format of the git
-    url is:
+  url is:
-          <protocol>://[<user>@]<hostname><separator><path>[#<commit-ish>]
+        <protocol>://[<user>@]<hostname><separator><path>[#<commit-ish>]
-    `<protocol>` is one of `git`, `git+ssh`, `git+http`, or
+  `<protocol>` is one of `git`, `git+ssh`, `git+http`, or
-    `git+https`.  If no `<commit-ish>` is specified, then `master` is
+  `git+https`.  If no `<commit-ish>` is specified, then `master` is
-    used.
+  used.
-    Examples:
+  Examples:
-          git+ssh://git@github.com:isaacs/npm.git#v1.0.27
+        git+ssh://git@github.com:isaacs/npm.git#v1.0.27
-          git+https://isaacs@github.com/isaacs/npm.git
+        git+https://isaacs@github.com/isaacs/npm.git
-          git://github.com/isaacs/npm.git#v1.0.27
+        git://github.com/isaacs/npm.git#v1.0.27
 You may combine multiple arguments, and even multiple types of arguments.
 For example:
@ -230,4 +199,3 @@ affects a real use-case, it will be investigated.
 * npm-folders(1)
 * npm-tag(1)
 * npm-rm(1)
 * npm-shrinkwrap(1)
--- a/deps/npm/doc/cli/json.md
+++ b/deps/npm/doc/cli/json.md
@ -332,7 +332,6 @@ is a semver compatible version identifier.
 * `""` (just an empty string) Same as `*`
 * `version1 - version2` Same as `>=version1 <=version2`.
 * `range1 || range2` Passes if either range1 or range2 are satisfied.
 * `git...` See 'Git URLs as Dependencies' below
 For example, these are all valid:
@ -388,18 +387,6 @@ of a version range.
 This tarball will be downloaded and installed locally to your package at
 install time.
 ### Git URLs as Dependencies
 Git urls can be of the form:
    git://github.com/user/project.git#commit-ish
    git+ssh://user@hostname:project.git#commit-ish
    git+http://user@hostname/project/blah.git#commit-ish
    git+https://user@hostname/project/blah.git#commit-ish
 The `commit-ish` can be any tag, sha, or branch which can be supplied as
 an argument to `git checkout`.  The default is `master`.
 ## devDependencies
 If someone is planning on downloading and using your module in their
@ -428,7 +415,7 @@ node that your stuff works on:
    { "engines" : { "node" : ">=0.1.27 <0.1.30" } }
 And, like with dependencies, if you don't specify the version (or if you
-specify "\*" as the version), then any version of node will do.
+specify "*" as the version), then any version of node will do.
 If you specify an "engines" field, then npm will require that "node" be
 somewhere on that list. If "engines" is omitted, then npm will just assume
@ -439,36 +426,6 @@ are capable of properly installing your program.  For example:
    { "engines" : { "npm" : "~1.0.20" } }
 ## os
 You can specify which operating systems your
 module will run on:
    "os" : [ "darwin", "linux" ]
 You can also blacklist instead of whitelist operating systems,
 just prepend the blacklisted os with a '!':
    "os" : [ "!win32" ]
 The host operating system is determined by `process.platform`
 It is allowed to both blacklist, and whitelist, although there isn't any
 good reason to do this.
 ## cpu
 If your code only runs on certain cpu architectures,
 you can specify which ones.
    "cpu" : [ "x64", "ia32" ]
 Like the `os` option, you can also blacklist architectures:
    "cpu" : [ "!arm", "!mips" ]
 The host architecture is determined by `process.arch`
 ## preferGlobal
 If your package is primarily a command-line application that should be
@ -485,7 +442,7 @@ to publish it.
 This is a way to prevent accidental publication of private repositories.
 If you would like to ensure that a given package is only ever published
-to a specific registry (for example, an internal registry),
+to a speciic registry (for example, an internal registry),
 then use the `publishConfig` hash described below
 to override the `registry` config param at publish-time.
--- a/deps/npm/doc/cli/list.md
+++ b/deps/npm/doc/cli/list.md
@ -22,13 +22,6 @@ When run as `ll` or `la`, it shows extended information by default.
 ## CONFIGURATION
 ### json
 * Default: false
 * Type: Boolean
 Show information in JSON format.
 ### long
 * Default: false
--- a/deps/npm/doc/cli/scripts.md
+++ b/deps/npm/doc/cli/scripts.md
@ -62,20 +62,6 @@ Package scripts run in an environment where many pieces of information are
 made available regarding the setup of npm and the current state of the
 process.
 ### path
 If you depend on modules that define executable scripts, like test suites,
 then those executables will be added to the `PATH` for executing the scripts.
 So, if your package.json has this:
    { "name" : "foo"
    , "dependencies" : { "bar" : "0.1.x" }
    , "scripts": { "start" : "bar ./test" } }
 then you could run `npm start` to execute the `bar` script, which is exported
 into the `node_modules/.bin` directory on `npm install`.
 ### package.json vars
 The package.json fields are tacked onto the `npm_package_` prefix. So, for
--- a/deps/npm/html/api/bin.html
+++ b/deps/npm/html/api/bin.html
@ -19,7 +19,7 @@
 <p>This function should not be used programmatically.  Instead, just refer
 to the <code>npm.bin</code> member.</p>
 </div>
-<p id="footer">bin &mdash; npm@1.1.18</p>
+<p id="footer">bin &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/bugs.html
+++ b/deps/npm/html/api/bugs.html
@ -25,7 +25,7 @@ optional version number.</p>
 <p>This command will launch a browser, so this command may not be the most
 friendly for programmatic use.</p>
 </div>
-<p id="footer">bugs &mdash; npm@1.1.18</p>
+<p id="footer">bugs &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/commands.html
+++ b/deps/npm/html/api/commands.html
@ -28,7 +28,7 @@ usage, or <code>man 3 npm-&lt;command&gt;</code> for programmatic usage.</p>
 <ul><li><a href="../doc/index.html">index(1)</a></li></ul>
 </div>
-<p id="footer">commands &mdash; npm@1.1.18</p>
+<p id="footer">commands &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/config.html
+++ b/deps/npm/html/api/config.html
@ -33,7 +33,7 @@ functions instead.</p>
 <ul><li><a href="../api/npm.html">npm(3)</a></li></ul>
 </div>
-<p id="footer">config &mdash; npm@1.1.18</p>
+<p id="footer">config &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/deprecate.html
+++ b/deps/npm/html/api/deprecate.html
@ -30,7 +30,7 @@ install the package.</p></li></ul>
 <ul><li><a href="../api/publish.html">publish(3)</a></li><li><a href="../api/unpublish.html">unpublish(3)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
 </div>
-<p id="footer">deprecate &mdash; npm@1.1.18</p>
+<p id="footer">deprecate &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/docs.html
+++ b/deps/npm/html/api/docs.html
@ -25,7 +25,7 @@ optional version number.</p>
 <p>This command will launch a browser, so this command may not be the most
 friendly for programmatic use.</p>
 </div>
-<p id="footer">docs &mdash; npm@1.1.18</p>
+<p id="footer">docs &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/edit.html
+++ b/deps/npm/html/api/edit.html
@ -30,7 +30,7 @@ to open. The package can optionally have a version number attached.</p>
 <p>Since this command opens an editor in a new process, be careful about where
 and how this is used.</p>
 </div>
-<p id="footer">edit &mdash; npm@1.1.18</p>
+<p id="footer">edit &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/explore.html
+++ b/deps/npm/html/api/explore.html
@ -24,7 +24,7 @@ sure to use <code>npm rebuild &lt;pkg&gt;</code> if you make any changes.</p>
 <p>The first element in the 'args' parameter must be a package name.  After that is the optional command, which can be any number of strings. All of the strings will be combined into one, space-delimited command.</p>
 </div>
-<p id="footer">explore &mdash; npm@1.1.18</p>
+<p id="footer">explore &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/help-search.html
+++ b/deps/npm/html/api/help-search.html
@ -32,7 +32,7 @@ Name of the file that matched</li></ul>
 <p>The silent parameter is not neccessary not used, but it may in the future.</p>
 </div>
-<p id="footer">help-search &mdash; npm@1.1.18</p>
+<p id="footer">help-search &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/init.html
+++ b/deps/npm/html/api/init.html
@ -35,7 +35,7 @@ then go ahead and use this programmatically.</p>
 <p><a href="../doc/json.html">json(1)</a></p>
 </div>
-<p id="footer">init &mdash; npm@1.1.18</p>
+<p id="footer">init &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/install.html
+++ b/deps/npm/html/api/install.html
@ -25,7 +25,7 @@ the name of a package to be installed.</p>
 <p>Finally, 'callback' is a function that will be called when all packages have been
 installed or when an error has been encountered.</p>
 </div>
-<p id="footer">install &mdash; npm@1.1.18</p>
+<p id="footer">install &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/link.html
+++ b/deps/npm/html/api/link.html
@ -39,7 +39,7 @@ npm.commands.link('redis', cb)  # link-install the package</code></pre>
 <p>Now, any changes to the redis package will be reflected in
 the package in the current working directory</p>
 </div>
-<p id="footer">link &mdash; npm@1.1.18</p>
+<p id="footer">link &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/load.html
+++ b/deps/npm/html/api/load.html
@ -32,7 +32,7 @@ config object.</p>
 <p>For a list of all the available command-line configs, see <code>npm help config</code></p>
 </div>
-<p id="footer">load &mdash; npm@1.1.18</p>
+<p id="footer">load &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/ls.html
+++ b/deps/npm/html/api/ls.html
@ -28,12 +28,6 @@ like with any other command, such as <code>global</code> to list global packages
 <p>If the silent parameter is set to true, nothing will be output to the screen,
 but the data will still be returned.</p>
 <p>Callback is provided an error if one occurred, the full data about which
 packages are installed and which dependencies they will receive, and a
 "lite" data object which just shows which versions are installed where.
 Note that the full data object is a circular structure, so care must be
 taken if it is serialized to JSON.</p>
 <h2 id="CONFIGURATION">CONFIGURATION</h2>
 <h3 id="long">long</h3>
@ -59,7 +53,7 @@ project.</p>
 This means that if a submodule a same dependency as a parent module, then the
 dependency will only be output once.</p>
 </div>
-<p id="footer">ls &mdash; npm@1.1.18</p>
+<p id="footer">ls &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/npm.html
+++ b/deps/npm/html/api/npm.html
@ -24,7 +24,7 @@ npm.load(configObject, function (er, npm) {
 <h2 id="VERSION">VERSION</h2>
-<p>1.1.18</p>
+<p>1.1.0-2</p>
 <h2 id="DESCRIPTION">DESCRIPTION</h2>
@ -91,7 +91,7 @@ method names.  Use the <code>npm.deref</code> method to find the real name.</p>
 <pre><code>var cmd = npm.deref("unp") // cmd === "unpublish"</code></pre>
 </div>
-<p id="footer">npm &mdash; npm@1.1.18</p>
+<p id="footer">npm &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/outdated.html
+++ b/deps/npm/html/api/outdated.html
@ -19,7 +19,7 @@ currently outdated.</p>
 <p>If the 'packages' parameter is left out, npm will check all packages.</p>
 </div>
-<p id="footer">outdated &mdash; npm@1.1.18</p>
+<p id="footer">outdated &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/owner.html
+++ b/deps/npm/html/api/owner.html
@ -34,7 +34,7 @@ that is not implemented at this time.</p>
 <ul><li><a href="../api/publish.html">publish(3)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
 </div>
-<p id="footer">owner &mdash; npm@1.1.18</p>
+<p id="footer">owner &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/pack.html
+++ b/deps/npm/html/api/pack.html
@ -25,7 +25,7 @@ overwritten the second time.</p>
 <p>If no arguments are supplied, then npm packs the current package folder.</p>
 </div>
-<p id="footer">pack &mdash; npm@1.1.18</p>
+<p id="footer">pack &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/prefix.html
+++ b/deps/npm/html/api/prefix.html
@ -21,7 +21,7 @@
 <p>This function is not useful programmatically</p>
 </div>
-<p id="footer">prefix &mdash; npm@1.1.18</p>
+<p id="footer">prefix &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/prune.html
+++ b/deps/npm/html/api/prune.html
@ -23,7 +23,7 @@
 <p>Extraneous packages are packages that are not listed on the parent
 package's dependencies list.</p>
 </div>
-<p id="footer">prune &mdash; npm@1.1.18</p>
+<p id="footer">prune &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/publish.html
+++ b/deps/npm/html/api/publish.html
@ -32,7 +32,7 @@ the registry.  Overwrites when the "force" environment variable is set.</p>
 <ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../api/owner.html">owner(3)</a></li></ul>
 </div>
-<p id="footer">publish &mdash; npm@1.1.18</p>
+<p id="footer">publish &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/rebuild.html
+++ b/deps/npm/html/api/rebuild.html
@ -22,7 +22,7 @@ the new binary. If no 'packages' parameter is specify, every package will be reb
 <p>See <code>npm help build</code></p>
 </div>
-<p id="footer">rebuild &mdash; npm@1.1.18</p>
+<p id="footer">rebuild &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/restart.html
+++ b/deps/npm/html/api/restart.html
@ -27,7 +27,7 @@ in the <code>packages</code> parameter.</p>
 <ul><li><a href="../api/start.html">start(3)</a></li><li><a href="../api/stop.html">stop(3)</a></li></ul>
 </div>
-<p id="footer">restart &mdash; npm@1.1.18</p>
+<p id="footer">restart &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/root.html
+++ b/deps/npm/html/api/root.html
@ -21,7 +21,7 @@
 <p>This function is not useful programmatically.</p>
 </div>
-<p id="footer">root &mdash; npm@1.1.18</p>
+<p id="footer">root &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/run-script.html
+++ b/deps/npm/html/api/run-script.html
@ -29,7 +29,7 @@ assumed to be the command to run. All other elements are ignored.</p>
 <ul><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../api/test.html">test(3)</a></li><li><a href="../api/start.html">start(3)</a></li><li><a href="../api/restart.html">restart(3)</a></li><li><a href="../api/stop.html">stop(3)</a></li></ul>
 </div>
-<p id="footer">run-script &mdash; npm@1.1.18</p>
+<p id="footer">run-script &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/search.html
+++ b/deps/npm/html/api/search.html
@ -32,7 +32,7 @@ excluded term (the "searchexclude" config). The search is case insensitive
 and doesn't try to read your mind (it doesn't do any verb tense matching or the
 like).</p>
 </div>
-<p id="footer">search &mdash; npm@1.1.18</p>
+<p id="footer">search &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/shrinkwrap.html
+++ b/deps/npm/html/api/shrinkwrap.html
@ -26,7 +26,7 @@ but the shrinkwrap file will still be written.</p>
 <p>Finally, 'callback' is a function that will be called when the shrinkwrap has
 been saved.</p>
 </div>
-<p id="footer">shrinkwrap &mdash; npm@1.1.18</p>
+<p id="footer">shrinkwrap &mdash; npm@1.1.16</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/start.html
+++ b/deps/npm/html/api/start.html
@ -19,7 +19,7 @@
 <p>npm can run tests on multiple packages. Just specify multiple packages
 in the <code>packages</code> parameter.</p>
 </div>
-<p id="footer">start &mdash; npm@1.1.18</p>
+<p id="footer">start &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/stop.html
+++ b/deps/npm/html/api/stop.html
@ -19,7 +19,7 @@
 <p>npm can run stop on multiple packages. Just specify multiple packages
 in the <code>packages</code> parameter.</p>
 </div>
-<p id="footer">stop &mdash; npm@1.1.18</p>
+<p id="footer">stop &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/submodule.html
+++ b/deps/npm/html/api/submodule.html
@ -33,7 +33,7 @@ dependencies into the submodule folder.</p>
 <ul><li>npm help json</li><li>git help submodule</li></ul>
 </div>
-<p id="footer">submodule &mdash; npm@1.1.18</p>
+<p id="footer">submodule &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/tag.html
+++ b/deps/npm/html/api/tag.html
@ -29,7 +29,7 @@ parameter is missing or falsey (empty), the default froom the config will be
 used. For more information about how to set this config, check
 <code>man 3 npm-config</code> for programmatic usage or <code>man npm-config</code> for cli usage.</p>
 </div>
-<p id="footer">tag &mdash; npm@1.1.18</p>
+<p id="footer">tag &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/test.html
+++ b/deps/npm/html/api/test.html
@ -22,7 +22,7 @@ true.</p>
 <p>npm can run tests on multiple packages. Just specify multiple packages
 in the <code>packages</code> parameter.</p>
 </div>
-<p id="footer">test &mdash; npm@1.1.18</p>
+<p id="footer">test &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/uninstall.html
+++ b/deps/npm/html/api/uninstall.html
@ -22,7 +22,7 @@ the name of a package to be uninstalled.</p>
 <p>Finally, 'callback' is a function that will be called when all packages have been
 uninstalled or when an error has been encountered.</p>
 </div>
-<p id="footer">uninstall &mdash; npm@1.1.18</p>
+<p id="footer">uninstall &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/unpublish.html
+++ b/deps/npm/html/api/unpublish.html
@ -26,7 +26,7 @@ is what is meant.</p>
 <p>If no version is specified, or if all versions are removed then
 the root package entry is removed from the registry entirely.</p>
 </div>
-<p id="footer">unpublish &mdash; npm@1.1.18</p>
+<p id="footer">unpublish &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/update.html
+++ b/deps/npm/html/api/update.html
@ -18,7 +18,7 @@
 <p>The 'packages' argument is an array of packages to update. The 'callback' parameter will be called when done or when an error occurs.</p>
 </div>
-<p id="footer">update &mdash; npm@1.1.18</p>
+<p id="footer">update &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/version.html
+++ b/deps/npm/html/api/version.html
@ -24,7 +24,7 @@ fail if the repo is not clean.</p>
 parameter. The difference, however, is this function will fail if it does
 not have exactly one element. The only element should be a version number.</p>
 </div>
-<p id="footer">version &mdash; npm@1.1.18</p>
+<p id="footer">version &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/view.html
+++ b/deps/npm/html/api/view.html
@ -99,7 +99,7 @@ the field name.</p>
 <p>corresponding to the list of fields selected.</p>
 </div>
-<p id="footer">view &mdash; npm@1.1.18</p>
+<p id="footer">view &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/whoami.html
+++ b/deps/npm/html/api/whoami.html
@ -21,7 +21,7 @@
 <p>This function is not useful programmatically</p>
 </div>
-<p id="footer">whoami &mdash; npm@1.1.18</p>
+<p id="footer">whoami &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/README.html
+++ b/deps/npm/html/doc/README.html
@ -267,7 +267,7 @@ will no doubt tell you to put the output in a gist or email.</p>
 <ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/index.html">index(1)</a></li></ul>
 </div>
-<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.1.18</p>
+<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/adduser.html
+++ b/deps/npm/html/doc/adduser.html
@ -39,7 +39,7 @@ authorize on a new machine.</p>
 <ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li><li><a href="../doc/whoami.html">whoami(1)</a></li></ul>
 </div>
-<p id="footer">adduser &mdash; npm@1.1.18</p>
+<p id="footer">adduser &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/bin.html
+++ b/deps/npm/html/doc/bin.html
@ -20,7 +20,7 @@
 <ul><li><a href="../doc/prefix.html">prefix(1)</a></li><li><a href="../doc/root.html">root(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
 </div>
-<p id="footer">bin &mdash; npm@1.1.18</p>
+<p id="footer">bin &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/bugs.html
+++ b/deps/npm/html/doc/bugs.html
@ -36,7 +36,7 @@ config param.</p>
 <ul><li><a href="../doc/docs.html">docs(1)</a></li><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
 </div>
-<p id="footer">bugs &mdash; npm@1.1.18</p>
+<p id="footer">bugs &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/build.html
+++ b/deps/npm/html/doc/build.html
@ -25,7 +25,7 @@ A folder containing a <code>package.json</code> file in its root.</li></ul>
 <ul><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
 </div>
-<p id="footer">build &mdash; npm@1.1.18</p>
+<p id="footer">build &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/bundle.html
+++ b/deps/npm/html/doc/bundle.html
@ -20,7 +20,7 @@ install packages into the local space.</p>
 <ul><li><a href="../doc/install.html">install(1)</a></li></ul>
 </div>
-<p id="footer">bundle &mdash; npm@1.1.18</p>
+<p id="footer">bundle &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cache.html
+++ b/deps/npm/html/doc/cache.html
@ -66,7 +66,7 @@ they do not make an HTTP request to the registry.</p>
 <ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/pack.html">pack(1)</a></li></ul>
 </div>
-<p id="footer">cache &mdash; npm@1.1.18</p>
+<p id="footer">cache &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/changelog.html
+++ b/deps/npm/html/doc/changelog.html
@ -10,37 +10,6 @@
 <h2 id="HISTORY">HISTORY</h2>
 <h3 id="1-1-3-1-1-4">1.1.3, 1.1.4</h3>
 <ul><li>Update request to support HTTPS-over-HTTP proxy tunneling</li><li>Throw on undefined envs in config settings</li><li>Update which to 1.0.5</li><li>Fix windows UNC busyloop in findPrefix</li><li>Bundle nested bundleDependencies properly</li><li>Alias adduser to add-user</li><li>Doc updates  (Christian Howe, Henrik Hodne, Andrew Lunny)</li><li>ignore logfd/outfd streams in makeEnv() (Rod Vagg)</li><li>shrinkwrap: Behave properly with url-installed deps</li><li>install: Support --save with url install targets</li><li>Support installing naked tars or single-file modules from urls etc.</li><li>init: Don't add engines section</li><li>Don't run make clean on rebuild</li><li>Added missing unicode replacement (atomizer)</li></ul>
 <h3 id="1-1-2">1.1.2</h3>
 <p>Dave Pacheco (2):
      add "npm shrinkwrap"</p>
 <p>Martin Cooper (1):
      Fix #1753 Make a copy of the cached objects we'll modify.</p>
 <p>Tim Oxley (1):
      correctly remove readme from default npm view command.</p>
 <p>Tyler Green (1):
      fix #2187 set terminal columns to Infinity if 0</p>
 <p>isaacs (19):
      update minimatch
      update request
      Experimental: single-file modules
      Fix #2172 Don't remove global mans uninstalling local pkgs
      Add --versions flag to show the version of node as well
      Support --json flag for ls output
      update request to 2.9.151</p>
 <h3 id="1-1">1.1</h3>
 <ul><li>Replace system tar dependency with a JS tar</li><li>Continue to refine</li></ul>
 <h3 id="1-0">1.0</h3>
 <ul><li>Greatly simplified folder structure </li><li>Install locally (bundle by default) </li><li>Drastic rearchitecture</li></ul>
@ -65,7 +34,7 @@
 <ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li></ul>
 </div>
-<p id="footer">changelog &mdash; npm@1.1.18</p>
+<p id="footer">changelog &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/coding-style.html
+++ b/deps/npm/html/doc/coding-style.html
@ -64,7 +64,7 @@ while (foo) {
 <p>Don't use them except in four situations:</p>
 <ul><li><code>for (;;)</code> loops.  They're actually required.</li><li>null loops like: <code>while (something) ;</code> (But you'd better have a good
-reason for doing that.)</li><li><code>case "foo": doSomething(); break</code></li><li>In front of a leading <code>(</code> or <code>[</code> at the start of the line.
+reason for doing that.)</li><li>case "foo": doSomething(); break</li><li>In front of a leading ( or [ at the start of the line.
 This prevents the expression from being interpreted
 as a function call or property access, respectively.</li></ul>
@ -191,7 +191,7 @@ set to anything."</p>
 <ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
 </div>
-<p id="footer">coding-style &mdash; npm@1.1.18</p>
+<p id="footer">coding-style &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/completion.html
+++ b/deps/npm/html/doc/completion.html
@ -33,7 +33,7 @@ completions based on the arguments.</p>
 <ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
 </div>
-<p id="footer">completion &mdash; npm@1.1.18</p>
+<p id="footer">completion &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/config.html
+++ b/deps/npm/html/doc/config.html
@ -105,7 +105,7 @@ global config.</p>
 <p>The following shorthands are parsed on the command-line:</p>
-<ul><li><code>-v</code>: <code>--version</code></li><li><code>-h</code>, <code>-?</code>, <code>--help</code>, <code>-H</code>: <code>--usage</code></li><li><code>-s</code>, <code>--silent</code>: <code>--loglevel silent</code></li><li><code>-q</code>, <code>--quiet</code>: <code>--loglevel warn</code></li><li><code>-d</code>: <code>--loglevel info</code></li><li><code>-dd</code>, <code>--verbose</code>: <code>--loglevel verbose</code></li><li><code>-ddd</code>: <code>--loglevel silly</code></li><li><code>-g</code>: <code>--global</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-m</code>: <code>--message</code></li><li><code>-p</code>, <code>--porcelain</code>: <code>--parseable</code></li><li><code>-reg</code>: <code>--registry</code></li><li><code>-v</code>: <code>--version</code></li><li><code>-f</code>: <code>--force</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-desc</code>: <code>--description</code></li><li><code>-S</code>: <code>--save</code></li><li><code>-D</code>: <code>--save-dev</code></li><li><code>-O</code>: <code>--save-optional</code></li><li><code>-y</code>: <code>--yes</code></li><li><code>-n</code>: <code>--yes false</code></li><li><code>ll</code> and <code>la</code> commands: <code>ls --long</code></li></ul>
+<ul><li><code>-v</code>: <code>--version</code></li><li><code>-h</code>, <code>-?</code>, <code>--help</code>, <code>-H</code>: <code>--usage</code></li><li><code>-s</code>, <code>--silent</code>: <code>--loglevel silent</code></li><li><code>-q</code>, <code>--quiet</code>: <code>--loglevel warn</code></li><li><code>-d</code>: <code>--loglevel info</code></li><li><code>-dd</code>, <code>--verbose</code>: <code>--loglevel verbose</code></li><li><code>-ddd</code>: <code>--loglevel silly</code></li><li><code>-g</code>: <code>--global</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-m</code>: <code>--message</code></li><li><code>-p</code>, <code>--porcelain</code>: <code>--parseable</code></li><li><code>-reg</code>: <code>--registry</code></li><li><code>-v</code>: <code>--version</code></li><li><code>-f</code>: <code>--force</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-desc</code>: <code>--description</code></li><li><code>-S</code>: <code>--save</code></li><li><code>-y</code>: <code>--yes</code></li><li><code>-n</code>: <code>--yes false</code></li><li><code>ll</code> and <code>la</code> commands: <code>ls --long</code></li></ul>
 <p>If the specified configuration param resolves unambiguously to a known
 configuration parameter, then it is expanded to that configuration
@ -200,26 +200,6 @@ to trust only that specific signing authority.</p>
 <p>The location of npm's cache directory.  See <code><a href="../doc/cache.html">cache(1)</a></code></p>
 <h3 id="cache-max">cache-max</h3>
 <ul><li>Default: Infinity</li><li>Type: Number</li></ul>
 <p>The maximum time (in seconds) to keep items in the registry cache before
 re-checking against the registry.</p>
 <p>Note that no purging is done unless the <code>npm cache clean</code> command is
 explicitly used, and that only GET requests use the cache.</p>
 <h3 id="cache-min">cache-min</h3>
 <ul><li>Default: 0</li><li>Type: Number</li></ul>
 <p>The minimum time (in seconds) to keep items in the registry cache before
 re-checking against the registry.</p>
 <p>Note that no purging is done unless the <code>npm cache clean</code> command is
 explicitly used, and that only GET requests use the cache.</p>
 <h3 id="color">color</h3>
 <ul><li>Default: true on Posix, false on Windows</li><li>Type: Boolean or <code>"always"</code></li></ul>
@ -320,12 +300,6 @@ user.</p>
 <p>A proxy to use for outgoing https requests.</p>
 <h3 id="user-agent">user-agent</h3>
 <ul><li>Default: npm/{npm.version} node/{process.version}</li><li>Type: String</li></ul>
 <p>Sets a User-Agent to the request header</p>
 <h3 id="ignore">ignore</h3>
 <ul><li>Default: ""</li><li>Type: string</li></ul>
@ -341,7 +315,7 @@ from packages when building tarballs.</p>
 <h3 id="init-author-name">init.author.name</h3>
-<ul><li>Default: ""</li><li>Type: String</li></ul>
+<ul><li>Default: "0.0.0"</li><li>Type: String</li></ul>
 <p>The value <code>npm init</code> should use by default for the package author's name.</p>
@ -357,16 +331,6 @@ from packages when building tarballs.</p>
 <p>The value <code>npm init</code> should use by default for the package author's homepage.</p>
 <h3 id="json">json</h3>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
 <p>Whether or not to output JSON data, rather than the normal output.</p>
 <p>This feature is currently experimental, and the output data structures
 for many commands is either not implemented in JSON yet, or subject to
 change.  Only the output from <code>npm ls --json</code> is currently valid.</p>
 <h3 id="link">link</h3>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
@ -516,22 +480,6 @@ this as true.</p>
 <p>Only works if there is already a package.json file present.</p>
 <h3 id="save-dev">save-dev</h3>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
 <p>Save installed packages to a package.json file as devDependencies.</p>
 <p>Only works if there is already a package.json file present.</p>
 <h3 id="save-optional">save-optional</h3>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
 <p>Save installed packages to a package.json file as optionalDependencies.</p>
 <p>Only works if there is already a package.json file present.</p>
 <h3 id="searchopts">searchopts</h3>
 <ul><li>Default: ""</li><li>Type: String</li></ul>
@ -653,15 +601,6 @@ this value.  Thus, the defaults are <code>0755</code> and <code>0644</code> resp
 <p>Only relevant when specified explicitly on the command line.</p>
 <h3 id="versions">versions</h3>
 <ul><li>Default: false</li><li>Type: boolean</li></ul>
 <p>If true, output the npm version as well as node's <code>process.versions</code>
 hash, and exit successfully.</p>
 <p>Only relevant when specified explicitly on the command line.</p>
 <h3 id="viewer">viewer</h3>
 <ul><li>Default: "man" on Posix, "browser" on Windows</li><li>Type: path</li></ul>
@ -684,7 +623,7 @@ then answer "no" to any prompt.</p>
 <ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
 </div>
-<p id="footer">config &mdash; npm@1.1.18</p>
+<p id="footer">config &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/deprecate.html
+++ b/deps/npm/html/doc/deprecate.html
@ -29,7 +29,7 @@ something like this:</p>
 <ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
 </div>
-<p id="footer">deprecate &mdash; npm@1.1.18</p>
+<p id="footer">deprecate &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/developers.html
+++ b/deps/npm/html/doc/developers.html
@ -28,23 +28,13 @@ topic, or <code>npm help thing</code> to see the same information.</p>
 <p>A package is:</p>
-<ul><li>a) a folder containing a program described by a package.json file</li><li>b) a gzipped tarball containing (a)</li><li>c) a url that resolves to (b)</li><li>d) a <code>&lt;name&gt;@&lt;version&gt;</code> that is published on the registry with (c)</li><li>e) a <code>&lt;name&gt;@&lt;tag&gt;</code> that points to (d)</li><li>f) a <code>&lt;name&gt;</code> that has a "latest" tag satisfying (e)</li><li>g) a <code>git</code> url that, when cloned, results in (a).</li></ul>
+<ul><li>a) a folder containing a program described by a package.json file</li><li>b) a gzipped tarball containing (a)</li><li>c) a url that resolves to (b)</li><li>d) a <code>&lt;name&gt;@&lt;version&gt;</code> that is published on the registry with (c)</li><li>e) a <code>&lt;name&gt;@&lt;tag&gt;</code> that points to (d)</li><li>f) a <code>&lt;name&gt;</code> that has a "latest" tag satisfying (e)</li></ul>
 <p>Even if you never publish your package, you can still get a lot of
 benefits of using npm if you just want to write a node program (a), and
 perhaps if you also want to be able to easily install it elsewhere
 after packing it up into a tarball (b).</p>
 <p>Git urls can be of the form:</p>
 <pre><code>git://github.com/user/project.git#commit-ish
 git+ssh://user@hostname:project.git#commit-ish
 git+http://user@hostname/project/blah.git#commit-ish
 git+https://user@hostname/project/blah.git#commit-ish</code></pre>
 <p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as
 an argument to <code>git checkout</code>.  The default is <code>master</code>.</p>
 <h2 id="The-package-json-File">The package.json File</h2>
 <p>You need to have a <code>package.json</code> file in the root of your project to do
@ -160,7 +150,7 @@ from a fresh checkout.</p>
 <ul><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
 </div>
-<p id="footer">developers &mdash; npm@1.1.18</p>
+<p id="footer">developers &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/disputes.html
+++ b/deps/npm/html/doc/disputes.html
@ -80,7 +80,7 @@ license statement)</li><li>Illegal content.</li></ol>
 <ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li></ul>
 </div>
-<p id="footer">disputes &mdash; npm@1.1.18</p>
+<p id="footer">disputes &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/docs.html
+++ b/deps/npm/html/doc/docs.html
@ -37,7 +37,7 @@ config param.</p>
 <ul><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
 </div>
-<p id="footer">docs &mdash; npm@1.1.18</p>
+<p id="footer">docs &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/edit.html
+++ b/deps/npm/html/doc/edit.html
@ -37,7 +37,7 @@ or <code>"notepad"</code> on Windows.</li><li>Type: path</li></ul>
 <ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/explore.html">explore(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
 </div>
-<p id="footer">edit &mdash; npm@1.1.18</p>
+<p id="footer">edit &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/explore.html
+++ b/deps/npm/html/doc/explore.html
@ -40,7 +40,7 @@ Windows</li><li>Type: path</li></ul>
 <ul><li><a href="../doc/submodule.html">submodule(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/edit.html">edit(1)</a></li><li><a href="../doc/rebuild.html">rebuild(1)</a></li><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
 </div>
-<p id="footer">explore &mdash; npm@1.1.18</p>
+<p id="footer">explore &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/faq.html
+++ b/deps/npm/html/doc/faq.html
@ -241,7 +241,7 @@ We'll have someone kick it or something.</p>
 <ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li></ul>
 </div>
-<p id="footer">faq &mdash; npm@1.1.18</p>
+<p id="footer">faq &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/folders.html
+++ b/deps/npm/html/doc/folders.html
@ -205,7 +205,7 @@ cannot be found elsewhere.  See <code><a href="../doc/json.html">json(1)</a></co
 <ul><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/pack.html">pack(1)</a></li><li><a href="../doc/cache.html">cache(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li></ul>
 </div>
-<p id="footer">folders &mdash; npm@1.1.18</p>
+<p id="footer">folders &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/help-search.html
+++ b/deps/npm/html/doc/help-search.html
@ -38,7 +38,7 @@ where the terms were found in the documentation.</p>
 <ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/help.html">help(1)</a></li></ul>
 </div>
-<p id="footer">help-search &mdash; npm@1.1.18</p>
+<p id="footer">help-search &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/help.html
+++ b/deps/npm/html/doc/help.html
@ -36,7 +36,7 @@ matches are equivalent to specifying a topic name.</p>
 <ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/README.html">README</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/help-search.html">help-search(1)</a></li><li><a href="../doc/index.html">index(1)</a></li></ul>
 </div>
-<p id="footer">help &mdash; npm@1.1.18</p>
+<p id="footer">help &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/index.html
+++ b/deps/npm/html/doc/index.html
@ -178,10 +178,6 @@
 <p> The semantic versioner for npm</p>
 <h2 id="npm-shrinkwrap-1"><a href="../doc/shrinkwrap.html">shrinkwrap(1)</a></h2>
 <p> Lock down dependency versions</p>
 <h2 id="npm-star-1"><a href="../doc/star.html">star(1)</a></h2>
 <p> Mark your favorite packages</p>
@ -336,10 +332,6 @@
 <p> Search for packages</p>
 <h2 id="npm-shrinkwrap-3"><a href="../api/shrinkwrap.html">shrinkwrap(3)</a></h2>
 <p> programmatically generate package shrinkwrap file</p>
 <h2 id="npm-start-3"><a href="../api/start.html">start(3)</a></h2>
 <p> Start a package</p>
@ -384,7 +376,7 @@
 <p> Display npm username</p>
 </div>
-<p id="footer">index &mdash; npm@1.1.18</p>
+<p id="footer">index &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/init.html
+++ b/deps/npm/html/doc/init.html
@ -29,7 +29,7 @@ without a really good reason to do so.</p>
 <ul><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/version.html">version(1)</a></li></ul>
 </div>
-<p id="footer">init &mdash; npm@1.1.18</p>
+<p id="footer">init &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/install.html
+++ b/deps/npm/html/doc/install.html
@ -14,17 +14,14 @@
 npm install &lt;tarball file&gt;
 npm install &lt;tarball url&gt;
 npm install &lt;folder&gt;
-npm install &lt;name&gt; [--save|--save-dev|--save-optional]
+npm install &lt;name&gt;
 npm install &lt;name&gt;@&lt;tag&gt;
 npm install &lt;name&gt;@&lt;version&gt;
 npm install &lt;name&gt;@&lt;version range&gt;
 npm install &lt;name&gt;@&lt;version range&gt;</code></pre>
 <h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>This command installs a package, and any packages that it depends on. If the
+<p>This command installs a package, and any packages that it depends on.</p>
 package has a shrinkwrap file, the installation of dependencies will be driven
 by that. See <a href="../doc/shrinkwrap.html">shrinkwrap(1)</a>.</p>
 <p>A <code>package</code> is:</p>
@ -35,29 +32,33 @@ benefits of using npm if you just want to write a node program (a), and
 perhaps if you also want to be able to easily install it elsewhere
 after packing it up into a tarball (b).</p>
-<ul><li><p><code>npm install</code> (in package directory, no arguments):</p><p>Install the dependencies in the local node_modules folder.</p><p>In global mode (ie, with <code>-g</code> or <code>--global</code> appended to the command),
+<ul><li><p><code>npm install</code> (in package directory, no arguments):
 Install the dependencies in the local node_modules folder.</p><p>In global mode (ie, with <code>-g</code> or <code>--global</code> appended to the command),
 it installs the current package context (ie, the current working
-directory) as a global package.</p></li><li><p><code>npm install &lt;folder&gt;</code>:</p><p>Install a package that is sitting in a folder on the filesystem.</p></li><li><p><code>npm install &lt;tarball file&gt;</code>:</p><p>Install a package that is sitting on the filesystem.  Note: if you just want
+directory) as a global package.</p></li><li><p><code>npm install &lt;folder&gt;</code>:
 Install a package that is sitting in a folder on the filesystem.</p></li><li><p><code>npm install &lt;tarball file&gt;</code>:
 Install a package that is sitting on the filesystem.  Note: if you just want
 to link a dev directory into your npm root, you can do this more easily by
-using <code>npm link</code>.</p><p>Example:</p><pre><code>  npm install ./package.tgz</code></pre></li><li><p><code>npm install &lt;tarball url&gt;</code>:</p><p>Fetch the tarball url, and then install it.  In order to distinguish between
+using <code>npm link</code>.</p><p>Example:</p><pre><code>npm install ./package.tgz</code></pre></li><li><p><code>npm install &lt;tarball url&gt;</code>:
-this and other options, the argument must start with "http://" or "https://"</p><p>Example:</p><pre><code>  npm install https://github.com/indexzero/forever/tarball/v0.5.6</code></pre></li><li><p><code>npm install &lt;name&gt; [--save|--save-dev|--save-optional]</code>:</p><p>Do a <code>&lt;name&gt;@&lt;tag&gt;</code> install, where <code>&lt;tag&gt;</code> is the "tag" config. (See
+Fetch the tarball url, and then install it.  In order to distinguish between
-<code><a href="../doc/config.html">config(1)</a></code>.)</p><p>In most cases, this will install the latest version
+this and other options, the argument must start with "http://" or "https://"</p><p>Example:</p><pre><code>npm install https://github.com/indexzero/forever/tarball/v0.5.6</code></pre></li><li><p><code>npm install &lt;name&gt;</code>:
-of the module published on npm.</p><p>Example:</p><p>      npm install sax</p><p><code>npm install</code> takes 3 exclusive, optional flags which save or update
+Do a <code>&lt;name&gt;@&lt;tag&gt;</code> install, where <code>&lt;tag&gt;</code> is the "tag" config. (See
-the package version in your main package.json:</p><ul><li><p><code>--save</code>: Package will appear in your <code>dependencies</code>.</p></li><li><p><code>--save-dev</code>: Package will appear in your <code>devDependencies</code>.</p></li><li><p><code>--save-optional</code>: Package will appear in your <code>optionalDependencies</code>.</p><p>Examples:</p><p>  npm install sax --save
+<code><a href="../doc/config.html">config(1)</a></code>)</p><p>Example:</p><pre><code>npm install sax</code></pre><p><strong>Note</strong>: If there is a file or folder named <code>&lt;name&gt;</code> in the current
  npm install node-tap --save-dev
  npm install dtrace-provider --save-optional</p><p><strong>Note</strong>: If there is a file or folder named <code>&lt;name&gt;</code> in the current
 working directory, then it will try to install that, and only try to
-fetch the package by name if it is not valid.</p></li></ul></li><li><p><code>npm install &lt;name&gt;@&lt;tag&gt;</code>:</p><p>Install the version of the package that is referenced by the specified tag.
+fetch the package by name if it is not valid.</p></li><li><p><code>npm install &lt;name&gt;@&lt;tag&gt;</code>:
 Install the version of the package that is referenced by the specified tag.
 If the tag does not exist in the registry data for that package, then this
-will fail.</p><p>Example:</p><pre><code>  npm install sax@latest</code></pre></li><li><p><code>npm install &lt;name&gt;@&lt;version&gt;</code>:</p><p>Install the specified version of the package.  This will fail if the version
+will fail.</p><p>Example:</p><pre><code>npm install sax@latest</code></pre></li><li><p><code>npm install &lt;name&gt;@&lt;version&gt;</code>:
-has not been published to the registry.</p><p>Example:</p><pre><code>  npm install sax@0.1.1</code></pre></li><li><p><code>npm install &lt;name&gt;@&lt;version range&gt;</code>:</p><p>Install a version of the package matching the specified version range.  This
+Install the specified version of the package.  This will fail if the version
 has not been published to the registry.</p><p>Example:</p><pre><code>npm install sax@0.1.1</code></pre></li><li><p><code>npm install &lt;name&gt;@&lt;version range&gt;</code>:
 Install a version of the package matching the specified version range.  This
 will follow the same rules for resolving dependencies described in <code><a href="../doc/json.html">json(1)</a></code>.</p><p>Note that most version ranges must be put in quotes so that your shell will
-treat it as a single argument.</p><p>Example:</p><p>      npm install sax@"&gt;=0.1.0 &lt;0.2.0"</p></li><li><p><code>npm install &lt;git remote url&gt;</code>:</p><p>Install a package by cloning a git remote url.  The format of the git
+treat it as a single argument.</p><p>Example:</p><pre><code>npm install sax@"&gt;=0.1.0 &lt;0.2.0"</code></pre></li><li><p><code>npm install &lt;git remote url&gt;</code>:</p><p>Install a package by cloning a git remote url.  The format of the git
-url is:</p><p>      &lt;protocol&gt;://[&lt;user&gt;@]&lt;hostname&gt;&lt;separator&gt;&lt;path&gt;[#&lt;commit-ish&gt;]</p><p><code>&lt;protocol&gt;</code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, or
+url is:</p><pre><code>&lt;protocol&gt;://[&lt;user&gt;@]&lt;hostname&gt;&lt;separator&gt;&lt;path&gt;[#&lt;commit-ish&gt;]</code></pre><p><code>&lt;protocol&gt;</code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, or
 <code>git+https</code>.  If no <code>&lt;commit-ish&gt;</code> is specified, then <code>master</code> is
-used.</p><p>Examples:</p><pre><code>  git+ssh://git@github.com:isaacs/npm.git#v1.0.27
+used.</p><p>Examples:</p><pre><code>git+ssh://git@github.com:isaacs/npm.git#v1.0.27
-  git+https://isaacs@github.com/isaacs/npm.git
+git+https://isaacs@github.com/isaacs/npm.git
-  git://github.com/isaacs/npm.git#v1.0.27</code></pre></li></ul>
+git://github.com/isaacs/npm.git#v1.0.27</code></pre></li></ul>
 <p>You may combine multiple arguments, and even multiple types of arguments.
 For example:</p>
@ -131,9 +132,9 @@ affects a real use-case, it will be investigated.</p>
 <h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/rebuild.html">rebuild(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/tag.html">tag(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/shrinkwrap.html">shrinkwrap(1)</a></li></ul>
+<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/rebuild.html">rebuild(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/tag.html">tag(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li></ul>
 </div>
-<p id="footer">install &mdash; npm@1.1.18</p>
+<p id="footer">install &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/json.html
+++ b/deps/npm/html/doc/json.html
@ -311,7 +311,7 @@ space-separated descriptors, OR a range like "fromVersion - toVersion"</p>
 <p>Version range descriptors may be any of the following styles, where "version"
 is a semver compatible version identifier.</p>
-<ul><li><code>version</code> Must match <code>version</code> exactly</li><li><code>=version</code> Same as just <code>version</code></li><li><code>&gt;version</code> Must be greater than <code>version</code></li><li><code>&gt;=version</code> etc</li><li><code>&lt;version</code></li><li><code>&lt;=version</code></li><li><code>~version</code> See 'Tilde Version Ranges' below</li><li><code>1.2.x</code> See 'X Version Ranges' below</li><li><code>http://...</code> See 'URLs as Dependencies' below</li><li><code>*</code> Matches any version</li><li><code>""</code> (just an empty string) Same as <code>*</code></li><li><code>version1 - version2</code> Same as <code>&gt;=version1 &lt;=version2</code>.</li><li><code>range1 || range2</code> Passes if either range1 or range2 are satisfied.</li><li><code>git...</code> See 'Git URLs as Dependencies' below</li></ul>
+<ul><li><code>version</code> Must match <code>version</code> exactly</li><li><code>=version</code> Same as just <code>version</code></li><li><code>&gt;version</code> Must be greater than <code>version</code></li><li><code>&gt;=version</code> etc</li><li><code>&lt;version</code></li><li><code>&lt;=version</code></li><li><code>~version</code> See 'Tilde Version Ranges' below</li><li><code>1.2.x</code> See 'X Version Ranges' below</li><li><code>http://...</code> See 'URLs as Dependencies' below</li><li><code>*</code> Matches any version</li><li><code>""</code> (just an empty string) Same as <code>*</code></li><li><code>version1 - version2</code> Same as <code>&gt;=version1 &lt;=version2</code>.</li><li><code>range1 || range2</code> Passes if either range1 or range2 are satisfied.</li></ul>
 <p>For example, these are all valid:</p>
@ -360,18 +360,6 @@ of a version range.</p>
 <p>This tarball will be downloaded and installed locally to your package at
 install time.</p>
 <h3 id="Git-URLs-as-Dependencies">Git URLs as Dependencies</h3>
 <p>Git urls can be of the form:</p>
 <pre><code>git://github.com/user/project.git#commit-ish
 git+ssh://user@hostname:project.git#commit-ish
 git+http://user@hostname/project/blah.git#commit-ish
 git+https://user@hostname/project/blah.git#commit-ish</code></pre>
 <p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as
 an argument to <code>git checkout</code>.  The default is <code>master</code>.</p>
 <h2 id="devDependencies">devDependencies</h2>
 <p>If someone is planning on downloading and using your module in their
@ -411,36 +399,6 @@ are capable of properly installing your program.  For example:</p>
 <pre><code>{ "engines" : { "npm" : "~1.0.20" } }</code></pre>
 <h2 id="os">os</h2>
 <p>You can specify which operating systems your
 module will run on:</p>
 <pre><code>"os" : [ "darwin", "linux" ]</code></pre>
 <p>You can also blacklist instead of whitelist operating systems,
 just prepend the blacklisted os with a '!':</p>
 <pre><code>"os" : [ "!win32" ]</code></pre>
 <p>The host operating system is determined by <code>process.platform</code></p>
 <p>It is allowed to both blacklist, and whitelist, although there isn't any
 good reason to do this.</p>
 <h2 id="cpu">cpu</h2>
 <p>If your code only runs on certain cpu architectures,
 you can specify which ones.</p>
 <pre><code>"cpu" : [ "x64", "ia32" ]</code></pre>
 <p>Like the <code>os</code> option, you can also blacklist architectures:</p>
 <pre><code>"cpu" : [ "!arm", "!mips" ]</code></pre>
 <p>The host architecture is determined by <code>process.arch</code></p>
 <h2 id="preferGlobal">preferGlobal</h2>
 <p>If your package is primarily a command-line application that should be
@ -457,7 +415,7 @@ to publish it.</p>
 <p>This is a way to prevent accidental publication of private repositories.
 If you would like to ensure that a given package is only ever published
-to a specific registry (for example, an internal registry),
+to a speciic registry (for example, an internal registry),
 then use the <code>publishConfig</code> hash described below
 to override the <code>registry</code> config param at publish-time.</p>
@ -478,7 +436,7 @@ overridden.</p>
 <ul><li><a href="../doc/semver.html">semver(1)</a></li><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/version.html">version(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li></ul>
 </div>
-<p id="footer">json &mdash; npm@1.1.18</p>
+<p id="footer">json &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/link.html
+++ b/deps/npm/html/doc/link.html
@ -58,7 +58,7 @@ installation target into your project's <code>node_modules</code> folder.</p>
 <ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
 </div>
-<p id="footer">link &mdash; npm@1.1.18</p>
+<p id="footer">link &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/list.html
+++ b/deps/npm/html/doc/list.html
@ -29,12 +29,6 @@ like with any other command, such as <code>-g</code> to list global packages.</p
 <h2 id="CONFIGURATION">CONFIGURATION</h2>
 <h3 id="json">json</h3>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
 <p>Show information in JSON format.</p>
 <h3 id="long">long</h3>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
@ -58,7 +52,7 @@ project.</p>
 <ul><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/prune.html">prune(1)</a></li><li><a href="../doc/outdated.html">outdated(1)</a></li><li><a href="../doc/update.html">update(1)</a></li></ul>
 </div>
-<p id="footer">list &mdash; npm@1.1.18</p>
+<p id="footer">list &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/npm.html
+++ b/deps/npm/html/doc/npm.html
@ -14,7 +14,7 @@
 <h2 id="VERSION">VERSION</h2>
-<p>1.1.18</p>
+<p>1.1.0-2</p>
 <h2 id="DESCRIPTION">DESCRIPTION</h2>
@ -135,7 +135,7 @@ will no doubt tell you to put the output in a gist or email.</p>
 <ul><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/README.html">README</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/index.html">index(1)</a></li><li><a href="../api/npm.html">npm(3)</a></li></ul>
 </div>
-<p id="footer">npm &mdash; npm@1.1.18</p>
+<p id="footer">npm &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/outdated.html
+++ b/deps/npm/html/doc/outdated.html
@ -21,7 +21,7 @@ packages are currently outdated.</p>
 <ul><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li></ul>
 </div>
-<p id="footer">outdated &mdash; npm@1.1.18</p>
+<p id="footer">outdated &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/owner.html
+++ b/deps/npm/html/doc/owner.html
@ -34,7 +34,7 @@ that is not implemented at this time.</p>
 <ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/disputes.html">disputes(1)</a></li></ul>
 </div>
-<p id="footer">owner &mdash; npm@1.1.18</p>
+<p id="footer">owner &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/pack.html
+++ b/deps/npm/html/doc/pack.html
@ -29,7 +29,7 @@ overwritten the second time.</p>
 <ul><li><a href="../doc/cache.html">cache(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
 </div>
-<p id="footer">pack &mdash; npm@1.1.18</p>
+<p id="footer">pack &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/prefix.html
+++ b/deps/npm/html/doc/prefix.html
@ -20,7 +20,7 @@
 <ul><li><a href="../doc/root.html">root(1)</a></li><li><a href="../doc/bin.html">bin(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
 </div>
-<p id="footer">prefix &mdash; npm@1.1.18</p>
+<p id="footer">prefix &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/prune.html
+++ b/deps/npm/html/doc/prune.html
@ -25,7 +25,7 @@ package's dependencies list.</p>
 <ul><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/list.html">list(1)</a></li></ul>
 </div>
-<p id="footer">prune &mdash; npm@1.1.18</p>
+<p id="footer">prune &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/publish.html
+++ b/deps/npm/html/doc/publish.html
@ -29,7 +29,7 @@ the registry.  Overwrites when the "--force" flag is set.</p>
 <ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li><li><a href="../doc/deprecate.html">deprecate(1)</a></li><li><a href="../doc/tag.html">tag(1)</a></li></ul>
 </div>
-<p id="footer">publish &mdash; npm@1.1.18</p>
+<p id="footer">publish &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/rebuild.html
+++ b/deps/npm/html/doc/rebuild.html
@ -25,7 +25,7 @@ the new binary.</p>
 <ul><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
 </div>
-<p id="footer">rebuild &mdash; npm@1.1.18</p>
+<p id="footer">rebuild &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/registry.html
+++ b/deps/npm/html/doc/registry.html
@ -97,7 +97,7 @@ ask for help on the <a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com
 <ul><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/disputes.html">disputes(1)</a></li></ul>
 </div>
-<p id="footer">registry &mdash; npm@1.1.18</p>
+<p id="footer">registry &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/removing-npm.html
+++ b/deps/npm/html/doc/removing-npm.html
@ -58,7 +58,7 @@ modules.  To track those down, you can do the following:</p>
 <ul><li><a href="../doc/README.html">README</a></li><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/prune.html">prune(1)</a></li></ul>
 </div>
-<p id="footer">removing-npm &mdash; npm@1.1.18</p>
+<p id="footer">removing-npm &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/restart.html
+++ b/deps/npm/html/doc/restart.html
@ -24,7 +24,7 @@ the "start" script.</p>
 <ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
 </div>
-<p id="footer">restart &mdash; npm@1.1.18</p>
+<p id="footer">restart &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/root.html
+++ b/deps/npm/html/doc/root.html
@ -20,7 +20,7 @@
 <ul><li><a href="../doc/prefix.html">prefix(1)</a></li><li><a href="../doc/bin.html">bin(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
 </div>
-<p id="footer">root &mdash; npm@1.1.18</p>
+<p id="footer">root &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/run-script.html
+++ b/deps/npm/html/doc/run-script.html
@ -23,7 +23,7 @@ called directly, as well.</p>
 <ul><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
 </div>
-<p id="footer">run-script &mdash; npm@1.1.18</p>
+<p id="footer">run-script &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/scripts.html
+++ b/deps/npm/html/doc/scripts.html
@ -52,19 +52,6 @@ privileges.</p>
 made available regarding the setup of npm and the current state of the
 process.</p>
 <h3 id="path">path</h3>
 <p>If you depend on modules that define executable scripts, like test suites,
 then those executables will be added to the <code>PATH</code> for executing the scripts.
 So, if your package.json has this:</p>
 <pre><code>{ "name" : "foo"
 , "dependencies" : { "bar" : "0.1.x" }
 , "scripts": { "start" : "bar ./test" } }</code></pre>
 <p>then you could run <code>npm start</code> to execute the <code>bar</code> script, which is exported
 into the <code>node_modules/.bin</code> directory on <code>npm install</code>.</p>
 <h3 id="package-json-vars">package.json vars</h3>
 <p>The package.json fields are tacked onto the <code>npm_package_</code> prefix. So, for
@ -177,7 +164,7 @@ will sudo the npm command in question.</li></ul>
 <ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
 </div>
-<p id="footer">scripts &mdash; npm@1.1.18</p>
+<p id="footer">scripts &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/search.html
+++ b/deps/npm/html/doc/search.html
@ -24,7 +24,7 @@ expression characters must be escaped or quoted in most shells.)</p>
 <ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/view.html">view(1)</a></li></ul>
 </div>
-<p id="footer">search &mdash; npm@1.1.18</p>
+<p id="footer">search &mdash; npm@1.1.0-2</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")