2012.01.09, Version 0.8.17 (Stable)

* npm: Upgrade to v1.2.0 - peerDependencies (Domenic Denicola) - node-gyp v0.8.2 (Nathan Rajlich) - Faster installs from github user/project shorthands (Nathan Zadoks) * typed arrays: fix 32 bit size/index overflow (Ben Noordhuis) * http: Improve performance of single-packet responses (Ben Noordhuis) * install: fix openbsd man page location (Ben Noordhuis) * http: bubble up parser errors to ClientRequest (Brian White)
typed arrays: fix 32 bit size/index overflow
2026-04-28 03:01:10 -04:00 · 2013-01-09 16:55:12 -08:00 · 2013-01-10 00:55:27 +01:00 · 2013-01-09 15:21:30 -08:00 · 2013-01-09 12:16:04 +04:00 · 2013-01-08 04:32:40 +01:00
1481 changed files with 49290 additions and 2867 deletions
--- a/11
+++ b/11
@@ -364,3 +364,14 @@ Pooya Karimian <pkarimian@sencha.com>
 Frédéric Germain <frederic.germain@gmail.com>
 Robin Lee <cheeselee@fedoraproject.org>
 Adam Blackburn <regality@gmail.com>
+Willi Eggeling <email@wje-online.de>
+Andrew Paprocki <andrew@ishiboo.com>
+Max Ogden <max@maxogden.com>
+Olivier Lalonde <olalonde@gmail.com>
+Francois Marier <francois@mozilla.com>
+Trevor Norris <trev.norris@gmail.com>
+Joshua Erickson <josh@snoj.us>
+Kai Sasaki Lewuathe <sasaki_kai@lewuathe.sakura.ne.jp>
+Nicolas Chambrier <naholyr@gmail.com>
+Tim Bradshaw <tfb@cley.com>
+Johannes Ewald <mail@johannesewald.de>
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -0,0 +1,145 @@
+# CONTRIBUTING
+
+The node.js project welcomes new contributors.  This document will guide you
+through the process.
+
+
+### FORK
+
+Fork the project [on GitHub](https://github.com/joyent/node) and check out
+your copy.
+
+```
+$ git clone git@github.com:username/node.git
+$ cd node
+$ git remote add upstream git://github.com/joyent/node.git
+```
+
+Now decide if you want your feature or bug fix to go into the master branch
+or the stable branch.  As a rule of thumb, bug fixes go into the stable branch
+while new features go into the master branch.
+
+The stable branch is effectively frozen; patches that change the node.js
+API/ABI or affect the run-time behavior of applications get rejected.
+
+The rules for the master branch are less strict; consult the
+[stability index page][] for details.
+
+In a nutshell, modules are at varying levels of API stability.  Bug fixes are
+always welcome but API or behavioral  changes to modules at stability level 3
+and up are off-limits.
+
+Node.js has several bundled dependencies in the deps/ directory that are not
+part of the project proper.  Any changes to files in that directory or its
+subdirectories should be sent to their respective projects.  Do not send
+that patch to us, we cannot accept it.
+
+In case of doubt, open an issue in the [issue tracker][], post your question
+to the [node.js mailing list][] or contact one of the [project maintainers][]
+on [IRC][].
+
+Especially do so if you plan to work on something big.  Nothing is more
+frustrating than seeing your hard work go to waste because your vision
+does not align with that of a project maintainer.
+
+
+### BRANCH
+
+Okay, so you have decided on the proper branch.  Create a feature branch
+and start hacking:
+
+```
+$ git checkout -b my-feature-branch -t origin/v0.8
+```
+
+(Where v0.8 is the latest stable branch as of this writing.)
+
+
+### COMMIT
+
+Make sure git knows your name and email address:
+
+```
+$ git config --global user.name "J. Random User"
+$ git config --global user.email "j.random.user@example.com"
+```
+
+Writing good commit logs is important.  A commit log should describe what
+changed and why.  Follow these guidelines when writing one:
+
+1. The first line should be 50 characters or less and contain a short
+   description of the change.
+2. Keep the second line blank.
+3. Wrap all other lines at 72 columns.
+
+A good commit log looks like this:
+
+```
+Header line: explaining the commit in one line
+
+Body of commit message is a few lines of text, explaining things
+in more detail, possibly giving some background about the issue
+being fixed, etc etc.
+
+The body of the commit message can be several paragraphs, and
+please do proper word-wrap and keep columns shorter than about
+72 characters or so. That way `git log` will show things
+nicely even when it is indented.
+```
+
+The header line should be meaningful; it is what other people see when they
+run `git shortlog` or `git log --oneline`.
+
+Have a look at `git log` for inspiration.
+
+
+### REBASE
+
+Use `git rebase` (not `git merge`) to sync your work from time to time.
+
+```
+$ git fetch upstream
+$ git rebase upstream/v0.8  # or upstream/master
+```
+
+
+### TEST
+
+Bug fixes and features should come with tests.  Add your tests in the
+test/simple/ directory.  Look at other tests to see how they should be
+structured (license boilerplate, common includes, etc.).
+
+```
+$ make jslint test
+```
+
+Make sure the linter is happy and that all tests pass.  Please, do not submit
+patches that fail either check.
+
+
+### PUSH
+
+```
+$ git push origin my-feature-branch
+```
+
+Go to https://github.com/username/node and select your feature branch.  Click
+the 'Pull Request' button and fill out the form.
+
+Pull requests are usually reviewed within a few days.  If there are comments
+to address, apply your changes in a separate commit and push that to your
+feature branch.  Post a comment in the pull request afterwards; GitHub does
+not send out notifications when you add commits.
+
+
+### CONTRIBUTOR LICENSE AGREEMENT
+
+Please visit http://nodejs.org/cla.html and sign the Contributor License
+Agreement.  You only need to do that once.
+
+
+[stability index page]: https://github.com/joyent/node/blob/master/doc/api/documentation.markdown
+[issue tracker]: https://github.com/joyent/node/issues
+[node.js mailing list]: http://groups.google.com/group/nodejs
+[IRC]: http://webchat.freenode.net/?channels=node.js
+[project maintainers]: https://github.com/joyent/node/wiki/Project-Organization
--- a/129
+++ b/129
@@ -1,9 +1,104 @@
-2012.09.27, Version 0.8.11 (Stable)
+2012.01.09, Version 0.8.17 (Stable)
+
+* npm: Upgrade to v1.2.0
+  - peerDependencies (Domenic Denicola)
+  - node-gyp v0.8.2 (Nathan Rajlich)
+  - Faster installs from github user/project shorthands (Nathan Zadoks)
+
+* typed arrays: fix 32 bit size/index overflow (Ben Noordhuis)
+
+* http: Improve performance of single-packet responses (Ben Noordhuis)
+
+* install: fix openbsd man page location (Ben Noordhuis)
+
+* http: bubble up parser errors to ClientRequest (Brian White)
+
+
+2012.12.13, Version 0.8.16 (Stable), 1c9c6277d5cfcaaac8569c0c8f7daa64292048a9
+
+* npm: Upgrade to 1.1.69
+
+* fs: fix WriteStream/ReadStream fd leaks (Ben Noordhuis)
+
+* crypto: fix leak in GetPeerCertificate (Fedor Indutny)
+
+* buffer: Don't double-negate numeric buffer arg (Trevor Norris)
+
+* net: More accurate IP address validation and IPv6 dotted notation. (Joshua Erickson)
+
+
+2012.11.26, Version 0.8.15 (Stable), fdf91afb494a7a2fff2913d817f589c191a2c88f
+
+* npm: Upgrade to 1.1.66 (isaacs)
+
+* linux: use /proc/cpuinfo for CPU frequency (Ben Noordhuis)
+
+* windows: map WSAESHUTDOWN to UV_EPIPE (Ben Noordhuis)
+
+* windows: map ERROR_GEN_FAILURE to UV_EIO (Bert Belder)
+
+* unix: do not set environ unless one is provided (Charlie McConnell)
+
+* domains: don't crash if domain is set to null (Bert Belder)
+
+* windows: fix the x64 debug build (Bert Belder)
+
+* net, tls: fix connect() resource leak (Ben Noordhuis)
+
+
+2012.10.25, Version 0.8.14 (Stable), b00527fcf05c3d9f/b5d5d790f9472906a59fe218
+
+* events: Don't clobber pre-existing _events obj in EE ctor (isaacs)
+
+
+2012.10.25, Version 0.8.13 (Stable), ff4c974873f9a7cc6a5b042eb9b6389bb8dde6d6
+
+* V8: Upgrade to 3.11.10.25
+
+* npm: Upgrade to 1.1.65
+
+* url: parse hostnames that start with - or _ (Ben Noordhuis)
+
+* repl: Fix Windows 8 terminal issue (Bert Belder)
+
+* typed arrays: use signed char for signed int8s (Aaron Jacobs)
+
+* crypto: fix bugs in DiffieHellman (Ben Noordhuis)
+
+* configure: turn on VFPv3 on ARMv7 (Ben Noordhuis)
+
+* Re-enable OpenSSL UI for entering passphrases via tty (Ben Noordhuis)
+
+* repl: ensure each REPL instance gets its own "context" (Nathan Rajlich)
+
+
+2012.10.12, Version 0.8.12 (Stable), 38c72d4e29574dec5205bcf23c2a85efe65331a4
+
+* npm: Upgrade to 1.1.63
+
+* crypto: Reduce stability index to 2-Unstable (isaacs)
+
+* windows: fix handle leak in uv_fs_utime (Bert Belder)
+
+* windows: fix application crashed popup in debug version (Bert Belder)
+
+* buffer: report proper retained size in profiler (Ben Noordhuis)
+
+* buffer: fix byteLength with UTF-16LE (koichik)
+
+* repl: make "end of input" JSON.parse() errors throw in the REPL (Nathan Rajlich)
+
+* repl: make invalid RegExp modifiers throw in the REPL (Nathan Rajlich)
+
+* http: handle multiple Proxy-Authenticate values (Willi Eggeling)
+
+
+2012.09.27, Version 0.8.11 (Stable), e1f39468fa580c1e4cb15fac621f87944ee625dc

 * fs: Fix stat() size reporting for large files (Ben Noordhuis)


-2012.09.25, Version 0.8.10 (Stable)
+2012.09.25, Version 0.8.10 (Stable), 0bc273da4fcaa79b209ed755ad249a3e7be626a6

 * npm: Upgrade to 1.1.62

@@ -765,7 +860,7 @@
 * Bug fixes


-2012.07.10 Version 0.6.20 (maintenance)
+2012.07.10 Version 0.6.20 (maintenance), 952e513379169ec1b40909d1db056e9bf4294899

 * npm: Upgrade to 1.1.37 (isaacs)

@@ -1128,7 +1223,7 @@
 * crypto: don't ignore DH init errors (Ben Noordhuis)


-2011.12.14, Version 0.6.6
+2011.12.14, Version 0.6.6 (stable), 9a059ea69e1f6ebd8899246682d8ca257610b8ab

 * npm update to 1.1.0-beta-4 (Isaac Z. Schlueter)

@@ -1365,7 +1460,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Upgrade GYP to r1081


-2011.10.10, Version 0.5.9 (unstable)
+2011.10.10, Version 0.5.9 (unstable), 3bd9b08fb125b606f97a4079b147accfdeebb07d

 * fs.watch interface backed by kqueue, inotify, and ReadDirectoryChangesW
  (Igor Zinkovsky, Ben Noordhuis)
@@ -1449,7 +1544,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * #1719 Drain OpenSSL error queue


-2011.09.08, Version 0.5.6 (unstable)
+2011.09.08, Version 0.5.6 (unstable), b49bec55806574a47403771bce1ee379c2b09ca2

 * #345, #1635, #1648 Documentation improvements (Thomas Shinnick,
  Abimanyu Raja, AJ ONeal, Koichi Kobayashi, Michael Jackson, Logan Smyth,
@@ -1737,7 +1832,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * DTrace probes: support X-Forwarded-For (Dave Pacheco)


-2011.09.15, Version 0.4.12 (stable)
+2011.09.15, Version 0.4.12 (stable), 771ba34ca7b839add2ef96879e1ffc684813cf7c

 * Improve docs

@@ -1786,7 +1881,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Doc improvments (koichik, Logan Smyth, Ben Noordhuis, Arnout Kazemier)


-2011.07.19, Version 0.4.10 (stable)
+2011.07.19, Version 0.4.10 (stable), 1b8dd65d6e3b82b6863ef38835cc436c5d30c1d5

 * #394 Fix Buffer drops last null character in UTF-8

@@ -1813,7 +1908,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Doc improvements


-2011.06.29, Version 0.4.9 (stable)
+2011.06.29, Version 0.4.9 (stable), de44eafd7854d06cd85006f509b7051e8540589b

 * Improve documentation

@@ -1887,7 +1982,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Upgrade V8 to 3.1.8.16.


-2011.04.22, Version 0.4.7 (stable)
+2011.04.22, Version 0.4.7 (stable), c85455a954411b38232e79752d4abb61bb75031b

 * Don't emit error on ECONNRESET from read() #670

@@ -1905,7 +2000,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Improve docs.


-2011.04.13, Version 0.4.6 (stable)
+2011.04.13, Version 0.4.6 (stable), 58002d56bc79410c5ff397fc0e1ffec0665db38a

 * Don't error on ENOTCONN from shutdown() #670

@@ -1935,7 +2030,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Upgrade v8 to 3.1.8.10


-2011.04.01, Version 0.4.5 (stable)
+2011.04.01, Version 0.4.5 (stable), 787a343b588de26784fef97f953420b53a6e1d73

 * Fix listener leak in stream.pipe() (Mikeal Rogers)

@@ -2068,7 +2163,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Upgrade V8 to 3.1.5, libev to 4.4.


-2011.02.10, Version 0.4.0 (stable)
+2011.02.10, Version 0.4.0 (stable), eb155ea6f6a6aa341aa8c731dca8da545c6a4008

 * require() improvements (isaacs)
  - understand package.json (isaacs)
@@ -2101,7 +2196,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Upgrade V8 to 3.1.2


-2011.02.04, Version 0.3.8 (unstable)
+2011.02.04, Version 0.3.8 (unstable), 9493b7563bff31525b4080df5aeef09747782d5e

 * Add req.abort() for client side requests.

@@ -2123,7 +2218,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)

 * Upgrade V8 to 3.1.1

