test: debug-signal-cluster increase timeouts

The test needs a little more time to run so that it passes for all builds (eg: Windows, debug)
debug client: connect after child is ready
2026-04-28 03:01:10 -04:00 · 2014-01-13 17:51:17 -08:00 · 2014-01-13 17:42:27 -08:00 · 2014-01-13 17:35:41 -08:00 · 2014-01-13 17:09:12 -08:00
1038 changed files with 36121 additions and 14483 deletions
--- a/.gitignore
+++ b/.gitignore
@@ -42,7 +42,6 @@ ipch/
 /dist-osx
 /npm.wxs
 /tools/msvs/npm.wixobj
-/test/addons/doc-*/
 email.md
 deps/v8-*
 ./node_modules
--- a/15
+++ b/15
@@ -514,18 +514,3 @@ Benjamin Waters <benjamin.waters@outlook.com>
 Lev Gimelfarb <lev.gimelfarb@gmail.com>
 Peter Flannery <flannery.peter@ntlworld.com>
 Tuğrul Topuz <tugrultopuz@gmail.com>
-Lorenz Leutgeb <lorenz.leutgeb@gmail.com>
-Brandon Cheng <bcheng.gt@gmail.com>
-Alexis Campailla <alexis@janeasystems.com>
-Yang Tianyang <contact@ayanamist.com>
-Tom Gallacher <tomgallacher23@gmail.com>
-Jo Liss <joliss42@gmail.com>
-Jun Ma <roammm@gmail.com>
-Jacob Hoffman-Andrews <github@hoffman-andrews.com>
-Keith M Wesolowski <wesolows@joyent.com>
-Maxime Quandalle <maxime.quandalle@gmail.com>
-Doron Pagot <doronpagot@gmail.com>
-Kenan Sulayman <kenan@sly.mn>
-Christian Schulz <me@rndm.de>
-Pedro Ballesteros <nitroduna@gmail.com>
-Anton Khlynovskiy <subzey@gmail.com>
--- a/103
+++ b/103
@@ -1,57 +1,4 @@
-2014.01.29, Version 0.11.11 (Unstable)
-
-* v8: Upgrade to 3.22.24.19
-
-* http_parser: Upgrade to 2.2.1
-
-* openssl: Upgrade to 1.0.1f
-
-* uv: Upgrade to 0.11.18
-
-* async-listener: revamp of subsystem (Trevor Norris)
-
-* node: do not ever close stdio (Fedor Indutny)
-
-* http: use writev on chunked encoding (Trevor Norris)
-
-* async_wrap/timers: remove Add/RemoveAsyncListener (Trevor Norris)
-
-* child_process: better error reporting for exec (Fedor Indutny)
-
-* crypto: add newline to cert and key if not present (Fedor Indutny)
-
-* crypto: clear error in GetPeerCertificate (Fedor Indutny)
-
-* crypto: honor default ciphers in client mode (Jacob Hoffman-Andrews)
-
-* crypto: introduce .setEngine(engine, [flags]) (Fedor Indutny)
-
-* crypto: support custom pbkdf2 digest methods (Ben Noordhuis)
-
-* domain: fix off-by-one in Domain.exit() (Ryan Graham)
-
-* http: concatenate duplicate headers by default (Alex Kocharin)
-
-* http: do not emit EOF non-readable socket (Fedor Indutny)
-
-* node: fix argument parsing with -p arg (Alexis Campailla)
-
-* path: improve POSIX path.join() performance (Jo Liss)
-
-* tls: emit `clientError` on early socket close (Fedor Indutny)
-
-* tls: introduce `.setMaxSendFragment(size)` (Fedor Indutny)
-
-* tls: make cert/pfx optional in tls.createServer() (Ben Noordhuis)
-
-* tls: process accumulated input (Fedor Indutny)
-
-* tls: show human-readable error messages (Ben Noordhuis)
-
-* util: handle escaped forward slashes correctly (Tom Gallacher)
-
-
-2013.12.31, Version 0.11.10 (Unstable), 66931791f06207d1cdfea5ec1529edf3c94026d3
+2013.12.31, Version 0.11.10 (Unstable)

 * http_parser: update to 2.2

@@ -498,54 +445,6 @@
 * console: `console.dir()` bypasses inspect() methods (Nathan Rajlich)


-2014.02.18, Version 0.10.26 (Stable), cc56c62ed879ad4f93b1fdab3235c43e60f48b7e
-
-* uv: Upgrade to v0.10.25 (Timothy J Fontaine)
-
-* npm: upgrade to 1.4.3 (isaacs)
-
-* v8: support compiling with VS2013 (Fedor Indutny)
-
-* cares: backport TXT parsing fix (Fedor Indutny)
-
-* crypto: throw on SignFinal failure (Fedor Indutny)
-
-* crypto: update root certificates (Ben Noordhuis)
-
-* debugger: Fix breakpoint not showing after restart (Farid Neshat)
-
-* fs: make unwatchFile() insensitive to path (iamdoron)
-
-* net: do not re-emit stream errors (Fedor Indutny)
-
-* net: make Socket destroy() re-entrance safe (Jun Ma)
-
-* net: reset `endEmitted` on reconnect (Fedor Indutny)
-
-* node: do not close stdio implicitly (Fedor Indutny)
-
-* zlib: avoid assertion in close (Fedor Indutny)
-
-
-2014.01.23, Version 0.10.25 (Stable), b0e5f195dfce3e2b99f5091373d49f6616682596
-
-* uv: Upgrade to v0.10.23
-
-* npm: Upgrade to v1.3.24
-
-* v8: Fix enumeration for objects with lots of properties
-
-* child_process: fix spawn() optional arguments (Sam Roberts)
-
-* cluster: report more errors to workers (Fedor Indutny)
-
-* domains: exit() only affects active domains (Ryan Graham)
-
-* src: OnFatalError handler must abort() (Timothy J Fontaine)
-
-* stream: writes may return false but forget to emit drain (Yang Tianyang)
-
-
 2013.12.18, Version 0.10.24 (Stable), b7fd6bc899ccb629d790c47aee06aba87e535c41

 * uv: Upgrade to v0.10.21
--- a/66
+++ b/66
@@ -100,38 +100,26 @@ test/gc/node_modules/weak/build/Release/weakref.node:
 		--directory="$(shell pwd)/test/gc/node_modules/weak" \
 		--nodedir="$(shell pwd)"