-2011.01.27, Version 0.3.7 (unstable)
+2011.01.27, Version 0.3.7 (unstable), d8579c6afdbe868de6dffa8db78bbe4ba2d03e0e

 * Expose agent in http and https client. (Mikeal Rogers)

@@ -2185,7 +2280,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Don't stat() on cached modules. (Felix Geisendörfer)


-2011.01.08, Version 0.3.4 (unstable)
+2011.01.08, Version 0.3.4 (unstable), 73f53e12e4a5b9ef7dbb4792bd5f8ad403094441

 * Primordial mingw build (Bert Belder)

@@ -2403,7 +2498,7 @@ koichik, Maciej Małecki, Guglielmo Ferri, isaacs)
 * Upgrade V8 to 2.3.8


-2010.08.13, Version 0.1.104
+2010.08.13, Version 0.1.104, b14dd49222687c12f3e8eac597cff4f2674f84e8

 * Various bug fixes (console, querystring, require)

--- a/benchmark/http_simple.js
+++ b/benchmark/http_simple.js
@@ -96,13 +96,12 @@ var server = http.createServer(function (req, res) {
                            'Transfer-Encoding': 'chunked' });
    // send body in chunks
    var len = body.length;
-    var step = ~~(len / n_chunks) || len;
+    var step = Math.floor(len / n_chunks) || 1;

-    for (var i = 0; i < len; i += step) {
-      res.write(body.slice(i, i + step));
+    for (var i = 0, n = (n_chunks - 1); i < n; ++i) {
+      res.write(body.slice(i * step, i * step + step));
    }
-
-    res.end();
+    res.end(body.slice((n_chunks - 1) * step));
  } else {
    var content_length = body.length.toString();

--- a/benchmark/http_simple_auto.js
+++ b/benchmark/http_simple_auto.js
@@ -77,13 +77,12 @@ var server = http.createServer(function (req, res) {
                            "Transfer-Encoding": "chunked" });
    // send body in chunks
    var len = body.length;
-    var step = ~~(len / n_chunks) || len;
+    var step = Math.floor(len / n_chunks) || 1;

-    for (var i = 0; i < len; i += step) {
-      res.write(body.slice(i, i + step));
+    for (var i = 0, n = (n_chunks - 1); i < n; ++i) {
+      res.write(body.slice(i * step, i * step + step));
    }
-
-    res.end();
+    res.end(body.slice((n_chunks - 1) * step));
  } else {
    var content_length = body.length.toString();

--- a/44
+++ b/44
@@ -176,6 +176,17 @@ parser.add_option("--with-arm-float-abi",
    help="Specifies which floating-point ABI to use. Valid values are: "
         "soft, softfp, hard")

+# Using --unsafe-optimizations voids your warranty.
+parser.add_option("--unsafe-optimizations",
+    action="store_true",
+    dest="unsafe_optimizations",
+    help=optparse.SUPPRESS_HELP)
+
+parser.add_option("--tag",
+    action="store",
+    dest="tag",
+    help="Custom build tag")
+
 (options, args) = parser.parse_args()


@@ -322,12 +333,31 @@ def compiler_version():
  return (version, is_clang)


+def configure_arm(o):
+  # V8 on ARM requires that armv7 is set. CPU Model detected by
+  # the presence of __ARM_ARCH_7__ and the like defines in compiler
+  if options.arm_float_abi:
+    hard_float = options.arm_float_abi == 'hard'
+  else:
+    hard_float = arm_hard_float_abi()
+  o['variables']['v8_use_arm_eabi_hardfloat'] = b(hard_float)
+
+  armv7 = is_arch_armv7()
+  if armv7:
+    # CHECKME VFPv3 implies ARMv7+ but is the reverse true as well?
+    o['variables']['arm_fpu'] = 'vfpv3'
+    o['variables']['arm_neon'] = 0
+  o['variables']['armv7'] = int(armv7)
+
+
 def configure_node(o):
  # TODO add gdb
  o['variables']['v8_no_strict_aliasing'] = 1 # work around compiler bugs
  o['variables']['node_prefix'] = os.path.expanduser(options.prefix or '')
  o['variables']['node_install_npm'] = b(not options.without_npm)
  o['variables']['node_install_waf'] = b(not options.without_waf)
+  o['variables']['node_unsafe_optimizations'] = (
+    1 if options.unsafe_optimizations else 0)
  o['default_configuration'] = 'Debug' if options.debug else 'Release'

  host_arch = host_arch_win() if os.name == 'nt' else host_arch_cc()
@@ -335,15 +365,8 @@ def configure_node(o):
  o['variables']['host_arch'] = host_arch
  o['variables']['target_arch'] = target_arch

-  # V8 on ARM requires that armv7 is set. CPU Model detected by
-  # the presence of __ARM_ARCH_7__ and the like defines in compiler
  if target_arch == 'arm':
-    if options.arm_float_abi:
-      hard_float = options.arm_float_abi == 'hard'
-    else:
-      hard_float = arm_hard_float_abi()
-    o['variables']['v8_use_arm_eabi_hardfloat'] = b(hard_float)
-    o['variables']['armv7'] = 1 if is_arch_armv7() else 0
+    configure_arm(o)

  cc_version, is_clang = compiler_version()
  o['variables']['clang'] = 1 if is_clang else 0
@@ -376,6 +399,11 @@ def configure_node(o):
  else:
    o['variables']['node_use_etw'] = 'false'

+  if options.tag:
+    o['variables']['node_tag'] = '-' + options.tag
+  else:
+    o['variables']['node_tag'] = ''
+

 def configure_libz(o):
  o['variables']['node_shared_zlib'] = b(options.shared_zlib)
--- a/deps/npm/AUTHORS
+++ b/deps/npm/AUTHORS
@@ -77,3 +77,4 @@ Nicolas Morel <marsup@gmail.com>
 Mark Dube <markisdee@gmail.com>
 Maxim Bogushevich <boga1@mail.ru>
 Justin Beckwith <justbe@microsoft.com>
+Meaglin <Meaglin.wasabi@gmail.com>
--- a/deps/npm/Makefile
+++ b/deps/npm/Makefile
@@ -92,7 +92,7 @@ doc/cli/index.md: $(markdowns) scripts/index-build.js scripts/doc-build.sh packa
 	node scripts/index-build.js > $@

 node_modules/.bin/ronn:
-	node cli.js install
+	node cli.js install ronn

 doc: man

--- a/deps/npm/README.md
+++ b/deps/npm/README.md
@@ -60,7 +60,7 @@ for testing, or running stuff without actually installing npm itself.)

 ## Fancy Windows Install

-You can download a zip file from <http://npmjs.org/dist/>, and unpack it
+You can download a zip file from <https://npmjs.org/dist/>, and unpack it
 in the same folder where node.exe lives.

 If that's not fancy enough for you, then you can fetch the code with
@@ -169,13 +169,13 @@ help config` to learn about all the options you can set there.

 ## More Docs

-Check out the [docs](http://npmjs.org/doc/),
-especially the [faq](http://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](http://npmjs.org/doc/developers.html)
+you should [read this](https://npmjs.org/doc/developers.html)

 ## Legal Stuff

@@ -221,7 +221,7 @@ If this concerns you, inspect the source before using packages.
 When you find issues, please report them:

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

--- a/deps/npm/doc/api/deprecate.md
+++ b/deps/npm/doc/api/deprecate.md
@@ -25,6 +25,8 @@ The 'args' parameter must have exactly two elements:
 Note that you must be the package owner to deprecate something.  See the
 `owner` and `adduser` help topics.

+To un-deprecate a package, specify an empty string (`""`) for the `message` argument.
+
 ## SEE ALSO

 * npm-publish(3)
--- a/deps/npm/doc/cli/coding-style.md
+++ b/deps/npm/doc/cli/coding-style.md
@@ -10,6 +10,8 @@ designed to reduce visual clutter and make bugs more apparent.
 If you want to contribute to npm (which is very encouraged), you should
 make your code conform to npm's style.

+Note: this concerns npm's code not the specific packages at npmjs.org
+
 ## Line Length

 Keep lines shorter than 80 characters.  It's better for lines to be
--- a/deps/npm/doc/cli/config.md
+++ b/deps/npm/doc/cli/config.md
@@ -112,7 +112,6 @@ The following shorthands are parsed on the command-line:
 * `-reg`: `--registry`
 * `-v`: `--version`
 * `-f`: `--force`
-* `-l`: `--long`
 * `-desc`: `--description`
 * `-S`: `--save`
 * `-D`: `--save-dev`
--- a/deps/npm/doc/cli/deprecate.md
+++ b/deps/npm/doc/cli/deprecate.md
@@ -18,6 +18,8 @@ something like this:
 Note that you must be the package owner to deprecate something.  See the
 `owner` and `adduser` help topics.

+To un-deprecate a package, specify an empty string (`""`) for the `message` argument.
+
 ## SEE ALSO

 * npm-publish(1)
--- a/deps/npm/doc/cli/disputes.md
+++ b/deps/npm/doc/cli/disputes.md
@@ -4,8 +4,10 @@ npm-disputes(1) -- Handling Module Name Disputes
 ## SYNOPSIS

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

 ## DESCRIPTION

@@ -40,7 +42,7 @@ 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 respecfully as possible**,
+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
@@ -75,6 +77,11 @@ but not limited to:
   MIT-licensed program, and then removing or changing the copyright and
   license statement)
 3. Illegal content.
+4. "Squatting" on a package name that you *plan* to use, but aren't
+   actually using.  Sorry, I don't care how great the name is, or how
+   perfect a fit it is for the thing that someday might happen.  If
+   someone wants to use it today, and you're just taking up space with
+   an empty tarball, you're going to be evicted.

 If you see bad behavior like this, please report it right away.

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

 ## Where can I find these docs in HTML?

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

    npm config set viewer browser

@@ -144,7 +144,7 @@ command.)

 In those cases, you can do this:

-    curl http://npmjs.org/install.sh | sh
+    curl https://npmjs.org/install.sh | sh

 ## What is a `package`?

@@ -177,9 +177,9 @@ an argument to `git checkout`.  The default is `master`.

 You don't.  Try one of these:

-* <http://github.com/isaacs/nave>
-* <http://github.com/visionmedia/n>
-* <http://github.com/creationix/nvm>
+* <https://github.com/isaacs/nave>
+* <https://github.com/visionmedia/n>
+* <https://github.com/creationix/nvm>

 ## How can I use npm for development?

@@ -245,7 +245,7 @@ There is not sufficient need to impose namespace rules on everyone.
 Discuss it on the mailing list, or post an issue.

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

 ## Why does npm hate me?

--- a/deps/npm/doc/cli/json.md
+++ b/deps/npm/doc/cli/json.md
@@ -366,8 +366,8 @@ a version in the following fashion.
 For example, the following are equivalent:

 * `"~1.2.3" = ">=1.2.3 <1.3.0"`
-* `"~1.2" = ">=1.2.0 <2.0.0"`
-* `"~1" = ">=1.0.0 <2.0.0"`
+* `"~1.2" = ">=1.2.0 <1.3.0"`
+* `"~1" = ">=1.0.0 <1.1.0"`

 ### X Version Ranges

--- a/deps/npm/doc/cli/registry.md
+++ b/deps/npm/doc/cli/registry.md
@@ -82,9 +82,7 @@ ask for help on the <npm-@googlegroups.com> mailing list.

 ## Is there a website or something to see package docs and such?

-No, but such a thing is planned, and a tiny bit developed.
-
-Stay tuned!
+Yes, head over to <https://npmjs.org/>

 ## SEE ALSO

--- a/deps/npm/doc/cli/scripts.md
+++ b/deps/npm/doc/cli/scripts.md
@@ -6,6 +6,11 @@ npm-scripts(1) -- How npm handles the "scripts" field
 npm supports the "scripts" member of the package.json script, for the
 following scripts:

+* prepublish:
+  Run BEFORE the package is published.  (Also run on local `npm
+  install` without any arguments.)
+* publish, postpublish:
+  Run AFTER the package is published.
 * preinstall:
  Run BEFORE the package is installed
 * install, postinstall:
@@ -18,10 +23,6 @@ following scripts:
  Run BEFORE the package is updated with the update command.
 * update, postupdate:
  Run AFTER the package is updated with the update command.
-* prepublish:
-  Run BEFORE the package is published.
-* publish, postpublish:
-  Run AFTER the package is published.
 * pretest, test, posttest:
  Run by the `npm test` command.
 * prestop, stop, poststop:
@@ -35,6 +36,50 @@ following scripts:
 Additionally, arbitrary scrips can be run by doing
 `npm run-script <stage> <pkg>`.

+## NOTE: INSTALL SCRIPTS ARE AN ANTIPATTERN
+
+**tl;dr** Don't use `install`.  Use a `.gyp` file for compilation, and
+`prepublish` for anything else.
+
+You should almost never have to explicitly set a `preinstall` or
+`install` script.  If you are doing this, please consider if there is
+another option.
+
+The only valid use of `install` or `preinstall` scripts is for
+compilation which must be done on the target architecture.  In early
+versions of node, this was often done using the `node-waf` scripts, or
+a standalone `Makefile`, and early versions of npm required that it be
+explicitly set in package.json.  This was not portable, and harder to
+do properly.
+
+In the current version of node, the standard way to do this is using a
+`.gyp` file.  If you have a file with a `.gyp` extension in the root
+of your package, then npm will run the appropriate `node-gyp` commands
+automatically at install time.  This is the only officially supported
+method for compiling binary addons, and does not require that you add
+anything to your package.json file.
+
+If you have to do other things before your package is used, in a way
+that is not dependent on the operating system or architecture of the
+target system, then use a `prepublish` script instead.  This includes
+tasks such as:
+
+* Compile CoffeeScript source code into JavaScript.
+* Create minified versions of JavaScript source code.
+* Fetching remote resources that your package will use.
+
+The advantage of doing these things at `prepublish` time instead of
+`preinstall` or `install` time is that they can be done once, in a
+single place, and thus greatly reduce complexity and variability.
+Additionally, this means that:
+
+* You can depend on `coffee-script` as a `devDependency`, and thus
+  your users don't need to have it installed.
+* You don't need to include the minifiers in your package, reducing
+  the size for your users.
+* You don't need to rely on your users having `curl` or `wget` or
+  other system tools on the target machines.
+
 ## DEFAULT VALUES

 npm will default some script values based on package contents.
--- a/deps/npm/doc/cli/semver.md
+++ b/deps/npm/doc/cli/semver.md
@@ -11,8 +11,8 @@ As a node module:

    $ npm install semver

-    semver.valid('1.2.3') // true
-    semver.valid('a.b.c') // false
+    semver.valid('1.2.3') // '1.2.3'
+    semver.valid('a.b.c') // null
    semver.clean('  =v1.2.3   ') // '1.2.3'
    semver.satisfies('1.2.3', '1.x || >=2.5.0 || 5.0.0 - 7.2.3') // true
    semver.gt('1.2.3', '9.8.7') // false
@@ -83,7 +83,7 @@ The following range styles are supported:
 * `<1.2.3` Less than
 * `1.2.3 - 2.3.4` := `>=1.2.3 <=2.3.4`
 * `~1.2.3` := `>=1.2.3 <1.3.0`
-* `~1.2` := `>=1.2.0 <2.0.0`
+* `~1.2` := `>=1.2.0 <1.3.0`
 * `~1` := `>=1.0.0 <2.0.0`
 * `1.2.x` := `>=1.2.0 <1.3.0`
 * `1.x` := `>=1.0.0 <2.0.0`
--- a/deps/npm/doc/cli/view.md
+++ b/deps/npm/doc/cli/view.md
@@ -69,7 +69,9 @@ was required by each matching version of yui3:

 If only a single string field for a single version is output, then it
 will not be colorized or quoted, so as to enable piping the output to
-another command.
+another command. If the field is an object, it will be output as a JavaScript object literal.
+
+If the --json flag is given, the outputted fields will be JSON.

 If the version range matches multiple versions, than each printed value
 will be prefixed with the version it applies to.
--- 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.62</p>
+<p id="footer">bin &mdash; npm@1.2.0</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.62</p>
+<p id="footer">bugs &mdash; npm@1.2.0</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.62</p>
+<p id="footer">commands &mdash; npm@1.2.0</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.62</p>
+<p id="footer">config &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/deprecate.html
+++ b/deps/npm/html/api/deprecate.html
@@ -26,11 +26,13 @@ install the package.</p></li></ul>
 <p>Note that you must be the package owner to deprecate something.  See the
 <code>owner</code> and <code>adduser</code> help topics.</p>

+<p>To un-deprecate a package, specify an empty string (<code>&quot;&quot;</code>) for the <code>message</code> argument.</p>
+
 <h2 id="SEE-ALSO">SEE ALSO</h2>

 <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.62</p>
+<p id="footer">deprecate &mdash; npm@1.2.0</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.62</p>
+<p id="footer">docs &mdash; npm@1.2.0</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.62</p>
+<p id="footer">edit &mdash; npm@1.2.0</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 &#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">explore &mdash; npm@1.1.62</p>
+<p id="footer">explore &mdash; npm@1.2.0</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.62</p>
+<p id="footer">help-search &mdash; npm@1.2.0</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.62</p>
+<p id="footer">init &mdash; npm@1.2.0</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, &#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">install &mdash; npm@1.1.62</p>
+<p id="footer">install &mdash; npm@1.2.0</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(&#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">link &mdash; npm@1.1.62</p>
+<p id="footer">link &mdash; npm@1.2.0</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.62</p>
+<p id="footer">load &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/api/ls.html
+++ b/deps/npm/html/api/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">ls &mdash; npm@1.1.62</p>
+<p id="footer">ls &mdash; npm@1.2.0</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.62</p>
+<p>1.2.0</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(&quot;unp&quot;) // cmd === &quot;unpublish&quot;</code></pre>
 </div>
-<p id="footer">npm &mdash; npm@1.1.62</p>
+<p id="footer">npm &mdash; npm@1.2.0</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 &#39;packages&#39; parameter is left out, npm will check all packages.</p>
 </div>
-<p id="footer">outdated &mdash; npm@1.1.62</p>
+<p id="footer">outdated &mdash; npm@1.2.0</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.62</p>
+<p id="footer">owner &mdash; npm@1.2.0</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.62</p>
+<p id="footer">pack &mdash; npm@1.2.0</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.62</p>
+<p id="footer">prefix &mdash; npm@1.2.0</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&#39;s dependencies list.</p>
 </div>
-<p id="footer">prune &mdash; npm@1.1.62</p>
+<p id="footer">prune &mdash; npm@1.2.0</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 &quot;force&quot; environment variable is set

 <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.62</p>
+<p id="footer">publish &mdash; npm@1.2.0</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 &#39;packages&#39; parameter is specify, every package wil

 <p>See <code>npm help build</code></p>
 </div>
-<p id="footer">rebuild &mdash; npm@1.1.62</p>
+<p id="footer">rebuild &mdash; npm@1.2.0</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.62</p>
+<p id="footer">restart &mdash; npm@1.2.0</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.62</p>
+<p id="footer">root &mdash; npm@1.2.0</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.62</p>
+<p id="footer">run-script &mdash; npm@1.2.0</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 &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">search &mdash; npm@1.1.62</p>
+<p id="footer">search &mdash; npm@1.2.0</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, &#39;callback&#39; is a function that will be called when the shrinkwrap has
 been saved.</p>
 </div>
-<p id="footer">shrinkwrap &mdash; npm@1.1.62</p>
+<p id="footer">shrinkwrap &mdash; npm@1.2.0</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.62</p>
+<p id="footer">start &mdash; npm@1.2.0</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.62</p>
+<p id="footer">stop &mdash; npm@1.2.0</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.62</p>
+<p id="footer">submodule &mdash; npm@1.2.0</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.62</p>
+<p id="footer">tag &mdash; npm@1.2.0</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.62</p>
+<p id="footer">test &mdash; npm@1.2.0</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, &#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">uninstall &mdash; npm@1.1.62</p>
+<p id="footer">uninstall &mdash; npm@1.2.0</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.62</p>
+<p id="footer">unpublish &mdash; npm@1.2.0</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 &#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">update &mdash; npm@1.1.62</p>
+<p id="footer">update &mdash; npm@1.2.0</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.62</p>
+<p id="footer">version &mdash; npm@1.2.0</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.62</p>
+<p id="footer">view &mdash; npm@1.2.0</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.62</p>
+<p id="footer">whoami &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/README.html
+++ b/deps/npm/html/doc/README.html
@@ -67,7 +67,7 @@ for testing, or running stuff without actually installing npm itself.)</p>

 <h2 id="Fancy-Windows-Install">Fancy Windows Install</h2>

-<p>You can download a zip file from <a href="http://npmjs.org/dist/">http://npmjs.org/dist/</a>, and unpack it
+<p>You can download a zip file from <a href="https://npmjs.org/dist/">https://npmjs.org/dist/</a>, and unpack it
 in the same folder where node.exe lives.</p>

 <p>If that&#39;s not fancy enough for you, then you can fetch the code with
@@ -175,13 +175,13 @@ 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="http://npmjs.org/doc/">docs</a>,
-especially the <a href="http://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="http://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>

@@ -227,7 +227,7 @@ process for published modules.</p>
 <p>When you find issues, please report them:</p>

 <ul><li>web:
-<a href="http://github.com/isaacs/npm/issues">http://github.com/isaacs/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
@@ -240,7 +240,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.62</p>
+<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.2.0</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.62</p>
+<p id="footer">adduser &mdash; npm@1.2.0</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.62</p>
+<p id="footer">bin &mdash; npm@1.2.0</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.62</p>
+<p id="footer">bugs &mdash; npm@1.2.0</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.62</p>
+<p id="footer">build &mdash; npm@1.2.0</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.62</p>
+<p id="footer">bundle &mdash; npm@1.2.0</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.62</p>
+<p id="footer">cache &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/changelog.html
+++ b/deps/npm/html/doc/changelog.html
@@ -65,7 +65,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.62</p>
+<p id="footer">changelog &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/coding-style.html
+++ b/deps/npm/html/doc/coding-style.html
@@ -17,6 +17,8 @@ designed to reduce visual clutter and make bugs more apparent.</p>
 <p>If you want to contribute to npm (which is very encouraged), you should
 make your code conform to npm&#39;s style.</p>

+<p>Note: this concerns npm&#39;s code not the specific packages at npmjs.org</p>
+
 <h2 id="Line-Length">Line Length</h2>

 <p>Keep lines shorter than 80 characters.  It&#39;s better for lines to be
@@ -180,7 +182,7 @@ set to anything.&quot;</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.62</p>
+<p id="footer">coding-style &mdash; npm@1.2.0</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.62</p>
+<p id="footer">completion &mdash; npm@1.2.0</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>-B</code>: <code>--save-bundle</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>-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>-B</code>: <code>--save-bundle</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
@@ -756,7 +756,7 @@ then answer &quot;no&quot; 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.62</p>
+<p id="footer">config &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/dedupe.html
+++ b/deps/npm/html/doc/dedupe.html
@@ -57,7 +57,7 @@ registry.</p>

 <ul><li><a href="../doc/ls.html">ls(1)</a></li><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
 </div>
-<p id="footer">dedupe &mdash; npm@1.1.62</p>
+<p id="footer">dedupe &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/deprecate.html
+++ b/deps/npm/html/doc/deprecate.html
@@ -25,11 +25,13 @@ something like this:</p>
 <p>Note that you must be the package owner to deprecate something.  See the
 <code>owner</code> and <code>adduser</code> help topics.</p>

+<p>To un-deprecate a package, specify an empty string (<code>&quot;&quot;</code>) for the <code>message</code> argument.</p>
+
 <h2 id="SEE-ALSO">SEE ALSO</h2>

 <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.62</p>
+<p id="footer">deprecate &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/developers.html
+++ b/deps/npm/html/doc/developers.html
@@ -160,7 +160,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.62</p>
+<p id="footer">developers &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/disputes.html
+++ b/deps/npm/html/doc/disputes.html
@@ -12,6 +12,8 @@

 <ol><li>Get the author email with <code>npm owner ls &lt;pkgname&gt;</code></li><li>Email the author, CC <a href="mailto:i@izs.me">i@izs.me</a>.</li><li>After a few weeks, if there&#39;s no resolution, we&#39;ll sort it out.</li></ol>

+<p>Don&#39;t squat on package names.  Publish code or move out of the way.</p>
+
 <h2 id="DESCRIPTION">DESCRIPTION</h2>

 <p>There sometimes arise cases where a user publishes a module, and then
@@ -41,7 +43,7 @@ but can&#39;t publish, because Bob&#39;s <code>foo</code> is in the way.</li></o
 Joe&#39;s appropriate course of action in each case is the same.</p>

 <ol><li><code>npm owner ls foo</code>.  This will tell Joe the email address of the
-owner (Bob).</li><li>Joe emails Bob, explaining the situation <strong>as respecfully as possible</strong>,
+owner (Bob).</li><li>Joe emails Bob, explaining the situation <strong>as respectfully as possible</strong>,
 and what he would like to do with the module name.  He adds
 isaacs <a href="mailto:i@izs.me">i@izs.me</a> to the CC list of the email.  Mention in the email
 that Bob can run <code>npm owner add joe foo</code> to add Joe as an owner of
@@ -72,7 +74,11 @@ but not limited to:</p>
 <ol><li>Malware (that is, a module designed to exploit or harm the machine on
 which it is installed)</li><li>Violations of copyright or licenses (for example, cloning an
 MIT-licensed program, and then removing or changing the copyright and
-license statement)</li><li>Illegal content.</li></ol>
+license statement)</li><li>Illegal content.</li><li>&quot;Squatting&quot; on a package name that you <em>plan</em> to use, but aren&#39;t
+actually using.  Sorry, I don&#39;t care how great the name is, or how
+perfect a fit it is for the thing that someday might happen.  If
+someone wants to use it today, and you&#39;re just taking up space with
+an empty tarball, you&#39;re going to be evicted.</li></ol>

 <p>If you see bad behavior like this, please report it right away.</p>

@@ -80,7 +86,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.62</p>
+<p id="footer">disputes &mdash; npm@1.2.0</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.62</p>
+<p id="footer">docs &mdash; npm@1.2.0</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>&quot;notepad&quot;</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.62</p>
+<p id="footer">edit &mdash; npm@1.2.0</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.62</p>
+<p id="footer">explore &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/faq.html
+++ b/deps/npm/html/doc/faq.html
@@ -10,7 +10,7 @@

 <h2 id="Where-can-I-find-these-docs-in-HTML">Where can I find these docs in HTML?</h2>

-<p><a href="http://npmjs.org/doc/">http://npmjs.org/doc/</a>, or run:</p>
+<p><a href="https://npmjs.org/doc/">https://npmjs.org/doc/</a>, or run:</p>

 <pre><code>npm config set viewer browser</code></pre>

@@ -148,7 +148,7 @@ command.)</p>

 <p>In those cases, you can do this:</p>

-<pre><code>curl http://npmjs.org/install.sh | sh</code></pre>
+<pre><code>curl https://npmjs.org/install.sh | sh</code></pre>

 <h2 id="What-is-a-package">What is a <code>package</code>?</h2>

@@ -175,7 +175,7 @@ an argument to <code>git checkout</code>.  The default is <code>master</code>.</

 <p>You don&#39;t.  Try one of these:</p>

-<ul><li><a href="http://github.com/isaacs/nave">http://github.com/isaacs/nave</a></li><li><a href="http://github.com/visionmedia/n">http://github.com/visionmedia/n</a></li><li><a href="http://github.com/creationix/nvm">http://github.com/creationix/nvm</a></li></ul>
+<ul><li><a href="https://github.com/isaacs/nave">https://github.com/isaacs/nave</a></li><li><a href="https://github.com/visionmedia/n">https://github.com/visionmedia/n</a></li><li><a href="https://github.com/creationix/nvm">https://github.com/creationix/nvm</a></li></ul>

 <h2 id="How-can-I-use-npm-for-development">How can I use npm for development?</h2>

@@ -240,7 +240,7 @@ There is not sufficient need to impose namespace rules on everyone.</p>

 <p>Discuss it on the mailing list, or post an issue.</p>

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

 <h2 id="Why-does-npm-hate-me">Why does npm hate me?</h2>

@@ -250,7 +250,7 @@ There is not sufficient need to impose namespace rules on everyone.</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.62</p>
+<p id="footer">faq &mdash; npm@1.2.0</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.62</p>
+<p id="footer">folders &mdash; npm@1.2.0</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.62</p>
+<p id="footer">help-search &mdash; npm@1.2.0</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.62</p>
+<p id="footer">help &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/index.html
+++ b/deps/npm/html/doc/index.html
@@ -388,7 +388,7 @@

 <p> Display npm username</p>
 </div>
-<p id="footer">index &mdash; npm@1.1.62</p>
+<p id="footer">index &mdash; npm@1.2.0</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="https://github.com/isaacs/init-package-json">https://github.com/isaacs/init-package-json</a></li><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.62</p>
+<p id="footer">init &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/install.html
+++ b/deps/npm/html/doc/install.html
@@ -133,7 +133,7 @@ affects a real use-case, it will be investigated.</p>

 <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>
 </div>
-<p id="footer">install &mdash; npm@1.1.62</p>
+<p id="footer">install &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/json.html
+++ b/deps/npm/html/doc/json.html
@@ -339,7 +339,7 @@ a version in the following fashion.</p>

 <p>For example, the following are equivalent:</p>

-<ul><li><code>&quot;~1.2.3&quot; = &quot;&gt;=1.2.3 &lt;1.3.0&quot;</code></li><li><code>&quot;~1.2&quot; = &quot;&gt;=1.2.0 &lt;2.0.0&quot;</code></li><li><code>&quot;~1&quot; = &quot;&gt;=1.0.0 &lt;2.0.0&quot;</code></li></ul>
+<ul><li><code>&quot;~1.2.3&quot; = &quot;&gt;=1.2.3 &lt;1.3.0&quot;</code></li><li><code>&quot;~1.2&quot; = &quot;&gt;=1.2.0 &lt;1.3.0&quot;</code></li><li><code>&quot;~1&quot; = &quot;&gt;=1.0.0 &lt;1.1.0&quot;</code></li></ul>

 <h3 id="X-Version-Ranges">X Version Ranges</h3>

@@ -525,7 +525,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.62</p>
+<p id="footer">json &mdash; npm@1.2.0</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&#39;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.62</p>
+<p id="footer">link &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/ls.html
+++ b/deps/npm/html/doc/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.1.62 /path/to/npm
+<pre><code>npm@1.2.0 /path/to/npm
 └─┬ init-package-json@0.0.4
  └── promzard@0.1.5</code></pre>

@@ -64,7 +64,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">ls &mdash; npm@1.1.62</p>
+<p id="footer">ls &mdash; npm@1.2.0</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.62</p>
+<p>1.2.0</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.62</p>
+<p id="footer">npm &mdash; npm@1.2.0</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.62</p>
+<p id="footer">outdated &mdash; npm@1.2.0</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.62</p>
+<p id="footer">owner &mdash; npm@1.2.0</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.62</p>
+<p id="footer">pack &mdash; npm@1.2.0</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.62</p>
+<p id="footer">prefix &mdash; npm@1.2.0</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&#39;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.62</p>
+<p id="footer">prune &mdash; npm@1.2.0</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 &quot;--force&quot; 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.62</p>
+<p id="footer">publish &mdash; npm@1.2.0</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.62</p>
+<p id="footer">rebuild &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/registry.html
+++ b/deps/npm/html/doc/registry.html
@@ -89,15 +89,13 @@ ask for help on the <a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com

 <h2 id="Is-there-a-website-or-something-to-see-package-docs-and-such">Is there a website or something to see package docs and such?</h2>

-<p>No, but such a thing is planned, and a tiny bit developed.</p>
-
-<p>Stay tuned!</p>
+<p>Yes, head over to <a href="https://npmjs.org/">https://npmjs.org/</a></p>

 <h2 id="SEE-ALSO">SEE ALSO</h2>

 <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.62</p>
+<p id="footer">registry &mdash; npm@1.2.0</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.62</p>
+<p id="footer">removing-npm &mdash; npm@1.2.0</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 &quot;start&quot; 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.62</p>
+<p id="footer">restart &mdash; npm@1.2.0</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.62</p>
+<p id="footer">root &mdash; npm@1.2.0</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.62</p>
+<p id="footer">run-script &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/deps/npm/html/doc/scripts.html
+++ b/deps/npm/html/doc/scripts.html
@@ -13,15 +13,16 @@
 <p>npm supports the &quot;scripts&quot; member of the package.json script, for the
 following scripts:</p>

-<ul><li>preinstall:
+<ul><li>prepublish:
+Run BEFORE the package is published.  (Also run on local <code>npm
+install</code> without any arguments.)</li><li>publish, postpublish:
+Run AFTER the package is published.</li><li>preinstall:
 Run BEFORE the package is installed</li><li>install, postinstall:
 Run AFTER the package is installed.</li><li>preuninstall, uninstall:
 Run BEFORE the package is uninstalled.</li><li>postuninstall:
 Run AFTER the package is uninstalled.</li><li>preupdate:
 Run BEFORE the package is updated with the update command.</li><li>update, postupdate:
-Run AFTER the package is updated with the update command.</li><li>prepublish:
-Run BEFORE the package is published.</li><li>publish, postpublish:
-Run AFTER the package is published.</li><li>pretest, test, posttest:
+Run AFTER the package is updated with the update command.</li><li>pretest, test, posttest:
 Run by the <code>npm test</code> command.</li><li>prestop, stop, poststop:
 Run by the <code>npm stop</code> command.</li><li>prestart, start, poststart:
 Run by the <code>npm start</code> command.</li><li>prerestart, restart, postrestart:
@@ -31,6 +32,46 @@ stop and start scripts if no <code>restart</code> script is provided.</li></ul>
 <p>Additionally, arbitrary scrips can be run by doing
 <code>npm run-script &lt;stage&gt; &lt;pkg&gt;</code>.</p>

+<h2 id="NOTE-INSTALL-SCRIPTS-ARE-AN-ANTIPATTERN">NOTE: INSTALL SCRIPTS ARE AN ANTIPATTERN</h2>
+
+<p><strong>tl;dr</strong> Don&#39;t use <code>install</code>.  Use a <code>.gyp</code> file for compilation, and
+<code>prepublish</code> for anything else.</p>
+
+<p>You should almost never have to explicitly set a <code>preinstall</code> or
+<code>install</code> script.  If you are doing this, please consider if there is
+another option.</p>
+
+<p>The only valid use of <code>install</code> or <code>preinstall</code> scripts is for
+compilation which must be done on the target architecture.  In early
+versions of node, this was often done using the <code>node-waf</code> scripts, or
+a standalone <code>Makefile</code>, and early versions of npm required that it be
+explicitly set in package.json.  This was not portable, and harder to
+do properly.</p>
+
+<p>In the current version of node, the standard way to do this is using a
+<code>.gyp</code> file.  If you have a file with a <code>.gyp</code> extension in the root
+of your package, then npm will run the appropriate <code>node-gyp</code> commands
+automatically at install time.  This is the only officially supported
+method for compiling binary addons, and does not require that you add
+anything to your package.json file.</p>
+
+<p>If you have to do other things before your package is used, in a way
+that is not dependent on the operating system or architecture of the
+target system, then use a <code>prepublish</code> script instead.  This includes
+tasks such as:</p>
+
+<ul><li>Compile CoffeeScript source code into JavaScript.</li><li>Create minified versions of JavaScript source code.</li><li>Fetching remote resources that your package will use.</li></ul>
+
+<p>The advantage of doing these things at <code>prepublish</code> time instead of
+<code>preinstall</code> or <code>install</code> time is that they can be done once, in a
+single place, and thus greatly reduce complexity and variability.
+Additionally, this means that:</p>
+
+<ul><li>You can depend on <code>coffee-script</code> as a <code>devDependency</code>, and thus
+your users don&#39;t need to have it installed.</li><li>You don&#39;t need to include the minifiers in your package, reducing
+the size for your users.</li><li>You don&#39;t need to rely on your users having <code>curl</code> or <code>wget</code> or
+other system tools on the target machines.</li></ul>
+
 <h2 id="DEFAULT-VALUES">DEFAULT VALUES</h2>

 <p>npm will default some script values based on package contents.</p>
@@ -177,7 +218,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.62</p>
+<p id="footer">scripts &mdash; npm@1.2.0</p>
 <script>
 ;(function () {
 var wrapper = document.getElementById("wrapper")
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
isaacs	c50c33e939	2012.01.09, Version 0.8.17 (Stable) * npm: Upgrade to v1.2.0 - peerDependencies (Domenic Denicola) - node-gyp v0.8.2 (Nathan Rajlich) - Faster installs from github user/project shorthands (Nathan Zadoks) * typed arrays: fix 32 bit size/index overflow (Ben Noordhuis) * http: Improve performance of single-packet responses (Ben Noordhuis) * install: fix openbsd man page location (Ben Noordhuis) * http: bubble up parser errors to ClientRequest (Brian White)	2013-01-09 16:55:12 -08:00
Ben Noordhuis	ed825f4888	typed arrays: fix 32 bit size/index overflow Fix an out-of-bound read/write bug due to integer wrapping. Reported by Dean McNamee.	2013-01-10 00:55:27 +01:00
isaacs	aa742ddf80	npm: Upgrade to v1.2.0	2013-01-09 15:21:30 -08:00
Fedor Indutny	7a2ae4c930	object_wrap: add missing HandleScope by Sven Panne's suggestion, see [0] for details. [0]: https://code.google.com/p/v8/issues/detail?id=2468	2013-01-09 12:16:04 +04:00
Ben Noordhuis	ad6769fc92	dgram: don't assert on send('string') Raise a TypeError when the argument to send() or sendto() is anything but a Buffer. Fixes the following assertion: $ node -e 'require("dgram").createSocket("udp4").send("BAM")' node: ../../src/udp_wrap.cc:220: static v8::Handle<v8::Value> node::UDPWrap::DoSend(const v8::Arguments&, int): Assertion `Buffer::HasInstance(args[0])' failed. Aborted (core dumped) Fixes #4496.	2013-01-08 04:32:40 +01:00
Johannes Ewald	872cb0d7fa	doc: improve example of process.hrtime() The example clarifies now that diff[0] * 1000000000 + diff[1] equals the result in nanoseconds.	2013-01-04 23:06:40 +01:00
Tim Bradshaw	50e88d0b66	os: change CPU time from Integer to Number CPU time values must be Numbers, not Integers, as they can be too large for Integers on 32 bit platforms.	2012-12-31 18:09:36 +01:00
Ben Noordhuis	acc085e131	doc: add CONTRIBUTING.md	2012-12-31 01:50:48 +01:00
isaacs	44ceb5d8f5	blog: Post for v0.9.5	2012-12-29 17:26:32 -08:00
Ben Noordhuis	a7cc53067d	deps: upgrade libuv to 4997738	2012-12-29 17:34:41 +01:00
Maciej Małecki	c2e71dd51d	build: allow to specify custom tags When building custom `node` versions (e.g., floating features/fixes from different versions) it's often useful to specify a custom tag which easily identifies build when invoking `node -v`. Introduce a way to specify this tag in `node_version.h` file or by running `./configure --tag="<tag>"`. Insert it right after the patch version (and before `-pre`, if build is not a release).	2012-12-26 20:15:17 -08:00
isaacs	54740c8b24	lint	2012-12-26 15:26:53 -08:00
isaacs	6738e68592	blog: Post about v0.9.4	2012-12-21 12:37:39 -08:00
isaacs	d30e76e0e8	npm: upgrade to 1.1.70	2012-12-21 16:42:29 +00:00
isaacs	9d0103d22e	blog: More streams2 wordsmithing	2012-12-21 00:46:40 +00:00
isaacs	0c867ae618	blog: Update blog post re streams2	2012-12-21 00:08:50 +00:00
Ben Noordhuis	5a19c07c08	http: pack response body buffer in first tcp packet Apply the same optimization to res.end(buf) that is applied to res.end(str). Speeds up `node benchmark/http_simple_auto -k -c 1 -n 25000 buffer/1` (non-chunked response body) by about 750x. That's not a typo. Chunked responses: $ cat tmp/http-chunked-client.js // Run `node benchmark/http_simple` in another terminal. var http = require('http'), url = require('url'); var options = url.parse('http://127.0.0.1:8000/buffer/1/1'); options.agent = new http.Agent({ maxSockets: 1 }); for (var i = 0; i < 25000; ++i) http.get(options); Before: $ time out/Release/node tmp/http-chunked-client.js real 16m40.411s user 0m9.184s sys 0m0.604s After: $ time out/Release/node tmp/http-chunked-client.js real 0m5.386s user 0m2.768s sys 0m0.728s That's still a 185x speed-up. Fixes #4415.	2012-12-20 12:02:06 +01:00
Ben Noordhuis	ba407ce410	bench: use res.end() for chunked encoding Use res.end() for the final chunk so we can benchmark the 'hot path' shortcut in lib/http.js that packs the headers and the body into a single packet.	2012-12-20 11:44:10 +01:00
isaacs	04adf0e5a1	blog: post about streams2 feature	2012-12-18 08:45:03 -08:00
Nicolas Chambrier	496c0bd936	doc: add Google+ French community	2012-12-17 17:21:35 +01:00
Ben Noordhuis	53b826e6ae	install: fix openbsd man page location Man pages go into $PREFIX/man on OpenBSD, not $PREFIX/share/man.	2012-12-17 12:05:14 +01:00
Brian White	827b2a9b0b	http: bubble up parser errors to ClientRequest Make parser errors bubble up to the ClientRequest instead of the underlying net.Socket object. This is a back-port of commit `c78678b` from the master branch. Fixes #3776.	2012-12-16 17:25:03 +01:00
isaacs	45cdb0e4c1	blog: Post for 0.8.16	2012-12-13 11:50:47 -08:00
isaacs	953673424a	Now working on 0.8.17	2012-12-13 11:50:35 -08:00
isaacs	a18507ce11	Merge commit 'v0.8.16' into v0.8	2012-12-13 11:50:15 -08:00
isaacs	1c9c6277d5	2012.12.13, Version 0.8.16 (Stable) * npm: Upgrade to 1.1.69 * fs: fix WriteStream/ReadStream fd leaks (Ben Noordhuis) * crypto: fix leak in GetPeerCertificate (Fedor Indutny) * buffer: Don't double-negate numeric buffer arg (Trevor Norris) * net: More accurate IP address validation and IPv6 dotted notation. (Joshua Erickson)	2012-12-13 11:49:39 -08:00
isaacs	b09f97068e	npm: Upgrade to v1.1.69	2012-12-12 14:41:28 -08:00
Ben Noordhuis	d65832ccd0	fs: fix WriteStream fd leak Close the file descriptor when a write operation fails. Fixes #4387.	2012-12-12 09:46:22 +01:00
Ben Noordhuis	6e97b2cc17	fs: fix ReadStream fd leak Close the file descriptor when a read operation fails. Fixes #4387.	2012-12-12 09:46:22 +01:00
Ben Noordhuis	65d824b488	test: add common.mustCall function Verifies that the callback gets invoked <n> times during the lifetime of the test script. This is a back-port of commit `d0e6c3f` from the master branch.	2012-12-12 09:46:09 +01:00
isaacs	92e92b0215	doc: Add nodejstr to community page	2012-12-10 16:56:49 -08:00
Ben Noordhuis	c79fd0e167	doc: remove broken require.extensions example Fixes #4384.	2012-12-06 21:58:36 +01:00
Fedor Indutny	276245d26f	crypto: fix leak in GetPeerCertificate	2012-12-03 20:30:16 +04:00
Ben Noordhuis	e5649d4b3d	tools: fix platform detection on freebsd, sunos This is a back-port of upstream gyp commit r1482.	2012-12-02 03:01:20 +01:00
Ben Noordhuis	22965da799	install: fix freebsd man page location Man pages go into $PREFIX/man on FreeBSD, not $PREFIX/share/man.	2012-12-02 02:55:50 +01:00
Lewuathe	4d0fcd515f	Fix dropped html tag	2012-11-30 18:14:26 -08:00
Trevor Norris	6772308883	buffer: Don't double-negate numeric buffer arg Fix #4331 Using double negate forces values into 32bit space. Because of this Math.ceil needs to be used. Since NaN comparisons are always false, use that to our advantage to return 0 if it is. Also added two tests to verify the changes.	2012-11-30 16:23:49 -08:00
Kyle Robinson Young	acad8d9a77	website: typo fixes	2012-11-29 23:00:09 +01:00
Joshua Erickson	c9f2531ae0	net: More accurate IP address validation and IPv6 dotted notation. * Added isIP method to make use of inet_pton to cares_wrap.cc * Modified net.isIP() to make use of new C++ isIP method. * Added new tests to test-net-isip.js. This is a back-port of commit `fb6377e` from the master branch.	2012-11-28 21:51:27 +01:00
Ryunosuke SATO	83161455bd	doc: Fix missing link target to 'https.request()'	2012-11-27 18:11:40 -08:00
isaacs	122ac4e1f2	blog: Post for v0.8.15	2012-11-26 09:20:07 -08:00
isaacs	e773be6f90	Now working on 0.8.16	2012-11-26 09:18:33 -08:00
isaacs	9f51fd6b84	Merge branch 'v0.8.15-release' into v0.8	2012-11-26 09:12:52 -08:00
isaacs	fdf91afb49	2012.11.26, Version 0.8.15 (Stable) * npm: Upgrade to 1.1.66 (isaacs) * linux: use /proc/cpuinfo for CPU frequency (Ben Noordhuis) * windows: map WSAESHUTDOWN to UV_EPIPE (Ben Noordhuis) * windows: map ERROR_GEN_FAILURE to UV_EIO (Bert Belder) * unix: do not set environ unless one is provided (Charlie McConnell) * domains: don't crash if domain is set to null (Bert Belder) * windows: fix the x64 debug build (Bert Belder) * net, tls: fix connect() resource leak (Ben Noordhuis)	2012-11-26 08:39:49 -08:00
Ben Noordhuis	121ed91331	tls: fix tls.connect() resource leak The 'secureConnect' event listener was attached with .on(), which blocked it from getting garbage collected. Use .once() instead. Fixes #4308.	2012-11-26 01:51:05 +01:00
Ben Noordhuis	4cb17cb219	net: fix net.connect() resource leak The 'connect' event listener was attached with .on(), which blocked it from getting garbage collected. Use .once() instead. Fixes #4308.	2012-11-24 15:27:14 +01:00
isaacs	fb5c7f03a0	blog: Don't filter out non-latest release notes This causes too many people to ask me why it's broken.	2012-11-23 12:54:33 -08:00
isaacs	db008f7cce	npm: Upgrade to 1.1.66	2012-11-23 12:51:23 -08:00
Trevor Norris	bb867c0fa6	doc: Add lines about additonal uses of Buffer That Buffers can be used with Typed Array Views and DataViews. Included are a couple simple examples. Closes #4257.	2012-11-22 09:30:18 -08:00
Ben Noordhuis	7716828166	deps: upgrade libuv to 5639b2f	2012-11-20 19:21:48 +01:00
Bert Belder	b3bfb6fbb6	domains: don't crash if domain is set to null Closes #4256	2012-11-09 00:49:24 +01:00
Bert Belder	9b22944b68	windows: fix the x64 debug build	2012-11-08 23:54:53 +01:00
Francois Marier	44dd2c392a	doc: remove duplicate set of options	2012-10-30 01:20:17 +01:00
Francois Marier	326bce91d6	doc: reflect hostname v. host preference in examples The documentation for http.request and https.request states that `hostname` is preferred over `host` so the code examples should use that option name.	2012-10-29 20:34:03 +01:00
isaacs	5f0a10ad21	blog: Correct shasums for v0.8.14	2012-10-25 14:42:47 -07:00
isaacs	7fe1671727	blog: Post for v0.8.14	2012-10-25 14:17:43 -07:00
isaacs	54e88b3d61	Now working on 0.8.15	2012-10-25 14:16:53 -07:00
isaacs	4379e49818	Merge branch 'v0.8.14-release' into v0.8	2012-10-25 14:15:27 -07:00
isaacs	b00527fcf0	2012.10.25, Version 0.8.14 (Stable) * events: Don't clobber pre-existing _events obj in EE ctor (isaacs)	2012-10-25 13:49:32 -07:00
isaacs	45a13d9674	events: Don't clobber pre-existing _events obj in EE ctor	2012-10-25 13:37:08 -07:00
isaacs	d130bb060e	blog: Post for v0.8.13	2012-10-25 12:54:00 -07:00
isaacs	648e38771e	Now working on 0.8.14	2012-10-25 12:52:46 -07:00
isaacs	d269f7e48c	Merge branch 'v0.8.13-release' into v0.8	2012-10-25 12:52:26 -07:00
isaacs	ff4c974873	2012.10.25, Version 0.8.13 (Stable) * V8: Upgrade to 3.11.10.25 * npm: Upgrade to 1.1.65 * url: parse hostnames that start with - or _ (Ben Noordhuis) * repl: Fix Windows 8 terminal issue (Bert Belder) * typed arrays: use signed char for signed int8s (Aaron Jacobs) * crypto: fix bugs in DiffieHellman (Ben Noordhuis) * configure: turn on VFPv3 on ARMv7 (Ben Noordhuis) * Re-enable OpenSSL UI for entering passphrases via tty (Ben Noordhuis) * repl: ensure each REPL instance gets its own "context" (Nathan Rajlich)	2012-10-25 11:46:13 -07:00
isaacs	e1bdde05c7	V8 build: 'echo -n' considered harmful	2012-10-25 11:46:13 -07:00
isaacs	822e13d375	npm: Upgrade to 1.1.65	2012-10-25 09:15:35 -07:00
isaacs	c7b2e29e5e	events: Make the EventEmitter class monomorphic Always add domain, _events, and _maxListeners properties, set to the default values at first. Leads to a very very slight perf improvement when using setMaxListeners, or dealing with a lot of EE objects that don't have any listeners.	2012-10-25 07:51:05 -07:00
Ben Noordhuis	4b8629db37	v8: remove optimization switches Remove compiler switches from $(TOPLEVEL)/deps/v8/build/common.gypi, we set them globally in $(TOPLEVEL)/common.gypi. Commit `29d12c73` accidentally reintroduced the switches again. In particular, the 'cflags!': ['-O2','-Os'] section forced building V8 without any optimizations, resulting in a steep (~66%) performance drop on some benchmarks. Fixes #4191.	2012-10-25 01:06:00 +02:00
Ben Noordhuis	28e6403a56	build: add --unsafe-optimizations configure switch Turns on -O3 and other optimizations that may produce buggy code with some toolchains. Use at your own risk.	2012-10-25 01:06:00 +02:00
Ben Noordhuis	de0303d3ad	url: parse hostnames that start with - or _ Allow hostnames like '-lovemonsterz.tumblr.com' and '_jabber._tcp.google.com'. Fixes #4177.	2012-10-25 01:06:00 +02:00
isaacs	82a72e9591	blog: Post for v0.9.3 release	2012-10-24 10:08:58 -07:00
Bert Belder	f34f1e30a6	repl: call resume() after setRawMode() Solves #4178, but does not fix the underlying issue	2012-10-24 02:52:18 +02:00
Olivier Lalonde	626db18635	doc: child_process: document uid and gid spawn() options	2012-10-24 01:24:00 +02:00
isaacs	76a6c4bf2e	V8: Reapply patches	2012-10-23 11:38:09 -07:00
isaacs	29d12c7342	V8: Upgrade to 3.11.10.25	2012-10-23 11:35:27 -07:00
isaacs	7413df0c1f	npm: Upgrade to 1.1.64	2012-10-23 11:34:46 -07:00
Ben Noordhuis	b6b881378a	test: add typed arrays regression test Ensure that uint8 values >= 128 are correctly promoted to int8 <= -1.	2012-10-23 17:12:39 +02:00
Aaron Jacobs	49f0f618a9	typed arrays: use `signed char` for signed int8s The C standard allows plain `char` to be unsigned. The build environment at Google trips this issue.	2012-10-23 16:55:59 +02:00
yangguo@chromium.org	9fa953d3e7	v8: use correct timezone information on Solaris `timezone` variable contains the difference, in seconds, between UTC and local standard time (see `man 3 localtime` on Solaris). Call to `tzset` is required to apply contents of `TZ` variable to `timezone` variable. BUG=v8:2064 Review URL: https://chromiumcodereview.appspot.com/10967066 Patch from Maciej Małecki <me@mmalecki.com>. This is a back-port of upstream commit r12802.	2012-10-23 16:43:38 +02:00
Ben Noordhuis	844a0058d0	crypto: fix DH use-after-free and memory leak Fix a use-after-free bug and a memory leak in the error path of DiffieHellman::ComputeSecret(). * the BIGNUM key was used after being freed with BN_free(). * the output buffer was not freed	2012-10-22 00:20:45 +02:00
Ben Noordhuis	de18e29784	crypto: fix DH 1 byte buffer underflow Passing a bad key to DiffieHellman::ComputeSecret() made it zero the byte before the heap allocated buffer due to an erroneous size calculation.	2012-10-22 00:20:32 +02:00
Ben Noordhuis	82df345fbb	test: add diffie-hellman regression test Exercises the error path in DiffieHellman::ComputeSecret() in src/node_crypto.cc	2012-10-21 23:56:01 +02:00
isaacs	627f0d27e8	doc: Typo. s/arguemnt/argument/	2012-10-16 10:59:23 -07:00
Nathan Rajlich	cca15e8e33	test: disable global variable check for "test-repl-options.js" Previously, the "global" mode of REPLs was broken when created after another non-global REPL (they would end up sharing the same context). Now that "global" mode is fixed for that case (`b1e78cef09`), this test case gets its global scope modified with "module" and other REPL-specific properties, so disable the global check.	2012-10-15 14:59:57 -07:00
Ben Noordhuis	1205734e69	configure: turn on VFPv3 on ARMv7 Fixes a V8 build error caused by missing arm_fpu and arm_neon settings. This is a back-port of commit `bbf6b4e` from the master branch. Fixes #4142.	2012-10-15 23:55:26 +02:00
Ben Noordhuis	28b0cc08b8	Revert "Disable OpenSSL UI" This reverts commit `1c88c3b3b5`. It breaks the "read a password from stdin" functionality that OpenSSL provides. Fixes #4059, #4143. Conflicts: deps/openssl/openssl.gyp	2012-10-15 23:40:15 +02:00
Jan Lehnardt	a7b5938715	docs: fix copy and paste error	2012-10-14 14:47:02 +02:00
Ben Noordhuis	4a23add90f	doc: rectify http.ClientResponse close/end events * The 'close' event doesn't emit an error object. * It's possible for a 'close' event to come after an 'end' event, contrary to what the documentation said. Fixes #4116.	2012-10-13 15:17:51 +02:00
Nathan Rajlich	b1e78cef09	repl: ensure each REPL instance gets its own "context" Before there was this weird module-scoped "context" variable which seemingly shared the "context" of subsequent REPL instances, unless ".clear" was invoked inside the REPL. To be proper, we need to ensure that each REPL gets its own "context" object. I literally don't know why this "sharing" behavior was in place before, but it was just plain wrong.	2012-10-12 16:37:17 -07:00
Max Ogden	323bbdb0cb	doc: set default background color to white	2012-10-13 00:54:21 +02:00
isaacs	58db21e6c5	Now working on 0.8.13	2012-10-12 08:57:25 -07:00
isaacs	b3536ae0a8	blog: Post about 0.8.12	2012-10-12 08:57:12 -07:00
isaacs	d411622814	Merge branch 'v0.8.12-release' into v0.8	2012-10-12 08:56:53 -07:00
isaacs	38c72d4e29	2012.10.12, Version 0.8.12 (Stable) * npm: Upgrade to 1.1.63 * crypto: Reduce stability index to 2-Unstable (isaacs) * windows: fix handle leak in uv_fs_utime (Bert Belder) * windows: fix application crashed popup in debug version (Bert Belder) * buffer: report proper retained size in profiler (Ben Noordhuis) * buffer: fix byteLength with UTF-16LE (koichik) * repl: make "end of input" JSON.parse() errors throw in the REPL (Nathan Rajlich) * repl: make invalid RegExp modifiers throw in the REPL (Nathan Rajlich) * http: handle multiple Proxy-Authenticate values (Willi Eggeling)	2012-10-11 14:34:11 -07:00
isaacs	218f08dbde	npm: Upgrade to 1.1.63	2012-10-11 14:11:38 -07:00
isaacs	99b2368a6c	doc: Reduce crypto stability to 2-Unstable	2012-10-11 08:32:46 -07:00
Ben Noordhuis	6a128e037e	buffer: report proper retained size in profiler Make buffers report the proper retained size in heap snapshots. Before this commit, Buffer objects would show up in the heap profiler as being only a few hundred bytes large, even if the actual buffer was many megabytes.	2012-10-11 01:05:18 +02:00
Bert Belder	87518f1e3c	uv: upgrade to b0c1a38	2012-10-10 17:18:48 +02:00
Ben Noordhuis	eec8c2edaf	crypto: fix -Wtautological-compare warning	2012-10-09 00:46:51 +02:00
Andreas Madsen	be5a8e24c2	doc: consistent use of the callback argument	2012-10-08 22:58:11 +02:00
Andrew Paprocki	8c5f269f90	Fix -Wsizeof-array-argument compiler warning.	2012-10-07 23:22:31 +02:00
Nathan Rajlich	59c166cfba	repl: move "isSyntaxError()" definition to the bottom fixes lint "line length too long" error	2012-10-05 18:33:28 -07:00
Nathan Rajlich	f826b3269d	doc: document the custom "inspect()" function behavior Closes #3361.	2012-10-05 16:48:13 -07:00
koichik	fbb0ee6f24	buffer: fix byteLength with UTF-16LE Fixes #4075.	2012-10-04 18:18:15 +09:00
Alex Kocharin	bf0bc3565b	doc: better example for process.hrtime() Fixes #3984.	2012-10-03 22:18:33 +02:00
Ben Noordhuis	b0d04ffbd8	doc: stream: clarify meaning of 'drain' some more Courtesy of Lee Coltrane (@coltrane).	2012-10-03 13:38:03 +02:00
Ben Noordhuis	f624be4093	doc: stream: clarify meaning of 'drain' event	2012-10-03 00:49:27 +02:00
isaacs	b90c1502e5	doc: Correct stream.write fd mention No streams actually work this way.	2012-10-01 14:30:02 -07:00
Nathan Rajlich	3b7312d23a	repl: make "end of input" JSON.parse() errors throw in the REPL	2012-10-01 11:36:06 -07:00
Nathan Rajlich	f1722a280c	repl: make invalid RegExp modifiers throw in the REPL Fixes #4012.	2012-09-30 22:47:57 -07:00
isaacs	fa912c246c	blog: s/LibUV/libuv/	2012-09-30 15:47:27 -07:00
isaacs	d3e818cf8f	blog: LXJS talk by @piscisaureus	2012-09-30 10:34:28 -07:00
thewilli	33a5c8a814	http: handle multiple Proxy-Authenticate values Just as the 'WWW-Authenticate' HTTP header the 'Proxy-Authenticate' header might be received several times as well. Currently only one value is preserved. This change allows to receive multiple values concatenated by space and comma.	2012-09-27 13:28:16 -07:00
isaacs	c08320c957	doc: Make the CLA more simple/sane 1. Emails should go to @isaacs, not emily. 2. Ask for the electronic signature first, not the printed faxed thing.	2012-09-27 13:25:55 -07:00
isaacs	dcc01df968	blog: Post about 0.8.11	2012-09-27 10:25:37 -07:00
isaacs	9877b8f414	Now working on 0.8.12	2012-09-27 10:25:12 -07:00
isaacs	a9429052c2	Merge branch 'v0.8.11-release' into v0.8	2012-09-27 10:24:32 -07:00