-build-addons:
-	@if [ ! -f node ]; then make all; fi
-	rm -rf test/addons/doc-*/
-	./node tools/doc/addon-verify.js
-	$(foreach dir, \
-			$(sort $(dir $(wildcard test/addons/*/*.gyp))), \
-			./node deps/npm/node_modules/node-gyp/bin/node-gyp rebuild \
-					--directory="$(shell pwd)/$(dir)" \
-					--nodedir="$(shell pwd)" && ) echo "build done"
-
 test-gc: all test/gc/node_modules/weak/build/Release/weakref.node
 	$(PYTHON) tools/test.py --mode=release gc

-test-build: all build-addons
-
-test-all: test-build test/gc/node_modules/weak/build/Release/weakref.node
+test-all: all test/gc/node_modules/weak/build/Release/weakref.node
 	$(PYTHON) tools/test.py --mode=debug,release
 	make test-npm

-test-all-http1: test-build
+test-all-http1: all
 	$(PYTHON) tools/test.py --mode=debug,release --use-http1

-test-all-valgrind: test-build
+test-all-valgrind: all
 	$(PYTHON) tools/test.py --mode=debug,release --valgrind

-test-release: test-build
+test-release: all
 	$(PYTHON) tools/test.py --mode=release

-test-debug: test-build
+test-debug: all
 	$(PYTHON) tools/test.py --mode=debug

-test-message: test-build
+test-message: all
 	$(PYTHON) tools/test.py message

 test-simple: all
@@ -152,22 +140,40 @@ test-npm: node
 test-npm-publish: node
 	npm_package_config_publishtest=true ./node deps/npm/test/run.js

-test-addons: test-build
-	$(PYTHON) tools/test.py --mode=release addons
-
 apidoc_sources = $(wildcard doc/api/*.markdown)
 apidocs = $(addprefix out/,$(apidoc_sources:.markdown=.html)) \
          $(addprefix out/,$(apidoc_sources:.markdown=.json))

-apidoc_dirs = out/doc out/doc/api/ out/doc/api/assets
+apidoc_dirs = out/doc out/doc/api/ out/doc/api/assets out/doc/about out/doc/community out/doc/download out/doc/logos out/doc/images

 apiassets = $(subst api_assets,api/assets,$(addprefix out/,$(wildcard doc/api_assets/*)))

-website_files = \
-	out/doc/sh_main.js    \
-	out/doc/sh_javascript.min.js
+doc_images = $(addprefix out/,$(wildcard doc/images/* doc/*.jpg doc/*.png))

-doc: $(apidoc_dirs) $(website_files) $(apiassets) $(apidocs) tools/doc/ node
+website_files = \
+	out/doc/index.html    \
+	out/doc/v0.4_announcement.html   \
+	out/doc/cla.html      \
+	out/doc/sh_main.js    \
+	out/doc/sh_javascript.min.js \
+	out/doc/sh_vim-dark.css \
+	out/doc/sh.css \
+	out/doc/favicon.ico   \
+	out/doc/pipe.css \
+	out/doc/about/index.html \
+	out/doc/community/index.html \
+	out/doc/download/index.html \
+	out/doc/logos/index.html \
+	out/doc/changelog.html \
+	$(doc_images)
+
+doc: $(apidoc_dirs) $(website_files) $(apiassets) $(apidocs) tools/doc/ blog node
+
+blogclean:
+	rm -rf out/blog
+
+blog: doc/blog out/Release/node tools/blog
+	out/Release/node tools/blog/generate.js doc/blog/ out/blog/ doc/blog.html doc/rss.xml

 $(apidoc_dirs):
 	mkdir -p $@
@@ -178,6 +184,9 @@ out/doc/api/assets/%: doc/api_assets/% out/doc/api/assets/
 out/doc/changelog.html: ChangeLog doc/changelog-head.html doc/changelog-foot.html tools/build-changelog.sh node
 	bash tools/build-changelog.sh

+out/doc/%.html: doc/%.html node
+	cat $< | sed -e 's|__VERSION__|'$(VERSION)'|g' > $@
+
 out/doc/%: doc/%
 	cp -r $< $@

@@ -194,6 +203,9 @@ email.md: ChangeLog tools/email-footer.md
 blog.html: email.md
 	cat $< | ./node tools/doc/node_modules/.bin/marked > $@

+blog-upload: blog
+	rsync -r out/blog/ node@nodejs.org:~/web/nodejs.org/blog/
+
 website-upload: doc
 	rsync -r out/doc/ node@nodejs.org:~/web/nodejs.org/
 	ssh node@nodejs.org '\
@@ -406,4 +418,4 @@ cpplint:

 lint: jslint cpplint

-.PHONY: lint cpplint jslint bench clean docopen docclean doc dist distclean check uninstall install install-includes install-bin all staticlib dynamiclib test test-all test-addons build-addons website-upload pkg blog blogclean tar binary release-only bench-http-simple bench-idle bench-all bench bench-misc bench-array bench-buffer bench-net bench-http bench-fs bench-tls
+.PHONY: lint cpplint jslint bench clean docopen docclean doc dist distclean check uninstall install install-includes install-bin all staticlib dynamiclib test test-all website-upload pkg blog blogclean tar binary release-only bench-http-simple bench-idle bench-all bench bench-misc bench-array bench-buffer bench-net bench-http bench-fs bench-tls
--- a/benchmark/net/tcp-raw-pipe.js
+++ b/benchmark/net/tcp-raw-pipe.js
@@ -51,7 +51,7 @@ function server() {
      if (nread < 0)
        fail(nread, 'read');

-      var writeReq = { async: false };
+      var writeReq = {};
      err = clientHandle.writeBuffer(writeReq, buffer);

      if (err)
--- a/benchmark/net/tcp-raw-s2c.js
+++ b/benchmark/net/tcp-raw-s2c.js
@@ -68,7 +68,7 @@ function server() {
      write();

    function write() {
-      var writeReq = { async: false, oncomplete: afterWrite };
+      var writeReq = { oncomplete: afterWrite };
      var err;
      switch (type) {
        case 'buf':
@@ -82,13 +82,8 @@ function server() {
          break;
      }

-      if (err) {
+      if (err)
        fail(err, 'write');
-      } else if (!writeReq.async) {
-        process.nextTick(function() {
-          afterWrite(null, clientHandle, writeReq);
-        });
-      }
    }

    function afterWrite(err, handle, req) {
--- a/common.gypi
+++ b/common.gypi
@@ -19,14 +19,7 @@
      }, {
        'os_posix': 1,
        'v8_postmortem_support': 'true'
-      }],
-      ['GENERATOR == "ninja"', {
-        'OBJ_DIR': '<(PRODUCT_DIR)/obj',
-        'V8_BASE': '<(PRODUCT_DIR)/libv8_base.<(target_arch).a',
-      }, {
-        'OBJ_DIR': '<(PRODUCT_DIR)/obj.target',
-        'V8_BASE': '<(PRODUCT_DIR)/obj.target/deps/v8/tools/gyp/libv8_base.<(target_arch).a',
-      }],
+      }]
    ],
  },

@@ -66,6 +59,9 @@
          ['OS=="solaris"', {
            # pull in V8's postmortem metadata
            'ldflags': [ '-Wl,-z,allextract' ]
+          }, {
+            # Doesn't work with the Solaris linker.
+            'ldflags': [ '-Wl,--gc-sections' ],
          }],
          ['clang == 0 and gcc_version >= 40', {
            'cflags': [ '-fno-tree-vrp' ],  # Work around compiler bug.
--- a/deps/http_parser/.gitignore
+++ b/deps/http_parser/.gitignore
@@ -12,16 +12,3 @@ parsertrace_g
 *.Makefile
 *.so.*
 *.a
-
-
-# Visual Studio uglies
-*.suo
-*.sln
-*.vcxproj
-*.vcxproj.filters
-*.vcxproj.user
-*.opensdf
-*.ncrunchsolution*
-*.sdf
-*.vsp
-*.psess
--- a/deps/http_parser/AUTHORS
+++ b/deps/http_parser/AUTHORS
@@ -45,5 +45,3 @@ Chris Dickinson <christopher.s.dickinson@gmail.com>
 Uli Köhler <ukoehler@btronik.de>
 Charlie Somerville <charlie@charliesomerville.com>
 Fedor Indutny <fedor.indutny@gmail.com>
-runner <runner.mei@gmail.com>
-Alexis Campailla <alexis@janeasystems.com>
--- a/deps/http_parser/Makefile
+++ b/deps/http_parser/Makefile
@@ -19,7 +19,7 @@
 # IN THE SOFTWARE.

 PLATFORM ?= $(shell sh -c 'uname -s | tr "[A-Z]" "[a-z]"')
-SONAME ?= libhttp_parser.so.2.2.1
+SONAME ?= libhttp_parser.so.2.2

 CC?=gcc
 AR?=ar
--- a/deps/http_parser/http_parser.c
+++ b/deps/http_parser/http_parser.c
@@ -1509,8 +1509,8 @@ size_t http_parser_execute (http_parser *parser,
            t *= 10;
            t += ch - '0';

-            /* Overflow? Test against a conservative limit for simplicity. */
-            if ((ULLONG_MAX - 10) / 10 < parser->content_length) {
+            /* Overflow? */
+            if (t < parser->content_length || t == ULLONG_MAX) {
              SET_ERRNO(HPE_INVALID_CONTENT_LENGTH);
              goto error;
            }
@@ -1782,8 +1782,8 @@ size_t http_parser_execute (http_parser *parser,
        t *= 16;
        t += unhex_val;

-        /* Overflow? Test against a conservative limit for simplicity. */
-        if ((ULLONG_MAX - 16) / 16 < parser->content_length) {
+        /* Overflow? */
+        if (t < parser->content_length || t == ULLONG_MAX) {
          SET_ERRNO(HPE_INVALID_CONTENT_LENGTH);
          goto error;
        }
--- a/deps/http_parser/http_parser.h
+++ b/deps/http_parser/http_parser.h
@@ -27,7 +27,7 @@ extern "C" {
 /* Also update SONAME in the Makefile whenever you change these. */
 #define HTTP_PARSER_VERSION_MAJOR 2
 #define HTTP_PARSER_VERSION_MINOR 2
-#define HTTP_PARSER_VERSION_PATCH 1
+#define HTTP_PARSER_VERSION_PATCH 0

 #include <sys/types.h>
 #if defined(_WIN32) && !defined(__MINGW32__) && (!defined(_MSC_VER) || _MSC_VER<1600)
--- a/deps/http_parser/test.c
+++ b/deps/http_parser/test.c
@@ -2938,7 +2938,7 @@ test_header_content_length_overflow_error (void)
  "HTTP/1.1 200 OK\r\n"                                                       \
  "Content-Length: " #size "\r\n"                                             \
  "\r\n"
-  const char a[] = X(1844674407370955160);  /* 2^64 / 10 - 1 */
+  const char a[] = X(18446744073709551614); /* 2^64-2 */
  const char b[] = X(18446744073709551615); /* 2^64-1 */
  const char c[] = X(18446744073709551616); /* 2^64   */
 #undef X
@@ -2956,7 +2956,7 @@ test_chunk_content_length_overflow_error (void)
    "\r\n"                                                                    \
    #size "\r\n"                                                              \
    "..."
-  const char a[] = X(FFFFFFFFFFFFFFE);   /* 2^64 / 16 - 1 */
+  const char a[] = X(FFFFFFFFFFFFFFFE);  /* 2^64-2 */
  const char b[] = X(FFFFFFFFFFFFFFFF);  /* 2^64-1 */
  const char c[] = X(10000000000000000); /* 2^64   */
 #undef X
--- a/deps/npm/AUTHORS
+++ b/deps/npm/AUTHORS
@@ -115,44 +115,3 @@ Vaz Allen <vaz@tryptid.com>
 elisee <elisee@sparklin.org>
 Evan You <yyx990803@gmail.com>
 Wil Moore III <wil.moore@wilmoore.com>
-Dylan Greene <dylang@gmail.com>
-zeke <zeke@sikelianos.com>
-Andrew Horton <andrew.j.horton@gmail.com>
-Denis Gladkikh <outcoldman@gmail.com>
-Daniel Santiago <daniel.santiago@highlevelwebs.com>
-Alex Kocharin <alex@kocharin.ru>
-Evan Lucas <evanlucas@me.com>
-Steve Mason <stevem@brandwatch.com>
-Quinn Slack <qslack@qslack.com>
-Sébastien Santoro <dereckson@espace-win.org>
-CamilleM <camille.moulin@alterway.fr>
-Tom Huang <hzlhu.dargon@gmail.com>
-Sergey Belov <peimei@ya.ru>
-Younghoon Park <sola92@gmail.com>
-Yazhong Liu <yorkiefixer@gmail.com>
-Mikola Lysenko <mikolalysenko@gmail.com>
-Rafael de Oleza <rafa@spotify.com>
-Yeonghoon Park <sola92@gmail.com>
-Franck Cuny <franck.cuny@gmail.com>
-Alan Shaw <alan@freestyle-developments.co.uk>
-Alex Rodionov <p0deje@gmail.com>
-Alexej Yaroshevich <alex@qfox.ru>
-Elan Shanker <elan.shanker@gmail.com>
-François Frisch <francoisfrisch@gmail.com>
-Gabriel Falkenberg <gabriel.falkenberg@gmail.com>
-Jason Diamond <jason@diamond.name>
-Jess Martin <jessmartin@gmail.com>
-Jon Spencer <jon@jonspencer.ca>
-Matt Colyer <matt@colyer.name>
-Matt McClure <matt.mcclure@mapmyfitness.com>
-Maximilian Antoni <maximilian.antoni@juliusbaer.com>
-Nicholas Kinsey <pyro@feisty.io>
-Paulo Cesar <pauloc062@gmail.com>
-Quim Calpe <quim@kalpe.com>
-Robert Gieseke <robert.gieseke@gmail.com>
-Spain Train <michael.spainhower@opower.com>
-TJ Holowaychuk <tj@vision-media.ca>
-Thom Blake <tblake@brightroll.com>
-Trevor Burnham <tburnham@hubspot.com>
-bitspill <bitspill+github@bitspill.net>
-Neil Gentleman <ngentleman@gmail.com>
--- a/deps/npm/CONTRIBUTING.md
+++ b/deps/npm/CONTRIBUTING.md
@@ -1,9 +0,0 @@
-## Before you submit a new issue
-
-* Check if there's a simple solution in the
-  [Troubleshooting](https://github.com/npm/npm/wiki/Troubleshooting)
-  wiki.
-* [Search for similar
-  issues](https://github.com/npm/npm/search?q=Similar%20issues&type=Issues).
-* Ensure your new issue conforms to the [Contributing
-  Guidelines](https://github.com/npm/npm/wiki/Contributing-Guidelines).
--- a/deps/npm/LICENSE
+++ b/deps/npm/LICENSE
@@ -1,4 +1,4 @@
-Copyright (c) npm, Inc. and Contributors
+Copyright (c) Isaac Z. Schlueter
 All rights reserved.

 npm is released under the Artistic License 2.0.
@@ -214,7 +214,7 @@ ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 --------


-"Node.js" and "node" trademark Joyent, Inc.  npm is not officially
+"Node.js" and "node" trademark Joyent, Inc. npm is not officially
 part of the Node.js project, and is neither owned by nor
 officially affiliated with Joyent, Inc.

--- a/deps/npm/Makefile
+++ b/deps/npm/Makefile
@@ -192,6 +192,9 @@ doc-publish: doc
    html/doc/* \
    node@npmjs.org:/home/node/npm-www/doc
 	rsync -vazu --stats --no-implied-dirs --delete \
+    html/static/webfonts/ \
+    node@npmjs.org:/home/node/npm-www/static/webfonts
+	rsync -vazu --stats --no-implied-dirs --delete \
    html/static/style.css \
    node@npmjs.org:/home/node/npm-www/static/
 	#cleanup
--- a/deps/npm/README.md
+++ b/deps/npm/README.md
@@ -169,61 +169,58 @@ help config` to learn about all the options you can set there.

 ## More Docs

-Check out the [docs](https://www.npmjs.org/doc/),
-especially the [faq](https://www.npmjs.org/doc/faq.html).
+Check out the [docs](https://npmjs.org/doc/),
+especially the [faq](https://npmjs.org/doc/faq.html).

 You can use the `npm help` command to read any of them.

 If you're a developer, and you want to use npm to publish your program,
-you should [read this](https://www.npmjs.org/doc/developers.html)
+you should [read this](https://npmjs.org/doc/developers.html)

 ## Legal Stuff

-"npm" and "The npm Registry" are owned by npm, Inc.
+"npm" and "the npm registry" are owned by Isaac Z. Schlueter.
 All rights reserved.  See the included LICENSE file for more details.

-"Node.js" and "node" are trademarks owned by Joyent, Inc.
+"Node.js" and "node" are trademarks owned by Joyent, Inc.  npm is not
+officially part of the Node.js project, and is neither owned by nor
+officially affiliated with Joyent, Inc.

-Modules published on the npm registry are not officially endorsed by
-npm, Inc. or the Node.js project.
+The packages in the npm registry are not part of npm itself, and are the
+sole property of their respective maintainers.  While every effort is
+made to ensure accountability, there is absolutely no guarantee,
+warrantee, or assertion made as to the quality, fitness for a specific
+purpose, or lack of malice in any given npm package.  Modules
+published on the npm registry are not affiliated with or endorsed by
+Joyent, Inc., Isaac Z. Schlueter, Ryan Dahl, or the Node.js project.

-Data published to the npm registry is not part of npm itself, and is
-the sole property of the publisher.  While every effort is made to
-ensure accountability, there is absolutely no guarantee, warrantee, or
-assertion expressed or implied as to the quality, fitness for a
-specific purpose, or lack of malice in any given npm package.
+If you have a complaint about a package in the npm registry, and cannot
+resolve it with the package owner, please express your concerns to
+Isaac Z. Schlueter at <i@izs.me>.

-If you have a complaint about a package in the public npm registry,
-and cannot [resolve it with the package
-owner](https://www.npmjs.org/doc/misc/npm-disputes.html), please email
-<support@npmjs.com> and explain the situation.
+### In plain english

-Any data published to The npm Registry (including user account
-information) may be removed or modified at the sole discretion of the
-npm server administrators.
-
-### In plainer english
-
-npm is the property of npm, Inc.
+This is mine; not my employer's, not Node's, not Joyent's, not Ryan
+Dahl's.

 If you publish something, it's yours, and you are solely accountable
-for it.
+for it.  Not me, not Node, not Joyent, not Ryan Dahl.

-If other people publish something, it's theirs.
+If other people publish something, it's theirs.  Not mine, not Node's,
+not Joyent's, not Ryan Dahl's.

-Users can publish Bad Stuff.  It will be removed promptly if reported.
-But there is no vetting process for published modules, and you use
-them at your own risk.  Please inspect the source.
+Yes, you can publish something evil.  It will be removed promptly if
+reported, and we'll lose respect for you.  But there is no vetting
+process for published modules.

-If you publish Bad Stuff, we may delete it from the registry, or even
-ban your account in extreme cases.  So don't do that.
+If this concerns you, inspect the source before using packages.

 ## BUGS

 When you find issues, please report them:

 * web:
-  <https://github.com/npm/npm/issues>
+  <https://github.com/isaacs/npm/issues>
 * email:
  <npm-@googlegroups.com>

--- a/deps/npm/doc/cli/npm-docs.md
+++ b/deps/npm/doc/cli/npm-docs.md
@@ -3,18 +3,17 @@ npm-docs(1) -- Docs for a package in a web browser maybe

 ## SYNOPSIS

-    npm docs [<pkgname> [<pkgname> ...]]
+    npm docs <pkgname>
    npm docs (with no args in a package dir)
-    npm home [<pkgname> [<pkgname> ...]]
+    npm home <pkgname>
    npm home (with no args in a package dir)

 ## DESCRIPTION

 This command tries to guess at the likely location of a package's
 documentation URL, and then tries to open it using the `--browser`
-config param. You can pass multiple package names at once. If no
-package name is provided, it will search for a `package.json` in
-the current folder and use the `name` property.
+config param. If no package name is provided, it will search for
+a `package.json` in the current folder and use the `name` property.

 ## CONFIGURATION

--- a/deps/npm/doc/cli/npm-install.md
+++ b/deps/npm/doc/cli/npm-install.md
@@ -146,9 +146,9 @@ after packing it up into a tarball (b).

    Examples:

-          git+ssh://git@github.com:npm/npm.git#v1.0.27
-          git+https://isaacs@github.com/npm/npm.git
-          git://github.com/npm/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://github.com/isaacs/npm.git#v1.0.27

 You may combine multiple arguments, and even multiple types of arguments.
 For example:
--- a/deps/npm/doc/cli/npm-ls.md
+++ b/deps/npm/doc/cli/npm-ls.md
@@ -61,12 +61,6 @@ Show parseable output instead of tree view.
 List packages in the global install prefix instead of in the current
 project.

-### depth
-
-* Type: Int
-
-Max display depth of the dependency tree.
-
 ## SEE ALSO

 * npm-config(1)
--- a/deps/npm/doc/cli/npm-outdated.md
+++ b/deps/npm/doc/cli/npm-outdated.md
@@ -14,43 +14,6 @@ The resulting field 'wanted' shows the latest version according to the
 version specified in the package.json, the field 'latest' the very latest
 version of the package.

-## CONFIGURATION
-
-### json
-
-* Default: false
-* Type: Boolean
-
-Show information in JSON format.
-
-### long
-
-* Default: false
-* Type: Boolean
-
-Show extended information.
-
-### parseable
-
-* Default: false
-* Type: Boolean
-
-Show parseable output instead of tree view.
-
-### global
-
-* Default: false
-* Type: Boolean
-
-Check packages in the global install prefix instead of in the current
-project.
-
-### depth
-
-* Type: Int
-
-Max depth for checking dependency tree.
-
 ## SEE ALSO

 * npm-update(1)
--- a/deps/npm/doc/cli/npm-search.md
+++ b/deps/npm/doc/cli/npm-search.md
@@ -3,7 +3,7 @@ npm-search(1) -- Search for packages

 ## SYNOPSIS

-    npm search [--long] [search terms ...]
+    npm search [search terms ...]
    npm s [search terms ...]
    npm se [search terms ...]

@@ -15,18 +15,6 @@ If a term starts with `/`, then it's interpreted as a regular expression.
 A trailing `/` will be ignored in this case.  (Note that many regular
 expression characters must be escaped or quoted in most shells.)

-## CONFIGURATION
-
-### long
-
-* Default: false
-* Type: Boolean
-
-Display full package descriptions and other long text across multiple
-lines. When disabled (default) search results are truncated to fit
-neatly on a single line. Modules with extremely long names will
-fall on multiple lines.
-
 ## SEE ALSO

 * npm-registry(7)
--- a/deps/npm/doc/cli/npm.md
+++ b/deps/npm/doc/cli/npm.md
@@ -114,7 +114,7 @@ easily by doing `npm view npm contributors`.
 If you would like to contribute, but don't know what to work on, check
 the issues list or ask on the mailing list.

-* <http://github.com/npm/npm/issues>
+* <http://github.com/isaacs/npm/issues>
 * <npm-@googlegroups.com>

 ## BUGS
@@ -122,7 +122,7 @@ the issues list or ask on the mailing list.
 When you find issues, please report them:

 * web:
-  <http://github.com/npm/npm/issues>
+  <http://github.com/isaacs/npm/issues>
 * email:
  <npm-@googlegroups.com>

--- a/deps/npm/doc/files/package.json.md
+++ b/deps/npm/doc/files/package.json.md
@@ -257,7 +257,7 @@ Do it like this:

    "repository" :
      { "type" : "git"
-      , "url" : "http://github.com/npm/npm.git"
+      , "url" : "http://github.com/isaacs/npm.git"
      }

    "repository" :
--- a/deps/npm/doc/misc/npm-coding-style.md
+++ b/deps/npm/doc/misc/npm-coding-style.md
@@ -133,7 +133,7 @@ string message to the callback.  Stack traces are handy.

 ## Logging

-Logging is done using the [npmlog](https://github.com/npm/npmlog)
+Logging is done using the [npmlog](https://github.com/isaacs/npmlog)
 utility.

 Please clean up logs when they are no longer helpful.  In particular,
--- a/deps/npm/doc/misc/npm-config.md
+++ b/deps/npm/doc/misc/npm-config.md
@@ -401,7 +401,7 @@ The value `npm init` should use by default for the package author's homepage.

 ### init.license

-* Default: "ISC"
+* Default: "BSD-2-Clause"
 * Type: String

 The value `npm init` should use by default for the package license.
@@ -466,7 +466,7 @@ The default is "http", which shows http, warn, and error output.
 * Type: Stream

 This is the stream that is passed to the
-[npmlog](https://github.com/npm/npmlog) module at run time.
+[npmlog](https://github.com/isaacs/npmlog) module at run time.

 It cannot be set from the command line, but if you are using npm
 programmatically, you may wish to send logs to somewhere other than
@@ -480,7 +480,7 @@ colored output if it is a TTY.
 * Default: false
 * Type: Boolean

-Show extended information in `npm ls` and `npm search`.
+Show extended information in `npm ls`

 ### message

--- a/deps/npm/doc/misc/npm-disputes.md
+++ b/deps/npm/doc/misc/npm-disputes.md
@@ -4,7 +4,7 @@ npm-disputes(7) -- Handling Module Name Disputes
 ## SYNOPSIS

 1. Get the author email with `npm owner ls <pkgname>`
-2. Email the author, CC <support@npmjs.com>
+2. Email the author, CC <i@izs.me>.
 3. After a few weeks, if there's no resolution, we'll sort it out.

 Don't squat on package names.  Publish code or move out of the way.
@@ -42,16 +42,15 @@ Joe's appropriate course of action in each case is the same.

 1. `npm owner ls foo`.  This will tell Joe the email address of the
   owner (Bob).
-2. Joe emails Bob, explaining the situation **as respectfully as
-   possible**, and what he would like to do with the module name.  He
-   adds the npm support staff <support@npmjs.com> to the CC list of
-   the email.  Mention in the email that Bob can run `npm owner add
-   joe foo` to add Joe as an owner of the `foo` package.
+2. Joe emails Bob, explaining the situation **as respectfully as possible**,
+   and what he would like to do with the module name.  He adds
+   isaacs <i@izs.me> to the CC list of the email.  Mention in the email
+   that Bob can run `npm owner add joe foo` to add Joe as an owner of
+   the `foo` package.
 3. After a reasonable amount of time, if Bob has not responded, or if
-   Bob and Joe can't come to any sort of resolution, email support
-   <support@npmjs.com> and we'll sort it out.  ("Reasonable" is
-   usually at least 4 weeks, but extra time is allowed around common
-   holidays.)
+   Bob and Joe can't come to any sort of resolution, email isaacs
+   <i@izs.me> and we'll sort it out.  ("Reasonable" is usually about 4
+   weeks, but extra time is allowed around common holidays.)

 ## REASONING

--- a/deps/npm/doc/misc/npm-faq.md
+++ b/deps/npm/doc/misc/npm-faq.md
@@ -3,7 +3,7 @@ npm-faq(7) -- Frequently Asked Questions

 ## Where can I find these docs in HTML?

-<https://www.npmjs.org/doc/>, or run:
+<https://npmjs.org/doc/>, or run:

    npm config set viewer browser

@@ -68,8 +68,7 @@ program that uses it.

 ## Whatever, I really want the old style 'everything global' style.

-Write your own package manager.  You could probably even wrap up `npm`
-in a shell script if you really wanted to.
+Write your own package manager, then.  It's not that hard.

 npm will not help you do something that is known to be a bad idea.

@@ -311,21 +310,17 @@ Go to <https://npmjs.org/forgot>.

 Either the registry is down, or node's DNS isn't able to reach out.

-To check if the registry is down, open up
-<https://registry.npmjs.org/> in a web browser.  This will also tell
-you if you are just unable to access the internet for some reason.
+To check if the registry is down, open up <http://registry.npmjs.org/>
+in a web browser.  This will also tell you if you are just unable to
+access the internet for some reason.

-If the registry IS down, let us know by emailing <support@npmjs.com>
-or posting an issue at <https://github.com/npm/npm/issues>.  If it's
-down for the world (and not just on your local network) then we're
-probably already being pinged about it.
-
-You can also often get a faster response by visiting the #npm channel
-on Freenode IRC.
+If the registry IS down, let me know by emailing <i@izs.me> or posting
+an issue at <https://github.com/isaacs/npm/issues>.  We'll have
+someone kick it or something.

 ## Why no namespaces?

-Please see this discussion: <https://github.com/npm/npm/issues/798>
+Please see this discussion: <https://github.com/isaacs/npm/issues/798>

 tl;dr - It doesn't actually make things better, and can make them worse.

@@ -335,18 +330,15 @@ There is not sufficient need to impose namespace rules on everyone.

 ## Who does npm?

-npm was originally written by Isaac Z. Schlueter, and many others have
-contributed to it, some of them quite substantially.
+`npm view npm author`

-The npm open source project, The npm Registry, and [the community
-website](https://www.npmjs.org) are maintained and operated by the
-good folks at [npm, Inc.](https://www.npmjs.com)
+`npm view npm contributors`

 ## I have a question or request not addressed here. Where should I put it?

 Post an issue on the github project:

-* <https://github.com/npm/npm/issues>
+* <https://github.com/isaacs/npm/issues>

 ## Why does npm hate me?

--- a/deps/npm/doc/misc/npm-registry.md
+++ b/deps/npm/doc/misc/npm-registry.md
@@ -14,7 +14,7 @@ account information.
 The official public npm registry is at <http://registry.npmjs.org/>.  It
 is powered by a CouchDB database at
 <http://isaacs.iriscouch.com/registry>.  The code for the couchapp is
-available at <http://github.com/npm/npmjs.org>.  npm user accounts
+available at <http://github.com/isaacs/npmjs.org>.  npm user accounts
 are CouchDB users, stored in the <http://isaacs.iriscouch.com/_users>
 database.

--- a/deps/npm/html/doc/README.html
+++ b/deps/npm/html/doc/README.html
@@ -175,61 +175,58 @@ help config</code> to learn about all the options you can set there.</p>

 <h2 id="More-Docs">More Docs</h2>

-<p>Check out the <a href="https://www.npmjs.org/doc/">docs</a>,
-especially the <a href="https://www.npmjs.org/doc/faq.html">faq</a>.</p>
+<p>Check out the <a href="https://npmjs.org/doc/">docs</a>,
+especially the <a href="https://npmjs.org/doc/faq.html">faq</a>.</p>

 <p>You can use the <code>npm help</code> command to read any of them.</p>

 <p>If you&#39;re a developer, and you want to use npm to publish your program,
-you should <a href="https://www.npmjs.org/doc/developers.html">read this</a></p>
+you should <a href="https://npmjs.org/doc/developers.html">read this</a></p>

 <h2 id="Legal-Stuff">Legal Stuff</h2>

-<p>&quot;npm&quot; and &quot;The npm Registry&quot; are owned by npm, Inc.
+<p>&quot;npm&quot; and &quot;the npm registry&quot; are owned by Isaac Z. Schlueter.
 All rights reserved.  See the included LICENSE file for more details.</p>

-<p>&quot;Node.js&quot; and &quot;node&quot; are trademarks owned by Joyent, Inc.</p>
+<p>&quot;Node.js&quot; and &quot;node&quot; are trademarks owned by Joyent, Inc.  npm is not
+officially part of the Node.js project, and is neither owned by nor
+officially affiliated with Joyent, Inc.</p>

-<p>Modules published on the npm registry are not officially endorsed by
-npm, Inc. or the Node.js project.</p>
+<p>The packages in the npm registry are not part of npm itself, and are the
+sole property of their respective maintainers.  While every effort is
+made to ensure accountability, there is absolutely no guarantee,
+warrantee, or assertion made as to the quality, fitness for a specific
+purpose, or lack of malice in any given npm package.  Modules
+published on the npm registry are not affiliated with or endorsed by
+Joyent, Inc., Isaac Z. Schlueter, Ryan Dahl, or the Node.js project.</p>

-<p>Data published to the npm registry is not part of npm itself, and is
-the sole property of the publisher.  While every effort is made to
-ensure accountability, there is absolutely no guarantee, warrantee, or
-assertion expressed or implied as to the quality, fitness for a
-specific purpose, or lack of malice in any given npm package.</p>
+<p>If you have a complaint about a package in the npm registry, and cannot
+resolve it with the package owner, please express your concerns to
+Isaac Z. Schlueter at <a href="mailto:i@izs.me">i@izs.me</a>.</p>

-<p>If you have a complaint about a package in the public npm registry,
-and cannot <a href="https://www.npmjs.org/doc/misc/npm-disputes.html">resolve it with the package
-owner</a>, please email
-<a href="mailto:support@npmjs.com">support@npmjs.com</a> and explain the situation.</p>
+<h3 id="In-plain-english">In plain english</h3>

-<p>Any data published to The npm Registry (including user account
-information) may be removed or modified at the sole discretion of the
-npm server administrators.</p>
-
-<h3 id="In-plainer-english">In plainer english</h3>
-
-<p>npm is the property of npm, Inc.</p>
+<p>This is mine; not my employer&#39;s, not Node&#39;s, not Joyent&#39;s, not Ryan
+Dahl&#39;s.</p>

 <p>If you publish something, it&#39;s yours, and you are solely accountable
-for it.</p>
+for it.  Not me, not Node, not Joyent, not Ryan Dahl.</p>

-<p>If other people publish something, it&#39;s theirs.</p>
+<p>If other people publish something, it&#39;s theirs.  Not mine, not Node&#39;s,
+not Joyent&#39;s, not Ryan Dahl&#39;s.</p>

-<p>Users can publish Bad Stuff.  It will be removed promptly if reported.
-But there is no vetting process for published modules, and you use
-them at your own risk.  Please inspect the source.</p>
+<p>Yes, you can publish something evil.  It will be removed promptly if
+reported, and we&#39;ll lose respect for you.  But there is no vetting
+process for published modules.</p>

-<p>If you publish Bad Stuff, we may delete it from the registry, or even
-ban your account in extreme cases.  So don&#39;t do that.</p>
+<p>If this concerns you, inspect the source before using packages.</p>

 <h2 id="BUGS">BUGS</h2>

 <p>When you find issues, please report them:</p>

 <ul><li>web:
-<a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li><li>email:
+<a href="https://github.com/isaacs/npm/issues">https://github.com/isaacs/npm/issues</a></li><li>email:
 <a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li></ul>

 <p>Be sure to include <em>all</em> of the output from the npm command that didn&#39;t work
@@ -242,7 +239,7 @@ will no doubt tell you to put the output in a gist or email.</p>

 <ul><li><a href="cli/npm.html">npm(1)</a></li><li><a href="misc/npm-faq.html">npm-faq(7)</a></li><li><a href="cli/npm-help.html">npm-help(1)</a></li><li><a href="misc/npm-index.html">npm-index(7)</a></li></ul>
 </div>
-<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.4.3</p>
+<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-bin.html
+++ b/deps/npm/html/doc/api/npm-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">npm-bin &mdash; npm@1.4.3</p>
+<p id="footer">npm-bin &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-bugs.html
+++ b/deps/npm/html/doc/api/npm-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">npm-bugs &mdash; npm@1.4.3</p>
+<p id="footer">npm-bugs &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-commands.html
+++ b/deps/npm/html/doc/api/npm-commands.html
@@ -28,7 +28,7 @@ usage, or <code>man 3 npm-&lt;command&gt;</code> for programmatic usage.</p>

 <ul><li><a href="../misc/npm-index.html">npm-index(7)</a></li></ul>
 </div>
-<p id="footer">npm-commands &mdash; npm@1.4.3</p>
+<p id="footer">npm-commands &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-config.html
+++ b/deps/npm/html/doc/api/npm-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">npm-config &mdash; npm@1.4.3</p>
+<p id="footer">npm-config &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-deprecate.html
+++ b/deps/npm/html/doc/api/npm-deprecate.html
@@ -32,7 +32,7 @@ install the package.</p></li></ul>

 <ul><li><a href="../api/npm-publish.html">npm-publish(3)</a></li><li><a href="../api/npm-unpublish.html">npm-unpublish(3)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li></ul>
 </div>
-<p id="footer">npm-deprecate &mdash; npm@1.4.3</p>
+<p id="footer">npm-deprecate &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-docs.html
+++ b/deps/npm/html/doc/api/npm-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">npm-docs &mdash; npm@1.4.3</p>
+<p id="footer">npm-docs &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-edit.html
+++ b/deps/npm/html/doc/api/npm-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">npm-edit &mdash; npm@1.4.3</p>
+<p id="footer">npm-edit &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-explore.html
+++ b/deps/npm/html/doc/api/npm-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 &#39;args&#39; 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">npm-explore &mdash; npm@1.4.3</p>
+<p id="footer">npm-explore &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-help-search.html
+++ b/deps/npm/html/doc/api/npm-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">npm-help-search &mdash; npm@1.4.3</p>
+<p id="footer">npm-help-search &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-init.html
+++ b/deps/npm/html/doc/api/npm-init.html
@@ -35,7 +35,7 @@ then go ahead and use this programmatically.</p>

 <p><a href="../files/package.json.html">package.json(5)</a></p>
 </div>
-<p id="footer">npm-init &mdash; npm@1.4.3</p>
+<p id="footer">npm-init &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-install.html
+++ b/deps/npm/html/doc/api/npm-install.html
@@ -25,7 +25,7 @@ the name of a package to be installed.</p>
 <p>Finally, &#39;callback&#39; 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">npm-install &mdash; npm@1.4.3</p>
+<p id="footer">npm-install &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-link.html
+++ b/deps/npm/html/doc/api/npm-link.html
@@ -39,7 +39,7 @@ npm.commands.link(&#39;redis&#39;, 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">npm-link &mdash; npm@1.4.3</p>
+<p id="footer">npm-link &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-load.html
+++ b/deps/npm/html/doc/api/npm-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">npm-load &mdash; npm@1.4.3</p>
+<p id="footer">npm-load &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-ls.html
+++ b/deps/npm/html/doc/api/npm-ls.html
@@ -59,7 +59,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">npm-ls &mdash; npm@1.4.3</p>
+<p id="footer">npm-ls &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-outdated.html
+++ b/deps/npm/html/doc/api/npm-outdated.html
@@ -19,7 +19,7 @@ currently outdated.</p>

 <p>If the &#39;packages&#39; parameter is left out, npm will check all packages.</p>
 </div>
-<p id="footer">npm-outdated &mdash; npm@1.4.3</p>
+<p id="footer">npm-outdated &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-owner.html
+++ b/deps/npm/html/doc/api/npm-owner.html
@@ -34,7 +34,7 @@ that is not implemented at this time.</p>

 <ul><li><a href="../api/npm-publish.html">npm-publish(3)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li></ul>
 </div>
-<p id="footer">npm-owner &mdash; npm@1.4.3</p>
+<p id="footer">npm-owner &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-pack.html
+++ b/deps/npm/html/doc/api/npm-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">npm-pack &mdash; npm@1.4.3</p>
+<p id="footer">npm-pack &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-prefix.html
+++ b/deps/npm/html/doc/api/npm-prefix.html
@@ -21,7 +21,7 @@

 <p>This function is not useful programmatically</p>
 </div>
-<p id="footer">npm-prefix &mdash; npm@1.4.3</p>
+<p id="footer">npm-prefix &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-prune.html
+++ b/deps/npm/html/doc/api/npm-prune.html
@@ -23,7 +23,7 @@
 <p>Extraneous packages are packages that are not listed on the parent
 package&#39;s dependencies list.</p>
 </div>
-<p id="footer">npm-prune &mdash; npm@1.4.3</p>
+<p id="footer">npm-prune &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-publish.html
+++ b/deps/npm/html/doc/api/npm-publish.html
@@ -32,7 +32,7 @@ the registry.  Overwrites when the &quot;force&quot; environment variable is set

 <ul><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li><li><a href="../api/npm-owner.html">npm-owner(3)</a></li></ul>
 </div>
-<p id="footer">npm-publish &mdash; npm@1.4.3</p>
+<p id="footer">npm-publish &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-rebuild.html
+++ b/deps/npm/html/doc/api/npm-rebuild.html
@@ -22,7 +22,7 @@ the new binary. If no &#39;packages&#39; parameter is specify, every package wil

 <p>See <code>npm help build</code></p>
 </div>
-<p id="footer">npm-rebuild &mdash; npm@1.4.3</p>
+<p id="footer">npm-rebuild &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-repo.html
+++ b/deps/npm/html/doc/api/npm-repo.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">npm-repo &mdash; npm@1.4.3</p>
+<p id="footer">npm-repo &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-restart.html
+++ b/deps/npm/html/doc/api/npm-restart.html
@@ -27,7 +27,7 @@ in the <code>packages</code> parameter.</p>

 <ul><li><a href="../api/npm-start.html">npm-start(3)</a></li><li><a href="../api/npm-stop.html">npm-stop(3)</a></li></ul>
 </div>
-<p id="footer">npm-restart &mdash; npm@1.4.3</p>
+<p id="footer">npm-restart &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-root.html
+++ b/deps/npm/html/doc/api/npm-root.html
@@ -21,7 +21,7 @@

 <p>This function is not useful programmatically.</p>
 </div>
-<p id="footer">npm-root &mdash; npm@1.4.3</p>
+<p id="footer">npm-root &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-run-script.html
+++ b/deps/npm/html/doc/api/npm-run-script.html
@@ -29,7 +29,7 @@ assumed to be the command to run. All other elements are ignored.</p>

 <ul><li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li><li><a href="../api/npm-test.html">npm-test(3)</a></li><li><a href="../api/npm-start.html">npm-start(3)</a></li><li><a href="../api/npm-restart.html">npm-restart(3)</a></li><li><a href="../api/npm-stop.html">npm-stop(3)</a></li></ul>
 </div>
-<p id="footer">npm-run-script &mdash; npm@1.4.3</p>
+<p id="footer">npm-run-script &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-search.html
+++ b/deps/npm/html/doc/api/npm-search.html
@@ -32,7 +32,7 @@ excluded term (the &quot;searchexclude&quot; config). The search is case insensi
 and doesn&#39;t try to read your mind (it doesn&#39;t do any verb tense matching or the
 like).</p>
 </div>
-<p id="footer">npm-search &mdash; npm@1.4.3</p>
+<p id="footer">npm-search &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-shrinkwrap.html
+++ b/deps/npm/html/doc/api/npm-shrinkwrap.html
@@ -26,7 +26,7 @@ but the shrinkwrap file will still be written.</p>
 <p>Finally, &#39;callback&#39; is a function that will be called when the shrinkwrap has
 been saved.</p>
 </div>
-<p id="footer">npm-shrinkwrap &mdash; npm@1.4.3</p>
+<p id="footer">npm-shrinkwrap &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-start.html
+++ b/deps/npm/html/doc/api/npm-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">npm-start &mdash; npm@1.4.3</p>
+<p id="footer">npm-start &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-stop.html
+++ b/deps/npm/html/doc/api/npm-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">npm-stop &mdash; npm@1.4.3</p>
+<p id="footer">npm-stop &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-submodule.html
+++ b/deps/npm/html/doc/api/npm-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">npm-submodule &mdash; npm@1.4.3</p>
+<p id="footer">npm-submodule &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-tag.html
+++ b/deps/npm/html/doc/api/npm-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">npm-tag &mdash; npm@1.4.3</p>
+<p id="footer">npm-tag &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-test.html
+++ b/deps/npm/html/doc/api/npm-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">npm-test &mdash; npm@1.4.3</p>
+<p id="footer">npm-test &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-uninstall.html
+++ b/deps/npm/html/doc/api/npm-uninstall.html
@@ -22,7 +22,7 @@ the name of a package to be uninstalled.</p>
 <p>Finally, &#39;callback&#39; 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">npm-uninstall &mdash; npm@1.4.3</p>
+<p id="footer">npm-uninstall &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-unpublish.html
+++ b/deps/npm/html/doc/api/npm-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">npm-unpublish &mdash; npm@1.4.3</p>
+<p id="footer">npm-unpublish &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-update.html
+++ b/deps/npm/html/doc/api/npm-update.html
@@ -18,7 +18,7 @@

 <p>The &#39;packages&#39; argument is an array of packages to update. The &#39;callback&#39; parameter will be called when done or when an error occurs.</p>
 </div>
-<p id="footer">npm-update &mdash; npm@1.4.3</p>
+<p id="footer">npm-update &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-version.html
+++ b/deps/npm/html/doc/api/npm-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">npm-version &mdash; npm@1.4.3</p>
+<p id="footer">npm-version &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-view.html
+++ b/deps/npm/html/doc/api/npm-view.html
@@ -99,7 +99,7 @@ the field name.</p>

 <p>corresponding to the list of fields selected.</p>
 </div>
-<p id="footer">npm-view &mdash; npm@1.4.3</p>
+<p id="footer">npm-view &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm-whoami.html
+++ b/deps/npm/html/doc/api/npm-whoami.html
@@ -21,7 +21,7 @@

 <p>This function is not useful programmatically</p>
 </div>
-<p id="footer">npm-whoami &mdash; npm@1.4.3</p>
+<p id="footer">npm-whoami &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/npm.html
+++ b/deps/npm/html/doc/api/npm.html
@@ -24,7 +24,7 @@ npm.load([configObject], function (er, npm) {

 <h2 id="VERSION">VERSION</h2>

-<p>1.4.3</p>
+<p>1.3.23</p>

 <h2 id="DESCRIPTION">DESCRIPTION</h2>

@@ -92,7 +92,7 @@ method names.  Use the <code>npm.deref</code> method to find the real name.</p>

 <pre><code>var cmd = npm.deref(&quot;unp&quot;) // cmd === &quot;unpublish&quot;</code></pre>
 </div>
-<p id="footer">npm &mdash; npm@1.4.3</p>
+<p id="footer">npm &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/api/repo.html
+++ b/deps/npm/html/doc/api/repo.html
@@ -0,0 +1,59 @@
+<!doctype html>
+<html>
+  <title>repo</title>
+  <meta http-equiv="content-type" value="text/html;utf-8">
+  <link rel="stylesheet" type="text/css" href="../../static/style.css">
+
+  <body>
+    <div id="wrapper">
+<h1><a href="../api/npm-repo.html">npm-repo</a></h1> <p>Open package repository page in the browser</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<pre><code>npm.commands.repo(package, callback)</code></pre>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>This command tries to guess at the likely location of a package&#39;s
+repository URL, and then tries to open it using the <code>--browser</code>
+config param.</p>
+
+<p>Like other commands, the first parameter is an array. This command only
+uses the first element, which is expected to be a package name with an
+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">repo &mdash; npm@1.3.22</p>
+<script>
+;(function () {
+var wrapper = document.getElementById("wrapper")
+var els = Array.prototype.slice.call(wrapper.getElementsByTagName("*"), 0)
+  .filter(function (el) {
+    return el.parentNode === wrapper
+        && el.tagName.match(/H[1-6]/)
+        && el.id
+  })
+var l = 2
+  , toc = document.createElement("ul")
+toc.innerHTML = els.map(function (el) {
+  var i = el.tagName.charAt(1)
+    , out = ""
+  while (i > l) {
+    out += "<ul>"
+    l ++
+  }
+  while (i < l) {
+    out += "</ul>"
+    l --
+  }
+  out += "<li><a href='#" + el.id + "'>" +
+    ( el.innerText || el.text || el.innerHTML)
+    + "</a>"
+  return out
+}).join("\n")
+toc.id = "toc"
+document.body.appendChild(toc)
+})()
+</script>
--- a/deps/npm/html/doc/cli/npm-adduser.html
+++ b/deps/npm/html/doc/cli/npm-adduser.html
@@ -39,7 +39,7 @@ authorize on a new machine.</p>

 <ul><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../cli/npm-owner.html">npm-owner(1)</a></li><li><a href="../cli/npm-whoami.html">npm-whoami(1)</a></li></ul>
 </div>
-<p id="footer">npm-adduser &mdash; npm@1.4.3</p>
+<p id="footer">npm-adduser &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-bin.html
+++ b/deps/npm/html/doc/cli/npm-bin.html
@@ -20,7 +20,7 @@

 <ul><li><a href="../cli/npm-prefix.html">npm-prefix(1)</a></li><li><a href="../cli/npm-root.html">npm-root(1)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li></ul>
 </div>
-<p id="footer">npm-bin &mdash; npm@1.4.3</p>
+<p id="footer">npm-bin &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-bugs.html
+++ b/deps/npm/html/doc/cli/npm-bugs.html
@@ -38,7 +38,7 @@ a <code>package.json</code> in the current folder and use the <code>name</code>

 <ul><li><a href="../cli/npm-docs.html">npm-docs(1)</a></li><li><a href="../cli/npm-view.html">npm-view(1)</a></li><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li></ul>
 </div>
-<p id="footer">npm-bugs &mdash; npm@1.4.3</p>
+<p id="footer">npm-bugs &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-build.html
+++ b/deps/npm/html/doc/cli/npm-build.html
@@ -25,7 +25,7 @@ A folder containing a <code>package.json</code> file in its root.</li></ul>

 <ul><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../cli/npm-link.html">npm-link(1)</a></li><li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li></ul>
 </div>
-<p id="footer">npm-build &mdash; npm@1.4.3</p>
+<p id="footer">npm-build &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-bundle.html
+++ b/deps/npm/html/doc/cli/npm-bundle.html
@@ -20,7 +20,7 @@ install packages into the local space.</p>

 <ul><li><a href="../cli/npm-install.html">npm-install(1)</a></li></ul>
 </div>
-<p id="footer">npm-bundle &mdash; npm@1.4.3</p>
+<p id="footer">npm-bundle &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-cache.html
+++ b/deps/npm/html/doc/cli/npm-cache.html
@@ -66,7 +66,7 @@ they do not make an HTTP request to the registry.</p>

 <ul><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li><li><a href="../cli/npm-pack.html">npm-pack(1)</a></li></ul>
 </div>
-<p id="footer">npm-cache &mdash; npm@1.4.3</p>
+<p id="footer">npm-cache &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-completion.html
+++ b/deps/npm/html/doc/cli/npm-completion.html
@@ -33,7 +33,7 @@ completions based on the arguments.</p>

 <ul><li><a href="../misc/npm-developers.html">npm-developers(7)</a></li><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../cli/npm.html">npm(1)</a></li></ul>
 </div>
-<p id="footer">npm-completion &mdash; npm@1.4.3</p>
+<p id="footer">npm-completion &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-config.html
+++ b/deps/npm/html/doc/cli/npm-config.html
@@ -73,7 +73,7 @@ global config.</p>

 <ul><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../cli/npm.html">npm(1)</a></li></ul>
 </div>
-<p id="footer">npm-config &mdash; npm@1.4.3</p>
+<p id="footer">npm-config &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-dedupe.html
+++ b/deps/npm/html/doc/cli/npm-dedupe.html
@@ -62,7 +62,7 @@ versions.</p>

 <ul><li><a href="../cli/npm-ls.html">npm-ls(1)</a></li><li><a href="../cli/npm-update.html">npm-update(1)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li></ul>
 </div>
-<p id="footer">npm-dedupe &mdash; npm@1.4.3</p>
+<p id="footer">npm-dedupe &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-deprecate.html
+++ b/deps/npm/html/doc/cli/npm-deprecate.html
@@ -31,7 +31,7 @@ something like this:</p>

 <ul><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li></ul>
 </div>
-<p id="footer">npm-deprecate &mdash; npm@1.4.3</p>
+<p id="footer">npm-deprecate &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-docs.html
+++ b/deps/npm/html/doc/cli/npm-docs.html
@@ -10,18 +10,17 @@

 <h2 id="SYNOPSIS">SYNOPSIS</h2>

-<pre><code>npm docs [&lt;pkgname&gt; [&lt;pkgname&gt; ...]]
+<pre><code>npm docs &lt;pkgname&gt;
 npm docs (with no args in a package dir)
-npm home [&lt;pkgname&gt; [&lt;pkgname&gt; ...]]
+npm home &lt;pkgname&gt;
 npm home (with no args in a package dir)</code></pre>

 <h2 id="DESCRIPTION">DESCRIPTION</h2>

 <p>This command tries to guess at the likely location of a package&#39;s
 documentation URL, and then tries to open it using the <code>--browser</code>
-config param. You can pass multiple package names at once. If no
-package name is provided, it will search for a <code>package.json</code> in
-the current folder and use the <code>name</code> property.</p>
+config param. If no package name is provided, it will search for
+a <code>package.json</code> in the current folder and use the <code>name</code> property.</p>

 <h2 id="CONFIGURATION">CONFIGURATION</h2>

@@ -41,7 +40,7 @@ the current folder and use the <code>name</code> property.</p>

 <ul><li><a href="../cli/npm-view.html">npm-view(1)</a></li><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li></ul>
 </div>
-<p id="footer">npm-docs &mdash; npm@1.4.3</p>
+<p id="footer">npm-docs &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-edit.html
+++ b/deps/npm/html/doc/cli/npm-edit.html
@@ -37,7 +37,7 @@ or <code>&quot;notepad&quot;</code> on Windows.</li><li>Type: path</li></ul>

 <ul><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-explore.html">npm-explore(1)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li></ul>
 </div>
-<p id="footer">npm-edit &mdash; npm@1.4.3</p>
+<p id="footer">npm-edit &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-explore.html
+++ b/deps/npm/html/doc/cli/npm-explore.html
@@ -40,7 +40,7 @@ Windows</li><li>Type: path</li></ul>

 <ul><li><a href="../cli/npm-submodule.html">npm-submodule(1)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-edit.html">npm-edit(1)</a></li><li><a href="../cli/npm-rebuild.html">npm-rebuild(1)</a></li><li><a href="../cli/npm-build.html">npm-build(1)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li></ul>
 </div>
-<p id="footer">npm-explore &mdash; npm@1.4.3</p>
+<p id="footer">npm-explore &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-help-search.html
+++ b/deps/npm/html/doc/cli/npm-help-search.html
@@ -38,7 +38,7 @@ where the terms were found in the documentation.</p>

 <ul><li><a href="../cli/npm.html">npm(1)</a></li><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../cli/npm-help.html">npm-help(1)</a></li></ul>
 </div>
-<p id="footer">npm-help-search &mdash; npm@1.4.3</p>
+<p id="footer">npm-help-search &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-help.html
+++ b/deps/npm/html/doc/cli/npm-help.html
@@ -36,7 +36,7 @@ matches are equivalent to specifying a topic name.</p>

 <ul><li><a href="../cli/npm.html">npm(1)</a></li><li><a href="../../doc/README.html">README</a></li><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../cli/npm-help-search.html">npm-help-search(1)</a></li><li><a href="../misc/npm-index.html">npm-index(7)</a></li></ul>
 </div>
-<p id="footer">npm-help &mdash; npm@1.4.3</p>
+<p id="footer">npm-help &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-init.html
+++ b/deps/npm/html/doc/cli/npm-init.html
@@ -29,7 +29,7 @@ without a really good reason to do so.</p>

 <ul><li><a href="https://github.com/isaacs/init-package-json">https://github.com/isaacs/init-package-json</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../cli/npm-version.html">npm-version(1)</a></li></ul>
 </div>
-<p id="footer">npm-init &mdash; npm@1.4.3</p>
+<p id="footer">npm-init &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-install.html
+++ b/deps/npm/html/doc/cli/npm-install.html
@@ -57,9 +57,9 @@ will follow the same rules for resolving dependencies described in <code><a href
 treat it as a single argument.</p><p>Example:</p><p>      npm install sax@&quot;&gt;=0.1.0 &lt;0.2.0&quot;</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
 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
 <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:npm/npm.git#v1.0.27
-  git+https://isaacs@github.com/npm/npm.git
-  git://github.com/npm/npm.git#v1.0.27</code></pre></li></ul>
+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://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>
@@ -149,7 +149,7 @@ affects a real use-case, it will be investigated.</p>

 <ul><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-update.html">npm-update(1)</a></li><li><a href="../cli/npm-link.html">npm-link(1)</a></li><li><a href="../cli/npm-rebuild.html">npm-rebuild(1)</a></li><li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li><li><a href="../cli/npm-build.html">npm-build(1)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-tag.html">npm-tag(1)</a></li><li><a href="../cli/npm-rm.html">npm-rm(1)</a></li><li><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></li></ul>
 </div>
-<p id="footer">npm-install &mdash; npm@1.4.3</p>
+<p id="footer">npm-install &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-link.html
+++ b/deps/npm/html/doc/cli/npm-link.html
@@ -62,7 +62,7 @@ installation target into your project&#39;s <code>node_modules</code> folder.</p

 <ul><li><a href="../misc/npm-developers.html">npm-developers(7)</a></li><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li></ul>
 </div>
-<p id="footer">npm-link &mdash; npm@1.4.3</p>
+<p id="footer">npm-link &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-ls.html
+++ b/deps/npm/html/doc/cli/npm-ls.html
@@ -25,7 +25,7 @@ limit the results to only the paths to the packages named.  Note that
 nested packages will <em>also</em> show the paths to the specified packages.
 For example, running <code>npm ls promzard</code> in npm&#39;s source tree will show:</p>

-<pre><code>npm@1.4.3 /path/to/npm
+<pre><code>npm@1.3.23 /path/to/npm
 └─┬ init-package-json@0.0.4
  └── promzard@0.1.5</code></pre>

@@ -64,17 +64,11 @@ recognize potential forks of a project.</p>
 <p>List packages in the global install prefix instead of in the current
 project.</p>

-<h3 id="depth">depth</h3>
-
-<ul><li>Type: Int</li></ul>
-
-<p>Max display depth of the dependency tree.</p>
-
 <h2 id="SEE-ALSO">SEE ALSO</h2>

 <ul><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../cli/npm-link.html">npm-link(1)</a></li><li><a href="../cli/npm-prune.html">npm-prune(1)</a></li><li><a href="../cli/npm-outdated.html">npm-outdated(1)</a></li><li><a href="../cli/npm-update.html">npm-update(1)</a></li></ul>
 </div>
-<p id="footer">npm-ls &mdash; npm@1.4.3</p>
+<p id="footer">npm-ls &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-outdated.html
+++ b/deps/npm/html/doc/cli/npm-outdated.html
@@ -21,44 +21,11 @@ packages are currently outdated.</p>
 version specified in the package.json, the field &#39;latest&#39; the very latest
 version of the package.</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>
-
-<p>Show extended information.</p>
-
-<h3 id="parseable">parseable</h3>
-
-<ul><li>Default: false</li><li>Type: Boolean</li></ul>
-
-<p>Show parseable output instead of tree view.</p>
-
-<h3 id="global">global</h3>
-
-<ul><li>Default: false</li><li>Type: Boolean</li></ul>
-
-<p>Check packages in the global install prefix instead of in the current
-project.</p>
-
-<h3 id="depth">depth</h3>
-
-<ul><li>Type: Int</li></ul>
-
-<p>Max depth for checking dependency tree.</p>
-
 <h2 id="SEE-ALSO">SEE ALSO</h2>

 <ul><li><a href="../cli/npm-update.html">npm-update(1)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li></ul>
 </div>
-<p id="footer">npm-outdated &mdash; npm@1.4.3</p>
+<p id="footer">npm-outdated &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-owner.html
+++ b/deps/npm/html/doc/cli/npm-owner.html
@@ -34,7 +34,7 @@ that is not implemented at this time.</p>

 <ul><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li><li><a href="../misc/npm-disputes.html">npm-disputes(7)</a></li></ul>
 </div>
-<p id="footer">npm-owner &mdash; npm@1.4.3</p>
+<p id="footer">npm-owner &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-pack.html
+++ b/deps/npm/html/doc/cli/npm-pack.html
@@ -29,7 +29,7 @@ overwritten the second time.</p>

 <ul><li><a href="../cli/npm-cache.html">npm-cache(1)</a></li><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li></ul>
 </div>
-<p id="footer">npm-pack &mdash; npm@1.4.3</p>
+<p id="footer">npm-pack &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-prefix.html
+++ b/deps/npm/html/doc/cli/npm-prefix.html
@@ -20,7 +20,7 @@

 <ul><li><a href="../cli/npm-root.html">npm-root(1)</a></li><li><a href="../cli/npm-bin.html">npm-bin(1)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li></ul>
 </div>
-<p id="footer">npm-prefix &mdash; npm@1.4.3</p>
+<p id="footer">npm-prefix &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-prune.html
+++ b/deps/npm/html/doc/cli/npm-prune.html
@@ -29,7 +29,7 @@ packages specified in your <code>devDependencies</code>.</p>

 <ul><li><a href="../cli/npm-rm.html">npm-rm(1)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-ls.html">npm-ls(1)</a></li></ul>
 </div>
-<p id="footer">npm-prune &mdash; npm@1.4.3</p>
+<p id="footer">npm-prune &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-publish.html
+++ b/deps/npm/html/doc/cli/npm-publish.html
@@ -29,7 +29,7 @@ the registry.  Overwrites when the &quot;--force&quot; flag is set.</p>

 <ul><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li><li><a href="../cli/npm-owner.html">npm-owner(1)</a></li><li><a href="../cli/npm-deprecate.html">npm-deprecate(1)</a></li><li><a href="../cli/npm-tag.html">npm-tag(1)</a></li></ul>
 </div>
-<p id="footer">npm-publish &mdash; npm@1.4.3</p>
+<p id="footer">npm-publish &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-rebuild.html
+++ b/deps/npm/html/doc/cli/npm-rebuild.html
@@ -26,7 +26,7 @@ the new binary.</p>

 <ul><li><a href="../cli/npm-build.html">npm-build(1)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li></ul>
 </div>
-<p id="footer">npm-rebuild &mdash; npm@1.4.3</p>
+<p id="footer">npm-rebuild &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-repo.html
+++ b/deps/npm/html/doc/cli/npm-repo.html
@@ -32,7 +32,7 @@ a <code>package.json</code> in the current folder and use the <code>name</code>

 <ul><li><a href="../cli/npm-docs.html">npm-docs(1)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li></ul>
 </div>
-<p id="footer">npm-repo &mdash; npm@1.4.3</p>
+<p id="footer">npm-repo &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-restart.html
+++ b/deps/npm/html/doc/cli/npm-restart.html
@@ -24,7 +24,7 @@ the &quot;start&quot; script.</p>

 <ul><li><a href="../cli/npm-run-script.html">npm-run-script(1)</a></li><li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li><li><a href="../cli/npm-test.html">npm-test(1)</a></li><li><a href="../cli/npm-start.html">npm-start(1)</a></li><li><a href="../cli/npm-stop.html">npm-stop(1)</a></li></ul>
 </div>
-<p id="footer">npm-restart &mdash; npm@1.4.3</p>
+<p id="footer">npm-restart &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/cli/npm-rm.html
+++ b/deps/npm/html/doc/cli/npm-rm.html
@@ -24,7 +24,7 @@ on its behalf.</p>

 <ul><li><a href="../cli/npm-prune.html">npm-prune(1)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li></ul>
 </div>
-<p id="footer">npm-rm &mdash; npm@1.4.3</p>
+<p id="footer">npm-rm &mdash; npm@1.3.23</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Alexis Campailla	06990da3f6	test: debug-signal-cluster increase timeouts The test needs a little more time to run so that it passes for all builds (eg: Windows, debug)	2014-01-13 17:51:17 -08:00
Alexis Campailla	4946c833f3	debug client: connect after child is ready We now wait to connect to the debuggee until we know that its error stream has data, to ensure that the output message "connecting..... ok" appears after "Debugger listening on port xyz" I also increased the test timeout to let the more complex tests finish in time on Windows This change fixes the following unit tests on Windows: test-debugger-repl.js test-debugger-repl-term.js test-debugger-repl-utf8.js test-debugger-repl-restart.js	2014-01-13 17:42:27 -08:00
Timothy J Fontaine	dcd5224e1f	test: move debugger repl into own section	2014-01-13 17:35:41 -08:00
Timothy J Fontaine	be3aaeb0e9	test: refactor to use common testcfg	2014-01-13 17:09:12 -08:00