deps: update npm to 5.5.1

Closes: https://github.com/nodejs/node/pull/16280 PR-URL: https://github.com/nodejs/node/pull/16509 Fixes: https://github.com/nodejs/node/issues/14161 Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Michaël Zasso <targos@protonmail.com>
2017-10-26 22:35:25 -04:00 · 2017-10-26 22:35:25 -04:00 · ace4fe566f
commit ace4fe566f
parent 64168eb9b4
1841 changed files with 108157 additions and 33875 deletions
--- a/deps/npm/.mailmap
+++ b/deps/npm/.mailmap
@ -32,6 +32,7 @@ Jake Verbaten <raynos2@gmail.com>
 James Sanders <jimmyjazz14@gmail.com>
 James Treworgy <jamietre@gmail.com>
 Jason Smith <jhs@iriscouch.com>
 Joshua Bennett <legodudejb@gmail.com>
 Jonas Weber <github@jonasw.de>
 Julien Meddah <julien.meddah@deveryware.com>
 Kevin Lorenz <mail@kevinlorenz.com>
--- a/deps/npm/.travis.yml
+++ b/deps/npm/.travis.yml
@ -25,9 +25,6 @@ matrix:
      script:
       - "standard"
       - "node . run tap -- \"test/tap/*.js\" \"test/broken-under-nyc/*.js\""
 before_install:
  # required by test/tap/registry.js
  - "mkdir -p /var/run/couchdb"
 notifications:
    slack: npm-inc:kRqQjto7YbINqHPb1X6nS3g8
 cache:
--- a/deps/npm/AUTHORS
+++ b/deps/npm/AUTHORS
@ -424,7 +424,7 @@ Daniel Paz-Soldan <daniel.pazsoldan@gmail.com>
 Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
 Zach Renner <zarenner@microsoft.com>
 Christopher Hiller <boneskull@boneskull.com>
-legodude17 <legodudejb@gmail.com>
+Joshua Bennett <legodudejb@gmail.com>
 Andrew Meyer <andrewm.bpi@gmail.com>
 Michael Jasper <mdjasper@gmail.com>
 Max <contact@mstoiber.com>
@ -503,3 +503,26 @@ Sanketh Katta <sankethkatta@gmail.com>
 Tim Needham <tim.needham@wmfs.net>
 leonardo rojas <leonardo.rojas@shopify.com>
 Mark Peter Fejes <fejes.mark@gmail.com>
 Ryan Florence <rpflorence@gmail.com>
 MichaelQQ <mingsian.tu@vpon.com>
 Anders D. Johnson <anders.d.johnson.developer@gmail.com>
 Benjamin Fernandes <lotharsee@gmail.com>
 Simon Kurtz <simonkurtz@gmail.com>
 David Goss <david@davidgoss.co.uk>
 Luis Gustavo Pereira <lgp1985@yahoo.com.br>
 Amos Wenger <fasterthanlime@users.noreply.github.com>
 Samuel Marks <samuelmarks@gmail.com>
 Victor Travieso <victor@grabcad.com>
 legodude17 <legodude17@users.noreply.github.com>
 Joshua Chaitin-Pollak <jbcpollak@users.noreply.github.com>
 Brendan Warkentin <faazshift@gmail.com>
 Scott Santucci <ScottFreeCode@users.noreply.github.com>
 Xavier Cambar <xcambar@gmail.com>
 Vikram <nrvikram19@gmail.com>
 Igor Nadj <igor.nadj@shinesolutions.com>
 Tong Li <supertong@users.noreply.github.com>
 tripu <t@tripu.info>
 Carsten Brandt <mail@cebe.cc>
 Marcin Szczepanski <marcin@imagichine.com.au>
 Josh Clow <josh@textio.com>
 Jakub Holy <jakubholy@jakubholy.net>
--- a/deps/npm/CHANGELOG.md
+++ b/deps/npm/CHANGELOG.md
@ -1,3 +1,402 @@
 ## v5.5.1 (2017-10-04):
 A very quick, record time, patch release, of a bug fix to a (sigh) last minute bug fix.
 * [`e628e058b`](https://github.com/npm/npm/commit/e628e058b)
  Fix login to properly recognize OTP request and store bearer tokens.
  ([@Rebecca Turner](https://github.com/Rebecca Turner))
 ## v5.5.0 (2017-10-04):
 Hey y'all, this is a big new feature release!  We've got some security
 related goodies plus a some quality-of-life improvements for anyone who uses
 the public registry (so, virtually everyone).
 The changes largely came together in one piece, so I'm just gonna leave the commit line here:
 * [`f6ebf5e8b`](https://github.com/npm/npm/commit/f6ebf5e8bd6a212c7661e248c62c423f2b54d978)
  [`f97ad6a38`](https://github.com/npm/npm/commit/f97ad6a38412581d059108ea29be470acb4fa510)
  [`f644018e6`](https://github.com/npm/npm/commit/f644018e6ef1ff7523c6ec60ae55a24e87a9d9ae)
  [`8af91528c`](https://github.com/npm/npm/commit/8af91528ce6277cd3a8c7ca8c8102671baf10d2f)
  [`346a34260`](https://github.com/npm/npm/commit/346a34260b5fba7de62717135f3e083cc4820853)
  Two factor authentication, profile editing and token management.
  ([@iarna](https://github.com/iarna))
 ### TWO FACTOR AUTHENTICATION
 You can now enable two-factor authentication for your npm account.  You can
 even do it from the CLI.  In fact, you have to, for the time being:
 ```
 npm profile enable-tfa
 ```
 With the default two-factor authentication mode you'll be prompted to enter
 a one-time password when logging in, when publishing and when modifying access rights to
 your modules.
 ### TOKEN MANAGEMENT
 You can now create, list and delete authentication tokens from the comfort
 of the command line.  Authentication tokens created this way can have NEW
 restrictions placed on them.  For instance, you can create a `read-only`
 token to give to your CI.  It will be able to download your private modules
 but it won't be able to publish or modify modules.  You can also create
 tokens that can only be used from certain network addresses.  This way you
 can lock down access to your corporate VPN or other trusted machines.
 Deleting tokens isn't new, you could [do it via the
 website](https://www.npmjs.com/settings/tokens) but now you can do it via
 the CLI as well.
 ### CHANGE YOUR PASSWORD, SET YOUR EMAIL
 You can finally change your password from the CLI with `npm profile set
 password`!  You can also update your email address with `npm profile set
 email <address>`. If you change your email address we'll send you a new
 verification email so you verify that its yours.
 ### AND EVERYTHING ELSE ON YOUR PROFILE
 You can also update all of the other attributes of your profile that
 previously you could only update via the website: `fullname`, `homepage`,
 `freenode`, `twitter` and `github`.
 ### AVAILABLE STAND ALONE
 All of these features were implemented in a stand alone library, so if you
 have use for them in your own project you can find them in
 [npm-profile](https://www.npmjs.com/package/npm-profile) on the registry.
 There's also a little mini-cli written just for it at
 [npm-profile-cli](https://www.npmjs.com/package/npm-profile-cli).  You might
 also be interested in the [API
 documentation](https://github.com/npm/registry/tree/master/docs) for these
 new features: [user profile editing](https://github.com/npm/registry/blob/master/docs/user/profile.md) and
 [authentication](https://github.com/npm/registry/blob/master/docs/user/authentication.md).
 ### BUG FIXES
 * [`5ee55dc71`](https://github.com/npm/npm/commit/5ee55dc71b8b74b8418c3d5ec17483a07b3b6777)
  install.sh: Drop support for upgrading from npm@1 as npm@5 can't run on
  any Node.js version that ships npm@1. This fixes an issue some folks were seeing when trying
  to upgrade using `curl | http://npmjs.com/install.sh`.
  ([@iarna](https://github.com/iarna))
 * [`5cad1699a`](https://github.com/npm/npm/commit/5cad1699a7a0fc85ac7f77a95087a9647f75e344)
  `npm-lifecycle@1.0.3` Fix a bug where when more than one lifecycle script
  got queued to run, npm would crash.
  ([@zkat](https://github.com/zkat))
 * [`cd256cbb2`](https://github.com/npm/npm/commit/cd256cbb2f97fcbcb82237e94b66eac80e493626)
  `npm-packlist@1.1.9` Fix a bug where test directories would always be
  excluded from published modules.
  ([@isaacs](https://github.com/isaacs))
 * [`2a11f0215`](https://github.com/npm/npm/commit/2a11f021561acb1eb1ad4ad45ad955793b1eb4af)
  Fix formatting of unsupported version warning
  ([@iarna](https://github.com/iarna))
 ### DEPENDENCY UPDATES
 * [`6d2a285a5`](https://github.com/npm/npm/commit/6d2a285a58655f10834f64d38449eb1f3c8b6c47)
  `npm-registry-client@8.5.0`
 * [`69e64e27b`](https://github.com/npm/npm/commit/69e64e27bf58efd0b76b3cf6e8182c77f8cc452f)
  `request@2.83.0`
 * [`34e0f4209`](https://github.com/npm/npm/commit/34e0f42090f6153eb5462f742e402813e4da56c8)
  `abbrev@1.1.1`
 * [`10d31739d`](https://github.com/npm/npm/commit/10d31739d39765f1f0249f688bd934ffad92f872)
  `aproba@1.2.0`
 * [`2b02e86c0`](https://github.com/npm/npm/commit/2b02e86c06cf2a5fe7146404f5bfd27f190ee4f4)
  `meant@1.0.1`
 * [`b81fff808`](https://github.com/npm/npm/commit/b81fff808ee269361d3dcf38c1b6019f1708ae02)
  `rimraf@2.6.2`:
  Fixes a long standing bug in rimraf's attempts to work around Windows limitations
  where it owns a file and can change its perms but can't remove it without
  first changing its perms. This _may_ be an improvement for Windows users of npm under
  some circumstances.
  ([@isaacs](https://github.com/isaacs))
 ## v5.4.2 (2017-09-14):
 This is a small bug fix release wrapping up most of the issues introduced with 5.4.0.
 ### Bugs
 * [`0b28ac72d`](https://github.com/npm/npm/commit/0b28ac72d29132e9b761717aba20506854465865)
  [#18458](https://github.com/npm/npm/pull/18458)
  Fix a bug on Windows where rolling back of failed optional dependencies would fail.
  ([@marcins](https://github.com/marcins))
 * [`3a1b29991`](https://github.com/npm/npm/commit/3a1b299913ce94fdf25ed3ae5c88fe6699b04e24)
  `write-file-atomic@2.1.0` Revert update of `write-file-atomic`. There were changes made to it
  that were resulting in EACCES errors for many users.
  ([@iarna](https://github.com/iarna))
 * [`cd8687e12`](https://github.com/npm/npm/commit/cd8687e1257f59a253436d69e8d79a29c85d00c8)
  Fix a bug where if npm decided it needed to move a module during an upgrade it would strip
  out much of the `package.json`. This would result in broken trees after package updates.
 * [`5bd0244ee`](https://github.com/npm/npm/commit/5bd0244eec347ce435e88ff12148c35da7c69efe)
  [#18385](https://github.com/npm/npm/pull/18385)
  Fix `npm outdated` when run on non-registry dependencies.
  ([@joshclow](https://github.com/joshclow))
  ([@iarna](https://github.com/iarna))
 ### Ux
 * [`339f17b1e`](https://github.com/npm/npm/commit/339f17b1e6816eccff7df97875db33917eccdd13)
  Report unsupported node versions with greater granularity.
  ([@iarna](https://github.com/iarna))
 ### Docs
 * [`b2ab6f43b`](https://github.com/npm/npm/commit/b2ab6f43b8ae645134238acd8dd3083e5ba8846e)
  [#18397](https://github.com/npm/npm/pull/18397)
  Document that the default loglevel with `npm@5` is `notice`.
  ([@KenanY](https://github.com/KenanY))
 * [`e5aedcd82`](https://github.com/npm/npm/commit/e5aedcd82af81fa9e222f9210f6f890c72a18dd3)
  [#18372](https://github.com/npm/npm/pull/18372)
  In npm-config documentation, note that env vars use \_ in place of -.
  ([@jakubholynet](https://github.com/jakubholynet))
 ## v5.4.1 (2017-09-06):
 This is a very small bug fix release to fix a problem where permissions on
 installed binaries were being set incorrectly.
 * [`767ff6eee`](https://github.com/npm/npm/commit/767ff6eee7fa3a0f42ad677dedc0ec1f0dc15e7c)
  [zkat/pacote#117](https://github.com/zkat/pacote/pull/117)
  [#18324](https://github.com/npm/npm/issues/18324)
  `pacote@6.0.2`
  ([@zkat](https://github.com/zkat))
 ## v5.4.0 (2017-08-22):
 Here's another ~~small~~ big release, with a ~~handful~~ bunch of fixes and
 a couple of ~~small~~ new features! This release has been incubating rather
 longer than usual and it's grown quite a bit in that time. I'm also excited
 to say that it has contributions from **27** different folks, which is a new
 record for us. Our previous record was 5.1.0 at 21. Before that the record
 had been held by 1.3.16 since _December of 2013_.
 ![chart of contributor counts by version, showing an increasing rate over time and spikes mid in the 1.x series and later at 5.x](https://pbs.twimg.com/media/DH38rbZUwAAf9hS.jpg)
 If you can't get enough of the bleeding edge, I encourage you to check out
 our canary release of npm. Get it with `npm install -g npmc`. It's going to
 be seeing some exciting stuff in the next couple of weeks, starting with a
 rewriten `npm dedupe`, but moving on to… well, you'll just have to wait and
 find out.
 ### PERFORMANCE
 * [`d080379f6`](https://github.com/npm/npm/commit/d080379f620c716afa2c1d2e2ffc0a1ac3459194)
  `pacote@6.0.1` Updates extract to use tar@4, which is much faster than the
  older tar@2. It reduces install times by as much as 10%.
  ([@zkat](https://github.com/zkat))
 * [`4cd6a1774`](https://github.com/npm/npm/commit/4cd6a1774f774506323cae5685c9ca9a10deab63)
  [`0195c0a8c`](https://github.com/npm/npm/commit/0195c0a8cdf816834c2f737372194ddc576c451d)
  [#16804](https://github.com/npm/npm/pull/16804)
  `tar@4.0.1` Update publish to use tar@4. tar@4 brings many advantages
  over tar@2: It's faster, better tested and easier to work with.  It also
  produces exactly the same byte-for-byte output when producing tarballs
  from the same set of files.  This will have some nice carry on effects for
  things like caching builds from git.  And finally, last but certainly not
  least, upgrading to it also let's us finally eliminate `fstream`—if
  you know what that is you'll know why we're so relieved.
  ([@isaacs](https://github.com/isaacs))
 ### FEATURES
 * [`1ac470dd2`](https://github.com/npm/npm/commit/1ac470dd283cc7758dc37721dd6331d5b316dc99)
  [#10382](https://github.com/npm/npm/pull/10382)
  If you make a typo when writing a command now, npm will print a brief "did you
  mean..." message with some possible alternatives to what you meant.
  ([@watilde](https://github.com/watilde))
 * [`20c46228d`](https://github.com/npm/npm/commit/20c46228d8f9243910f8c343f4830d52455d754e)
  [#12356](https://github.com/npm/npm/pull/12356)
  When running lifecycle scripts, `INIT_CWD` will now contain the original
  working directory that npm was executed from. Remember that you can use `npm
  run-script` even if you're not inside your package root directory!
  ([@MichaelQQ](https://github.com/MichaelQQ))
 * [`be91e1726`](https://github.com/npm/npm/commit/be91e1726e9c21c4532723e4f413b73a93dd53d1)
  [`4e7c41f4a`](https://github.com/npm/npm/commit/4e7c41f4a29744a9976cc22c77eee9d44172f21e)
  `libnpx@9.6.0`: Fixes a number of issues on Windows and adds support for
  several more languages: Korean, Norwegian (bokmål and nynorsk), Ukrainian,
  Serbian, Bahasa Indonesia, Polish, Dutch and Arabic.
  ([@zkat](https://github.com/zkat))
 * [`2dec601c6`](https://github.com/npm/npm/commit/2dec601c6d5a576751d50efbcf76eaef4deff31e)
  [#17142](https://github.com/npm/npm/pull/17142)
  Add the new `commit-hooks` option to `npm version` so that you can disable commit
  hooks when committing the version bump.
  ([@faazshift](https://github.com/faazshift))
 * [`bde151902`](https://github.com/npm/npm/commit/bde15190230b5c62dbd98095311eab71f6b52321)
  [#14461](https://github.com/npm/npm/pull/14461)
  Make output from `npm ping` clear as to its success or failure.
  ([@legodude17](https://github.com/legodude17))
 ### BUGFIXES
 * [`b6d5549d2`](https://github.com/npm/npm/commit/b6d5549d2c2d38dd0e4319c56b69ad137f0d50cd)
  [#17844](https://github.com/npm/npm/pull/17844)
  Make package-lock.json sorting locale-agnostic. Previously, sorting would vary
  by locale, due to using `localeCompare` for key sorting.  This'll give you
  a little package-lock.json churn as it reshuffles things, sorry!
  ([@LotharSee](https://github.com/LotharSee))
 * [`44b98b9dd`](https://github.com/npm/npm/commit/44b98b9ddcfcccf68967fdf106fca52bf0c3da4b)
  [#17919](https://github.com/npm/npm/pull/17919)
  Fix a crash where `npm prune --production` would fail while removing `.bin`.
  ([@fasterthanlime](https://github.com/fasterthanlime))
 * [`c3d1d3ba8`](https://github.com/npm/npm/commit/c3d1d3ba82aa41dfb2bd135e6cdc59f8d33cd9fb)
  [#17816](https://github.com/npm/npm/pull/17816)
  Fail more smoothly when attempting to install an invalid package name.
  ([@SamuelMarks](https://github.com/SamuelMarks))
 * [`55ac2fca8`](https://github.com/npm/npm/commit/55ac2fca81bf08338302dc7dc2070494e71add5c)
  [#12784](https://github.com/npm/npm/pull/12784)
  Guard against stack overflows when marking packages as failed.
  ([@vtravieso](https://github.com/vtravieso))
 * [`597cc0e4b`](https://github.com/npm/npm/commit/597cc0e4b5e6ee719014e3171d4e966df42a275c)
  [#15087](https://github.com/npm/npm/pull/15087)
  Stop outputting progressbars or using color on dumb terminals.
  ([@iarna](https://github.com/iarna))
 * [`7a7710ba7`](https://github.com/npm/npm/commit/7a7710ba72e6f82414653c2e7e91fea9a1aba7e2)
  [#15088](https://github.com/npm/npm/pull/15088)
  Don't exclude modules that are both dev & prod when using `npm ls --production`.
  ([@iarna](https://github.com/iarna))
 * [`867df2b02`](https://github.com/npm/npm/commit/867df2b0214689822b87b51578e347f353be97e8)
  [#18164](https://github.com/npm/npm/pull/18164)
  Only do multiple procs on OSX for now. We've seen a handful of issues
  relating to this in Docker and in on Windows with antivirus.
  ([@zkat](https://github.com/zkat))
 * [`23540af7b`](https://github.com/npm/npm/commit/23540af7b0ec5f12bbdc1558745c8c4f0861042b)
  [#18117](https://github.com/npm/npm/pull/18117)
  Some package managers would write spaces to the \_from field in package.json's in the
  form of `name @spec`. This was causing npm to fail to interpret them. We now handle that
  correctly and doubly make sure we don't do that ourselves.
  ([@IgorNadj](https://github.com/IgorNadj))
 * [`0ef320cb4`](https://github.com/npm/npm/commit/0ef320cb40222693b7367b97c60ddffabc2d58c5)
  [#16634](https://github.com/npm/npm/pull/16634)
  Convert any bin script with a shbang a the start to Unix line-endings. (These sorts of scripts
  are not compatible with Windows line-endings even on Windows.)
  ([@ScottFreeCode](https://github.com/ScottFreeCode))
 * [`71191ca22`](https://github.com/npm/npm/commit/71191ca2227694355c49dfb187104f68df5126bd)
  [#16476](https://github.com/npm/npm/pull/16476)
  `npm-lifecycle@1.0.2` Running an install with `--ignore-scripts` was resulting in the
  the package object being mutated to have the lifecycle scripts removed from it and that
  in turn was being written out to disk, causing further problems. This fixes that:
  No more mutation, no more unexpected changes.
  ([@addaleax](https://github.com/addaleax))
 * [`459fa9d51`](https://github.com/npm/npm/commit/459fa9d51600904ee75ed6267b159367a1209793)
  [npm/read-package-json#74](https://github.com/npm/read-package-json/pull/74)
  [#17802](https://github.com/npm/npm/pull/17802)
  `read-package-json@2.0.1` Use unix-style slashes for generated bin
  entries, which lets them be cross platform even when produced on Windows.
  ([@iarna](https://github.com/iarna))
 * [`5ec72ab5b`](https://github.com/npm/npm/commit/5ec72ab5b27c5c83cee9ff568cf75a9479d4b83a)
  [#18229](https://github.com/npm/npm/pull/18229)
  Make install.sh find nodejs on debian.
  ([@cebe](https://github.com/cebe))
 ### DOCUMENTATION
 * [`b019680db`](https://github.com/npm/npm/commit/b019680db78ae0a6dff2289dbfe9f61fccbbe824)
  [#10846](https://github.com/npm/npm/pull/10846)
  Remind users that they have to install missing `peerDependencies` manually.
  ([@ryanflorence](https://github.com/ryanflorence))
 * [`3aee5986a`](https://github.com/npm/npm/commit/3aee5986a65add2f815b24541b9f4b69d7fb445f)
  [#17898](https://github.com/npm/npm/pull/17898)
  Minor punctuation fixes to the README.
  ([@AndersDJohnson](https://github.com/AndersDJohnson))
 * [`e0d0a7e1d`](https://github.com/npm/npm/commit/e0d0a7e1dda2c43822b17eb71f4d51900575cc61)
  [#17832](https://github.com/npm/npm/pull/17832)
  Fix grammar, format, and spelling in documentation for `run-script`.
  ([@simonua](https://github.com/simonua))
 * [`3fd6a5f2f`](https://github.com/npm/npm/commit/3fd6a5f2f8802a9768dba2ec32c593b5db5a878d)
  [#17897](https://github.com/npm/npm/pull/17897)
  Add more info about using `files` with `npm pack`/`npm publish`.
  ([@davidjgoss](https://github.com/davidjgoss))
 * [`f00cdc6eb`](https://github.com/npm/npm/commit/f00cdc6eb90a0735bc3c516720de0b1428c79c31)
  [#17785](https://github.com/npm/npm/pull/17785)
  Add a note about filenames for certificates on Windows, which use a different
  extension and file type.
  ([@lgp1985](https://github.com/lgp1985))
 * [`0cea6f974`](https://github.com/npm/npm/commit/0cea6f9741243b1937abfa300c2a111d9ed79143)
  [#18022](https://github.com/npm/npm/pull/18022)
  Clarify usage for the `files` field in `package.json`.
  ([@xcambar](https://github.com/xcambar))
 * [`a0fdd1571`](https://github.com/npm/npm/commit/a0fdd15710971234cbc57086cd1a4dc037a39471)
  [#15234](https://github.com/npm/npm/pull/15234)
  Clarify the behavior of the `files` array in the package-json docs.
  ([@jbcpollak](https://github.com/jbcpollak))
 * [`cecd6aa5d`](https://github.com/npm/npm/commit/cecd6aa5d4dd04af765b26b749c1cd032f7eb913)
  [#18137](https://github.com/npm/npm/pull/18137)
  Clarify interaction between npmignore and files in package.json.
  ([@supertong](https://github.com/supertong))
 * [`6b8972039`](https://github.com/npm/npm/commit/6b89720396767961001e727fc985671ce88b901b)
  [#18044](https://github.com/npm/npm/pull/18044)
  Corrected the typo in package-locks docs.
  ([@vikramnr](https://github.com/vikramnr))
 * [`6e012924f`](https://github.com/npm/npm/commit/6e012924f99c475bc3637c86ab6a113875405fc7)
  [#17667](https://github.com/npm/npm/pull/17667)
  Fix description of package.json in npm-scripts docs.
  ([@tripu](https://github.com/tripu))
 ### POSSIBLY INTERESTING DEPENDENCY UPDATES
 * [`48d84171a`](https://github.com/npm/npm/commit/48d84171a302fde2510b3f31e4a004c5a4d39c73)
  [`f60b05d63`](https://github.com/npm/npm/commit/f60b05d6307a7c46160ce98d6f3ccba89411c4ba)
  `semver@5.4.1` Perf improvements.
  ([@zkat](https://github.com/zkat))
 * [`f4650b5d4`](https://github.com/npm/npm/commit/f4650b5d4b2be2c04c229cc53aa930e260af9b4e)
  `write-file-atomic@2.3.0`:
  Serialize writes to the same file so that results are deterministic.
  Cleanup tempfiles when process is interrupted or killed.
  ([@ferm10n](https://github.com/ferm10n))
  ([@iarna](https://github.com/iarna))
 ### CHORES
 * [`96d78df98`](https://github.com/npm/npm/commit/96d78df9843187bc53be2c93913e8567003ccb73)
  [`80e2f4960`](https://github.com/npm/npm/commit/80e2f4960691bc5dbd8320002e4d9143784b9ce9)
  [`4f49f687b`](https://github.com/npm/npm/commit/4f49f687bbd54b6a0e406936ae35593d8e971e1e)
  [`07d2296b1`](https://github.com/npm/npm/commit/07d2296b10e3d8d6f079eba3a61f0258501d7161)
  [`a267ab430`](https://github.com/npm/npm/commit/a267ab4309883012a9d55934533c5915e9842277)
  [#18176](https://github.com/npm/npm/pull/18176)
  [#18025](https://github.com/npm/npm/pull/18025)
  Move the lifecycle code out of npm into a separate library,
  [`npm-lifecycle`](https://github.com/npm/lifecycle). Shh, I didn't tell you this, but this
  portends to some pretty cool stuff to come very soon now.
  ([@mikesherov](https://github.com/mikesherov))
 * [`0933c7eaf`](https://github.com/npm/npm/commit/0933c7eaf9cfcdf56471fe4e71c403e2016973da)
  [#18025](https://github.com/npm/npm/pull/18025)
  Force Travis to use Precise instead of Trusty.  We have issues with our
  couchdb setup and Trusty.  =/
  ([@mikesherov](https://github.com/mikesherov))
 * [`afb086230`](https://github.com/npm/npm/commit/afb086230223f3c4fcddee4e958d18fce5db0ff9)
  [#18138](https://github.com/npm/npm/pull/18138)
  Fix typos in files-and-ignores test.
  ([@supertong](https://github.com/supertong))
 * [`3e6d11cde`](https://github.com/npm/npm/commit/3e6d11cde096b4ee7b07e7569b37186aa2115b1a)
  [#18175](https://github.com/npm/npm/pull/18175)
  Update dependencies to eliminate transitive dependencies with the WTFPL license, which
  some more serious corporate lawyery types aren't super comfortable with.
  ([@zkat](https://github.com/zkat))
 * [`ee4c9bd8a`](https://github.com/npm/npm/commit/ee4c9bd8ae574a0d6b24725ba6c7b718d8aaad8d)
  [#16474](https://github.com/npm/npm/pull/16474)
  The tests in `test/tap/lifecycle-signal.js`, as well as the features
  they are testing, are partially broken. This moves them from
  being skipped in CI to being disabled only for certain platforms.
  In particular, because `npm` spawns its lifecycle scripts in a
  shell, signals are not necessarily forwarded by the shell and
  won’t cause scripts to exit; also, shells may report the signal
  they receive using their exit status, rather than terminating
  themselves with a signal.
  ([@addaleax](https://github.com/addaleax))
 * [`9462e5d9c`](https://github.com/npm/npm/commit/9462e5d9cfbaa50218de6d0a630d6552e72ad0a8)
  [#16547](https://github.com/npm/npm/pull/16547)
  Remove unused file: bin/read-package-json.js
  ([@metux](https://github.com/metux))
 * [`0756d687d`](https://github.com/npm/npm/commit/0756d687d4ccfcd4a7fd83db0065eceb9261befb)
  [#16550](https://github.com/npm/npm/pull/16550)
  The build tools for the documentation need to be built/installed
  before the documents, even with parallel builds.
  Make has a simple mechanism which was made exactly for that:
  target dependencies.
  ([@metux](https://github.com/metux))
 ## v5.3.0 (2017-07-12):
 As mentioned before, we're continuing to do relatively rapid, smaller releases
--- a/deps/npm/Makefile
+++ b/deps/npm/Makefile
@ -88,12 +88,16 @@ doc-clean:
    html/doc \
    man
 ## build-time tools for the documentation
 build-doc-tools := node_modules/.bin/marked \
                   node_modules/.bin/marked-man
 # use `npm install marked-man` for this to work.
-man/man1/npm-README.1: README.md scripts/doc-build.sh package.json
+man/man1/npm-README.1: README.md scripts/doc-build.sh package.json $(build-doc-tools)
 	@[ -d man/man1 ] || mkdir -p man/man1
 	scripts/doc-build.sh $< $@
-man/man1/%.1: doc/cli/%.md scripts/doc-build.sh package.json
+man/man1/%.1: doc/cli/%.md scripts/doc-build.sh package.json $(build-doc-tools)
 	@[ -d man/man1 ] || mkdir -p man/man1
 	scripts/doc-build.sh $< $@
@ -106,26 +110,26 @@ man/man5/npm-json.5: man/man5/package.json.5
 man/man5/npm-global.5: man/man5/npm-folders.5
 	cp $< $@
-man/man5/%.5: doc/files/%.md scripts/doc-build.sh package.json
+man/man5/%.5: doc/files/%.md scripts/doc-build.sh package.json $(build-doc-tools)
 	@[ -d man/man5 ] || mkdir -p man/man5
 	scripts/doc-build.sh $< $@
-doc/misc/npm-index.md: scripts/index-build.js package.json
+doc/misc/npm-index.md: scripts/index-build.js package.json $(build-doc-tools)
 	node scripts/index-build.js > $@
-html/doc/index.html: doc/misc/npm-index.md $(html_docdeps)
+html/doc/index.html: doc/misc/npm-index.md $(html_docdeps) $(build-doc-tools)
 	@[ -d html/doc ] || mkdir -p html/doc
 	scripts/doc-build.sh $< $@
-man/man7/%.7: doc/misc/%.md scripts/doc-build.sh package.json
+man/man7/%.7: doc/misc/%.md scripts/doc-build.sh package.json $(build-doc-tools)
 	@[ -d man/man7 ] || mkdir -p man/man7
 	scripts/doc-build.sh $< $@
-html/doc/README.html: README.md $(html_docdeps)
+html/doc/README.html: README.md $(html_docdeps) $(build-doc-tools)
 	@[ -d html/doc ] || mkdir -p html/doc
 	scripts/doc-build.sh $< $@
-html/doc/cli/%.html: doc/cli/%.md $(html_docdeps)
+html/doc/cli/%.html: doc/cli/%.md $(html_docdeps) $(build-doc-tools)
 	@[ -d html/doc/cli ] || mkdir -p html/doc/cli
 	scripts/doc-build.sh $< $@
@ -135,11 +139,11 @@ html/doc/files/npm-json.html: html/doc/files/package.json.html
 html/doc/files/npm-global.html: html/doc/files/npm-folders.html
 	cp $< $@
-html/doc/files/%.html: doc/files/%.md $(html_docdeps)
+html/doc/files/%.html: doc/files/%.md $(html_docdeps) $(build-doc-tools)
 	@[ -d html/doc/files ] || mkdir -p html/doc/files
 	scripts/doc-build.sh $< $@
-html/doc/misc/%.html: doc/misc/%.md $(html_docdeps)
+html/doc/misc/%.html: doc/misc/%.md $(html_docdeps) $(build-doc-tools)
 	@[ -d html/doc/misc ] || mkdir -p html/doc/misc
 	scripts/doc-build.sh $< $@
--- a/deps/npm/README.md
+++ b/deps/npm/README.md
@ -141,12 +141,12 @@ you have chosen.
 ## More Docs
-Check out the [docs](https://docs.npmjs.com/),
+Check out the [docs](https://docs.npmjs.com/).
 You can use the `npm help` command to read any of them.
 If you're a developer, and you want to use npm to publish your program,
-you should [read this](https://docs.npmjs.com/misc/developers)
+you should [read this](https://docs.npmjs.com/misc/developers).
 ## BUGS
--- a/deps/npm/bin/read-package-json.js
+++ b/deps/npm/bin/read-package-json.js
@ -1,24 +0,0 @@
 var argv = process.argv
 if (argv.length < 3) {
  console.error('Usage: read-package.json <file> [<fields> ...]')
  process.exit(1)
 }
 var file = argv[2]
 var readJson = require('read-package-json')
 readJson(file, function (er, data) {
  if (er) throw er
  if (argv.length === 3) {
    console.log(data)
  } else {
    argv.slice(3).forEach(function (field) {
      field = field.split('.')
      var val = data
      field.forEach(function (f) {
        val = val[f]
      })
      console.log(val)
    })
  }
 })
--- a/deps/npm/doc/cli/npm-access.md
+++ b/deps/npm/doc/cli/npm-access.md
@ -60,6 +60,9 @@ You must have privileges to set the access of a package:
 * You have been given read-write privileges for a package, either as a member
  of a team or directly as an owner.
 If you have two-factor authentication enabled then you'll have to pass in an
 otp with `--otp` when making access changes.
 If your account is not paid, then attempts to publish scoped packages will fail
 with an HTTP 402 status code (logically enough), unless you use
 `--access=public`.
--- a/deps/npm/doc/cli/npm-config.md
+++ b/deps/npm/doc/cli/npm-config.md
@ -6,7 +6,7 @@ npm-config(1) -- Manage the npm configuration files
    npm config set <key> <value> [-g|--global]
    npm config get <key>
    npm config delete <key>
-    npm config list [-l]
+    npm config list [-l] [--json]
    npm config edit
    npm get <key>
    npm set <key> <value> [-g|--global]
@ -48,7 +48,8 @@ Echo the config value to stdout.
    npm config list
-Show all the config settings. Use `-l` to also show defaults.
+Show all the config settings. Use `-l` to also show defaults. Use `--json`
 to show the settings in json format.
 ### delete
--- a/deps/npm/doc/cli/npm-dist-tag.md
+++ b/deps/npm/doc/cli/npm-dist-tag.md
@ -15,7 +15,9 @@ Add, remove, and enumerate distribution tags on a package:
 * add:
  Tags the specified version of the package with the specified tag, or the
-  `--tag` config if not specified.
+  `--tag` config if not specified. The tag you're adding is `latest` and you
  have two-factor authentication on auth-and-writes then you'll need to include
  an otp on the command line with `--otp`.
 * rm:
  Clear a tag that is no longer in use from the package.
--- a/deps/npm/doc/cli/npm-owner.md
+++ b/deps/npm/doc/cli/npm-owner.md
@ -27,6 +27,10 @@ Note that there is only one level of access.  Either you can modify a package,
 or you can't.  Future versions may contain more fine-grained access levels, but
 that is not implemented at this time.
 If you have two-factor authentication enabled with `auth-and-writes` then
 you'll need to include an otp on the command line when changing ownership
 with `--otp`.
 ## SEE ALSO
 * npm-publish(1)
--- a/deps/npm/doc/cli/npm-ping.md
+++ b/deps/npm/doc/cli/npm-ping.md
@ -8,6 +8,14 @@ npm-ping(1) -- Ping npm registry
 ## DESCRIPTION
 Ping the configured or given npm registry and verify authentication.
 If it works it will output something like:
 ```
 Ping success: {*Details about registry*}
 ```
 otherwise you will get:
 ```
 Ping error: {*Detail about error}
 ```
 ## SEE ALSO
--- a/deps/npm/doc/cli/npm-profile.md
+++ b/deps/npm/doc/cli/npm-profile.md
@ -0,0 +1,74 @@
 npm-profile(1) -- Change settings on your registry profile
 ==========================================================
 ## SYNOPSIS
    npm profile get [--json|--parseable] [<property>]
    npm profile set [--json|--parseable] <property> <value>
    npm profile set password
    npm profile enable-2fa [auth-and-writes|auth-only]
    npm profile disable-2fa
 ## DESCRIPTION
 Change your profile information on the registry.  This not be available if
 you're using a non-npmjs registry.
 * `npm profile get [<property>]`:
  Display all of the properties of your profile, or one or more specific
  properties.  It looks like:
 ```
 +-----------------+---------------------------+
 | name            | example                   |
 +-----------------+---------------------------+
 | email           | me@example.com (verified) |
 +-----------------+---------------------------+
 | two factor auth | auth-and-writes           |
 +-----------------+---------------------------+
 | fullname        | Example User              |
 +-----------------+---------------------------+
 | homepage        |                           |
 +-----------------+---------------------------+
 | freenode        |                           |
 +-----------------+---------------------------+
 | twitter         |                           |
 +-----------------+---------------------------+
 | github          |                           |
 +-----------------+---------------------------+
 | created         | 2015-02-26T01:38:35.892Z  |
 +-----------------+---------------------------+
 | updated         | 2017-10-02T21:29:45.922Z  |
 +-----------------+---------------------------+
 ```
 * `npm profile set <property> <value>`:
  Set the value of a profile property. You can set the following properties this way:
    email, fullname, homepage, freenode, twitter, github
 * `npm profile set password`:
  Change your password.  This is interactive, you'll be prompted for your
  current password and a new password.  You'll also be prompted for an OTP
  if you have two-factor authentication enabled.
 * `npm profile enable-2fa [auth-and-writes|auth-only]`:
  Enables two-factor authentication. Defaults to `auth-and-writes` mode. Modes are:
  * `auth-only`: Require an OTP when logging in or making changes to your
    account's authentication.  The OTP will be required on both the website
    and the command line.
  * `auth-and-writes`: Requires an OTP at all the times `auth-only` does, and also requires one when
    publishing a module, setting the `latest` dist-tag, or changing access
    via `npm access` and `npm owner`.
 * `npm profile disable-2fa`:
  Disables two-factor authentication.
 ## DETAILS
 All of the `npm profile` subcommands accept `--json` and `--parseable` and
 will tailor their output based on those.  Some of these commands may not be
 available on non npmjs.com registries.
 ## SEE ALSO
 * npm-config(7)
--- a/deps/npm/doc/cli/npm-publish.md
+++ b/deps/npm/doc/cli/npm-publish.md
@ -4,7 +4,7 @@ npm-publish(1) -- Publish a package
 ## SYNOPSIS
-    npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>]
+    npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--otp otpcode]
    Publishes '.' if no argument supplied
    Sets tag 'latest' if no --tag specified
@ -41,6 +41,11 @@ specifying a different default registry or using a `npm-scope(7)` in the name
  If you don't have a paid account, you must publish with `--access public`
  to publish scoped packages.
 * `[--otp <otpcode>]`
  If you have two-factor authentication enabled in `auth-and-writes` mode
  then you can provide a code from your authenticator with this. If you
  don't include this and you're running from a TTY then you'll be prompted.
 Fails if the package name and version combination already exists in
 the specified registry.
@ -65,3 +70,4 @@ packs them into a tarball to be uploaded to the registry.
 * npm-deprecate(1)
 * npm-dist-tag(1)
 * npm-pack(1)
 * npm-profile(1)
--- a/deps/npm/doc/cli/npm-run-script.md
+++ b/deps/npm/doc/cli/npm-run-script.md
@ -27,7 +27,7 @@ and not to any pre or post script.
 The `env` script is a special built-in command that can be used to list
 environment variables that will be available to the script at runtime. If an
-"env" command is defined in your package it will take precedence over the
+"env" command is defined in your package, it will take precedence over the
 built-in.
 In addition to the shell's pre-existing `PATH`, `npm run` adds
@ -38,7 +38,17 @@ you should write:
    "scripts": {"test": "tap test/\*.js"}
-instead of `"scripts": {"test": "node_modules/.bin/tap test/\*.js"}` to run your tests.
+instead of
 	"scripts": {"test": "node_modules/.bin/tap test/\*.js"}
 to run your tests.
 Scripts are run from the root of the module, regardless of what your current
 working directory is when you call `npm run`. If you want your script to
 use different behavior based on what subdirectory you're in, you can use the
 `INIT_CWD` environment variable, which holds the full path you were in when
 you ran `npm run`.
 `npm run` sets the `NODE` environment variable to the `node` executable with
 which `npm` is executed. Also, if the `--scripts-prepend-node-path` is passed,
--- a/deps/npm/doc/cli/npm-token.md
+++ b/deps/npm/doc/cli/npm-token.md
@ -0,0 +1,59 @@
 npm-token(1) -- Manage your authentication tokens
 =================================================
 ## SYNOPSIS
    npm token list [--json|--parseable]
    npm token create [--read-only] [--cidr=1.1.1.1/24,2.2.2.2/16]
    npm token delete <id|token>
 ## DESCRIPTION
 This list you list, create and delete authentication tokens.
 * `npm token list`:
  Shows a table of all active authentication tokens. You can request this as
  JSON with `--json` or tab-separated values with `--parseable`.
 ```
 +--------+---------+------------+----------+----------------+
 | id     | token   | created    | read-only | CIDR whitelist |
 +--------+---------+------------+----------+----------------+
 | 7f3134 | 1fa9ba… | 2017-10-02 | yes      |                |
 +--------+---------+------------+----------+----------------+
 | c03241 | af7aef… | 2017-10-02 | no       | 192.168.0.1/24 |
 +--------+---------+------------+----------+----------------+
 | e0cf92 | 3a436a… | 2017-10-02 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 63eb9d | 74ef35… | 2017-09-28 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 2daaa8 | cbad5f… | 2017-09-26 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 68c2fe | 127e51… | 2017-09-23 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 6334e1 | 1dadd1… | 2017-09-23 | no       |                |
 +--------+---------+------------+----------+----------------+
 ```
 * `npm token create [--read-only] [--cidr=<cidr-ranges>]`:
  Create a new authentication token. It can be `--read-only` or accept a list of
  [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) ranges to
  limit use of this token to. This will prompt you for your password, and, if you have
  two-factor authentication enabled, an otp.
 ```
 +----------------+--------------------------------------+
 | token          | a73c9572-f1b9-8983-983d-ba3ac3cc913d |
 +----------------+--------------------------------------+
 | cidr_whitelist |                                      |
 +----------------+--------------------------------------+
 | readonly       | false                                |
 +----------------+--------------------------------------+
 | created        | 2017-10-02T07:52:24.838Z             |
 +----------------+--------------------------------------+
 ```
 * `npm token delete <token|id>`:
  This removes an authentication token, making it immediately unusable. This can accept
  both complete tokens (as you get back from `npm token create` and will
  find in your `.npmrc`) and ids as seen in the `npm token list` output.
  This will NOT accept the truncated token found in `npm token list` output.
--- a/deps/npm/doc/cli/npm-version.md
+++ b/deps/npm/doc/cli/npm-version.md
@ -93,6 +93,13 @@ to the same value as the current version.
 Commit and tag the version change.
 ### commit-hooks
 * Default: true
 * Type: Boolean
 Run git commit hooks when committing the version change.
 ### sign-git-tag
 * Default: false
--- a/deps/npm/doc/files/npm-package-locks.md
+++ b/deps/npm/doc/files/npm-package-locks.md
@ -92,7 +92,7 @@ which will look something like this:
    }
 This file describes an *exact*, and more importantly *reproducible*
-`node_modules` tree. Once it's present, and future installation will base its
+`node_modules` tree. Once it's present, any future installation will base its
 work off this file, instead of recalculating dependency versions off
 package.json(5).
--- a/deps/npm/doc/files/package.json.md
+++ b/deps/npm/doc/files/package.json.md
@ -168,14 +168,23 @@ npm also sets a top-level "maintainers" field with your npm user info.
 ## files
-The "files" field is an array of files to include in your project.  If
+The optional "files" field is an array of file patterns that describes
-you name a folder in the array, then it will also include the files
+the entries to be included when your package is installed as a
-inside that folder. (Unless they would be ignored by another rule.)
+dependency. If the files array is omitted, everything except
 automatically-excluded files will be included in your publish. If you
 name a folder in the array, then it will also include the files inside
 that folder (unless they would be ignored by another rule in this
 section.).
-You can also provide a ".npmignore" file in the root of your package or
+You can also provide a `.npmignore` file in the root of your package or
-in subdirectories, which will keep files from being included, even
+in subdirectories, which will keep files from being included. At the
-if they would be picked up by the files array.  The `.npmignore` file
+root of your package it will not override the "files" field, but in
-works just like a `.gitignore`.
+subdirectories it will. The `.npmignore` file works just like a
 `.gitignore`. If there is a `.gitignore` file, and `.npmignore` is
 missing, `.gitignore`'s contents will be used instead.
 Files included with the "package.json#files" field _cannot_ be excluded
 through `.npmignore` or `.gitignore`.
 Certain files are always included, regardless of settings:
--- a/deps/npm/doc/misc/npm-config.md
+++ b/deps/npm/doc/misc/npm-config.md
@ -31,6 +31,9 @@ npm will set its own environment variables and Node will prefer
 those lowercase versions over any uppercase ones that you might set.
 For details see [this issue](https://github.com/npm/npm/issues/14528).
 Notice that you need to use underscores instead of dashes, so `--allow-same-version`
 would become `npm_config_allow_same_version=true`.
 ### npmrc Files
 The four relevant files are:
@ -184,7 +187,7 @@ The browser that is called by the `npm docs` command to open websites.
 * Type: String, Array or null
 The Certificate Authority signing certificate that is trusted for SSL
-connections to the registry. Values should be in PEM format with newlines
+connections to the registry. Values should be in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newlines
 replaced by the string "\n". For example:
    ca="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
@ -260,12 +263,19 @@ Number of ms to wait for cache lock files to expire.
 * Type: String
 A client certificate to pass when accessing the registry.  Values should be in
-PEM format with newlines replaced by the string "\n". For example:
+PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newlines replaced by the string "\n". For example:
    cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
 It is _not_ the path to a certificate file (and there is no "certfile" option).
 ### cidr
 * Default: `null`
 * Type: String, Array, null
 This is a list of CIDR address to be used when configuring limited access tokens with the `npm token create` command.
 ### color
 * Default: true
@ -389,6 +399,13 @@ the git binary.
 Tag the commit when using the `npm version` command.
 ### commit-hooks
 * Default: `true`
 * Type: Boolean
 Run git commit hooks when using the `npm version` command.
 ### global
 * Default: false
@ -576,15 +593,15 @@ to the npm registry.  Must be IPv4 in versions of Node prior to 0.12.
 ### loglevel
-* Default: "warn"
+* Default: "notice"
 * Type: String
-* Values: "silent", "error", "warn", "http", "info", "verbose", "silly"
+* Values: "silent", "error", "warn", "notice", "http", "timing", "info",
  "verbose", "silly"
 What level of logs to report.  On failure, *all* logs are written to
 `npm-debug.log` in the current working directory.
-Any logs of a higher level than the setting are shown.
+Any logs of a higher level than the setting are shown. The default is "notice".
 The default is "warn", which shows warn and error output.
 ### logstream
@ -689,6 +706,14 @@ Attempt to install packages in the `optionalDependencies` object.  Note
 that if these packages fail to install, the overall installation
 process is not aborted.
 ### otp
 * Default: null
 * Type: Number
 This is a one-time password from a two-factor authenticator.  It's needed
 when publishing or changing package permissions with `npm access`.
 ### package-lock
 * Default: true
@ -754,18 +779,6 @@ operations, if `process.stderr` is a TTY.
 Set to `false` to suppress the progress bar.
 ### proprietary-attribs
 * Default: true
 * Type: Boolean
 Whether or not to include proprietary extended attributes in the
 tarballs created by npm.
 Unless you are expecting to unpack package tarballs with something other
 than npm -- particularly a very outdated tar implementation -- leave
 this as true.
 ### proxy
 * Default: null
@ -775,6 +788,13 @@ A proxy to use for outgoing http requests. If the `HTTP_PROXY` or
 `http_proxy` environment variables are set, proxy settings will be
 honored by the underlying `request` library.
 ### read-only
 * Default: false
 * Type: Boolean
 This is used to mark a token as unable to publish when configuring limited access tokens with the `npm token create` command.
 ### rebuild-bundle
 * Default: true
--- a/deps/npm/doc/misc/npm-developers.md
+++ b/deps/npm/doc/misc/npm-developers.md
@ -140,6 +140,19 @@ The following paths and files are never ignored, so adding them to
 * `CHANGELOG` (and its variants)
 * `LICENSE` / `LICENCE`
 If, given the structure of your project, you find `.npmignore` to be a
 maintenance headache, you might instead try populating the `files`
 property of `package.json`, which is an array of file or directory names
 that should be included in your package. Sometimes a whitelist is easier
 to manage than a blacklist.
 ### Testing whether your `.npmignore` or `files` config works
 If you want to double check that your package will include only the files
 you intend it to when published, you can run the `npm pack` command locally
 which will generate a tarball in the working directory, the same way it
 does for publishing.
 ## Link Packages
 `npm link` is designed to install a development package and see the
--- a/deps/npm/doc/misc/npm-index.md
+++ b/deps/npm/doc/misc/npm-index.md
@ -129,6 +129,10 @@ Ping npm registry
 Display prefix
 ### npm-profile(1)
 Change settings on your registry profile
 ### npm-prune(1)
 Remove extraneous packages
@ -189,6 +193,10 @@ Manage organization teams and team memberships
 Test a package
 ### npm-token(1)
 Manage your authentication tokens
 ### npm-uninstall(1)
 Remove a package
--- a/deps/npm/doc/misc/npm-scripts.md
+++ b/deps/npm/doc/misc/npm-scripts.md
@ -3,7 +3,7 @@ npm-scripts(7) -- How npm handles the "scripts" field
 ## DESCRIPTION
-npm supports the "scripts" property of the package.json script, for the
+npm supports the "scripts" property of the package.json file, for the
 following scripts:
 * prepublish:
--- a/deps/npm/doc/misc/semver.md
+++ b/deps/npm/doc/misc/semver.md
@ -1,55 +1,65 @@
 semver(7) -- The semantic versioner for npm
 ===========================================
 ## Install
 ```bash
 npm install --save semver
 ````
 ## Usage
-    $ npm install semver
+As a node module:
    $ node
    var semver = require('semver')
-    semver.valid('1.2.3') // '1.2.3'
+```js
-    semver.valid('a.b.c') // null
+const semver = require('semver')
-    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.valid('1.2.3') // '1.2.3'
-    semver.gt('1.2.3', '9.8.7') // false
+semver.valid('a.b.c') // null
-    semver.lt('1.2.3', '9.8.7') // true
+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
 semver.lt('1.2.3', '9.8.7') // true
 ```
 As a command-line utility:
-    $ semver -h
+```
 $ semver -h
-    SemVer 5.1.0
+SemVer 5.3.0
-    A JavaScript implementation of the http://semver.org/ specification
+A JavaScript implementation of the http://semver.org/ specification
-    Copyright Isaac Z. Schlueter
+Copyright Isaac Z. Schlueter
-    Usage: semver [options] <version> [<version> [...]]
+Usage: semver [options] <version> [<version> [...]]
-    Prints valid versions sorted by SemVer precedence
+Prints valid versions sorted by SemVer precedence
-    Options:
+Options:
-    -r --range <range>
+-r --range <range>
-            Print versions that match the specified range.
+        Print versions that match the specified range.
-    -i --increment [<level>]
+-i --increment [<level>]
-            Increment a version by the specified level.  Level can
+        Increment a version by the specified level.  Level can
-            be one of: major, minor, patch, premajor, preminor,
+        be one of: major, minor, patch, premajor, preminor,
-            prepatch, or prerelease.  Default level is 'patch'.
+        prepatch, or prerelease.  Default level is 'patch'.
-            Only one version may be specified.
+        Only one version may be specified.
-    --preid <identifier>
+--preid <identifier>
-            Identifier to be used to prefix premajor, preminor,
+        Identifier to be used to prefix premajor, preminor,
-            prepatch or prerelease version increments.
+        prepatch or prerelease version increments.
-    -l --loose
+-l --loose
-            Interpret versions and ranges loosely
+        Interpret versions and ranges loosely
-    Program exits successfully if any valid version satisfies
+Program exits successfully if any valid version satisfies
-    all supplied ranges, and prints all satisfying versions.
+all supplied ranges, and prints all satisfying versions.
-    If no satisfying versions are found, then exits failure.
+If no satisfying versions are found, then exits failure.
-    Versions are printed in ascending order, so supplying
+Versions are printed in ascending order, so supplying
-    multiple versions to the utility will just sort them.
+multiple versions to the utility will just sort them.
 ```
 ## Versions
@ -126,20 +136,20 @@ The method `.inc` takes an additional `identifier` string argument that
 will append the value of the string as a prerelease identifier:
 ```javascript
-> semver.inc('1.2.3', 'prerelease', 'beta')
+semver.inc('1.2.3', 'prerelease', 'beta')
-'1.2.4-beta.0'
+// '1.2.4-beta.0'
 ```
 command-line example:
-```shell
+```bash
 $ semver 1.2.3 -i prerelease --preid beta
 1.2.4-beta.0
 ```
 Which then can be used to increment further:
-```shell
+```bash
 $ semver 1.2.4-beta.0 -i prerelease
 1.2.4-beta.1
 ```
@ -296,6 +306,8 @@ strings that they parse.
 * `major(v)`: Return the major version number.
 * `minor(v)`: Return the minor version number.
 * `patch(v)`: Return the patch version number.
 * `intersects(r1, r2, loose)`: Return true if the two supplied ranges
  or comparators intersect.
 ### Comparison
@ -319,6 +331,9 @@ strings that they parse.
  (`major`, `premajor`, `minor`, `preminor`, `patch`, `prepatch`, or `prerelease`),
  or null if the versions are the same.
 ### Comparators
 * `intersects(comparator)`: Return true if the comparators intersect
 ### Ranges
@ -337,6 +352,7 @@ strings that they parse.
  the bounds of the range in either the high or low direction.  The
  `hilo` argument must be either the string `'>'` or `'<'`.  (This is
  the function called by `gtr` and `ltr`.)
 * `intersects(range)`: Return true if any of the ranges comparators intersect
 Note that, since ranges may be non-contiguous, a version might not be
 greater than a range, less than a range, *or* satisfy a range!  For
--- a/deps/npm/html/doc/README.html
+++ b/deps/npm/html/doc/README.html
@ -94,10 +94,10 @@ must remove them yourself manually if you want them gone.  Note that
 this means that future npm installs will not remember the settings that
 you have chosen.</p>
 <h2 id="more-docs">More Docs</h2>
-<p>Check out the <a href="https://docs.npmjs.com/">docs</a>,</p>
+<p>Check out the <a href="https://docs.npmjs.com/">docs</a>.</p>
 <p>You can use the <code>npm help</code> command to read any of them.</p>
 <p>If you&#39;re a developer, and you want to use npm to publish your program,
-you should <a href="https://docs.npmjs.com/misc/developers">read this</a></p>
+you should <a href="https://docs.npmjs.com/misc/developers">read this</a>.</p>
 <h2 id="bugs">BUGS</h2>
 <p>When you find issues, please report them:</p>
 <ul>
@ -127,5 +127,5 @@ doubt tell you to put the output in a gist or email.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@5.3.0</p>
+<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-access.html
+++ b/deps/npm/html/doc/cli/npm-access.html
@ -61,6 +61,8 @@ public using <code>npm publish --access=public</code>, or set their access as pu
 <li>You have been given read-write privileges for a package, either as a member
 of a team or directly as an owner.</li>
 </ul>
 <p>If you have two-factor authentication enabled then you&#39;ll have to pass in an
 otp with <code>--otp</code> when making access changes.</p>
 <p>If your account is not paid, then attempts to publish scoped packages will fail
 with an HTTP 402 status code (logically enough), unless you use
 <code>--access=public</code>.</p>
@ -84,5 +86,5 @@ with an HTTP 402 status code (logically enough), unless you use
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-access &mdash; npm@5.3.0</p>
+<p id="footer">npm-access &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-adduser.html
+++ b/deps/npm/html/doc/cli/npm-adduser.html
@ -81,5 +81,5 @@ username/password entry in legacy npm.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-adduser &mdash; npm@5.3.0</p>
+<p id="footer">npm-adduser &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-bin.html
+++ b/deps/npm/html/doc/cli/npm-bin.html
@ -35,5 +35,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-bin &mdash; npm@5.3.0</p>
+<p id="footer">npm-bin &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-bugs.html
+++ b/deps/npm/html/doc/cli/npm-bugs.html
@ -55,5 +55,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-bugs &mdash; npm@5.3.0</p>
+<p id="footer">npm-bugs &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-build.html
+++ b/deps/npm/html/doc/cli/npm-build.html
@ -40,5 +40,5 @@ directly, run:</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-build &mdash; npm@5.3.0</p>
+<p id="footer">npm-build &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-bundle.html
+++ b/deps/npm/html/doc/cli/npm-bundle.html
@ -31,5 +31,5 @@ install packages into the local space.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-bundle &mdash; npm@5.3.0</p>
+<p id="footer">npm-bundle &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-cache.html
+++ b/deps/npm/html/doc/cli/npm-cache.html
@ -89,5 +89,5 @@ verify</code>.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-cache &mdash; npm@5.3.0</p>
+<p id="footer">npm-cache &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-completion.html
+++ b/deps/npm/html/doc/cli/npm-completion.html
@ -43,5 +43,5 @@ completions based on the arguments.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-completion &mdash; npm@5.3.0</p>
+<p id="footer">npm-completion &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-config.html
+++ b/deps/npm/html/doc/cli/npm-config.html
@ -14,7 +14,7 @@
 <pre><code>npm config set &lt;key&gt; &lt;value&gt; [-g|--global]
 npm config get &lt;key&gt;
 npm config delete &lt;key&gt;
-npm config list [-l]
+npm config list [-l] [--json]
 npm config edit
 npm get &lt;key&gt;
 npm set &lt;key&gt; &lt;value&gt; [-g|--global]
@ -39,7 +39,8 @@ of the user and global npmrc files.</p>
 </code></pre><p>Echo the config value to stdout.</p>
 <h3 id="list">list</h3>
 <pre><code>npm config list
-</code></pre><p>Show all the config settings. Use <code>-l</code> to also show defaults.</p>
+</code></pre><p>Show all the config settings. Use <code>-l</code> to also show defaults. Use <code>--json</code>
 to show the settings in json format.</p>
 <h3 id="delete">delete</h3>
 <pre><code>npm config delete key
 </code></pre><p>Deletes the key from all configuration files.</p>
@ -67,5 +68,5 @@ global config.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-config &mdash; npm@5.3.0</p>
+<p id="footer">npm-config &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-dedupe.html
+++ b/deps/npm/html/doc/cli/npm-dedupe.html
@ -61,5 +61,5 @@ result in new modules being installed.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-dedupe &mdash; npm@5.3.0</p>
+<p id="footer">npm-dedupe &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-deprecate.html
+++ b/deps/npm/html/doc/cli/npm-deprecate.html
@ -38,5 +38,5 @@ something like this:</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-deprecate &mdash; npm@5.3.0</p>
+<p id="footer">npm-deprecate &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-dist-tag.html
+++ b/deps/npm/html/doc/cli/npm-dist-tag.html
@ -21,7 +21,9 @@ aliases: dist-tags
 <ul>
 <li><p>add:
 Tags the specified version of the package with the specified tag, or the
-<code>--tag</code> config if not specified.</p>
+<code>--tag</code> config if not specified. The tag you&#39;re adding is <code>latest</code> and you
 have two-factor authentication on auth-and-writes then you&#39;ll need to include
 an otp on the command line with <code>--otp</code>.</p>
 </li>
 <li><p>rm:
 Clear a tag that is no longer in use from the package.</p>
@ -86,5 +88,5 @@ begin with a number or the letter <code>v</code>.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-dist-tag &mdash; npm@5.3.0</p>
+<p id="footer">npm-dist-tag &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-docs.html
+++ b/deps/npm/html/doc/cli/npm-docs.html
@ -56,5 +56,5 @@ the current folder and use the <code>name</code> property.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-docs &mdash; npm@5.3.0</p>
+<p id="footer">npm-docs &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-doctor.html
+++ b/deps/npm/html/doc/cli/npm-doctor.html
@ -103,4 +103,4 @@ cache, you should probably run <code>npm cache clean</code> and reset the cache.
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-doctor &mdash; npm@5.3.0</p>
+<p id="footer">npm-doctor &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-edit.html
+++ b/deps/npm/html/doc/cli/npm-edit.html
@ -49,5 +49,5 @@ or <code>&quot;notepad&quot;</code> on Windows.</li>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-edit &mdash; npm@5.3.0</p>
+<p id="footer">npm-edit &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-explore.html
+++ b/deps/npm/html/doc/cli/npm-explore.html
@ -49,5 +49,5 @@ Windows</li>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-explore &mdash; npm@5.3.0</p>
+<p id="footer">npm-explore &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-help-search.html
+++ b/deps/npm/html/doc/cli/npm-help-search.html
@ -45,5 +45,5 @@ where the terms were found in the documentation.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-help-search &mdash; npm@5.3.0</p>
+<p id="footer">npm-help-search &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-help.html
+++ b/deps/npm/html/doc/cli/npm-help.html
@ -50,5 +50,5 @@ matches are equivalent to specifying a topic name.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-help &mdash; npm@5.3.0</p>
+<p id="footer">npm-help &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-init.html
+++ b/deps/npm/html/doc/cli/npm-init.html
@ -48,5 +48,5 @@ defaults and not prompt you for any options.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-init &mdash; npm@5.3.0</p>
+<p id="footer">npm-init &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-install-test.html
+++ b/deps/npm/html/doc/cli/npm-install-test.html
@ -42,5 +42,5 @@ takes exactly the same arguments as <code>npm install</code>.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-install-test &mdash; npm@5.3.0</p>
+<p id="footer">npm-install-test &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-install.html
+++ b/deps/npm/html/doc/cli/npm-install.html
@ -367,5 +367,5 @@ affects a real use-case, it will be investigated.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-install &mdash; npm@5.3.0</p>
+<p id="footer">npm-install &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-link.html
+++ b/deps/npm/html/doc/cli/npm-link.html
@ -74,5 +74,5 @@ include that scope, e.g.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-link &mdash; npm@5.3.0</p>
+<p id="footer">npm-link &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-logout.html
+++ b/deps/npm/html/doc/cli/npm-logout.html
@ -51,5 +51,5 @@ it takes precedence.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-logout &mdash; npm@5.3.0</p>
+<p id="footer">npm-logout &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-ls.html
+++ b/deps/npm/html/doc/cli/npm-ls.html
@ -21,7 +21,7 @@ installed, as well as their dependencies, in a tree-structure.</p>
 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@5.3.0 /path/to/npm
+<pre><code>npm@5.5.1 /path/to/npm
 └─┬ init-package-json@0.0.4
  └── promzard@0.1.5
 </code></pre><p>It will print out extraneous, missing, and invalid packages.</p>
@ -110,5 +110,5 @@ project.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-ls &mdash; npm@5.3.0</p>
+<p id="footer">npm-ls &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-outdated.html
+++ b/deps/npm/html/doc/cli/npm-outdated.html
@ -116,5 +116,5 @@ project.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-outdated &mdash; npm@5.3.0</p>
+<p id="footer">npm-outdated &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-owner.html
+++ b/deps/npm/html/doc/cli/npm-owner.html
@ -32,6 +32,9 @@ privileges.</li>
 <p>Note that there is only one level of access.  Either you can modify a package,
 or you can&#39;t.  Future versions may contain more fine-grained access levels, but
 that is not implemented at this time.</p>
 <p>If you have two-factor authentication enabled with <code>auth-and-writes</code> then
 you&#39;ll need to include an otp on the command line when changing ownership
 with <code>--otp</code>.</p>
 <h2 id="see-also">SEE ALSO</h2>
 <ul>
 <li><a href="../cli/npm-publish.html">npm-publish(1)</a></li>
@ -51,5 +54,5 @@ that is not implemented at this time.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-owner &mdash; npm@5.3.0</p>
+<p id="footer">npm-owner &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-pack.html
+++ b/deps/npm/html/doc/cli/npm-pack.html
@ -41,5 +41,5 @@ overwritten the second time.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-pack &mdash; npm@5.3.0</p>
+<p id="footer">npm-pack &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-ping.html
+++ b/deps/npm/html/doc/cli/npm-ping.html
@ -13,8 +13,12 @@
 <h2 id="synopsis">SYNOPSIS</h2>
 <pre><code>npm ping [--registry &lt;registry&gt;]
 </code></pre><h2 id="description">DESCRIPTION</h2>
-<p>Ping the configured or given npm registry and verify authentication.</p>
+<p>Ping the configured or given npm registry and verify authentication.
-<h2 id="see-also">SEE ALSO</h2>
+If it works it will output something like:</p>
 <pre><code>Ping success: {*Details about registry*}
 </code></pre><p>otherwise you will get:</p>
 <pre><code>Ping error: {*Detail about error}
 </code></pre><h2 id="see-also">SEE ALSO</h2>
 <ul>
 <li><a href="../cli/npm-config.html">npm-config(1)</a></li>
 <li><a href="../misc/npm-config.html">npm-config(7)</a></li>
@ -32,5 +36,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-ping &mdash; npm@5.3.0</p>
+<p id="footer">npm-ping &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-prefix.html
+++ b/deps/npm/html/doc/cli/npm-prefix.html
@ -38,5 +38,5 @@ to contain a package.json file unless <code>-g</code> is also specified.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-prefix &mdash; npm@5.3.0</p>
+<p id="footer">npm-prefix &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-profile.html
+++ b/deps/npm/html/doc/cli/npm-profile.html
@ -0,0 +1,93 @@
 <!doctype html>
 <html>
  <title>npm-profile</title>
  <meta charset="utf-8">
  <link rel="stylesheet" type="text/css" href="../../static/style.css">
  <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-profile.html">
  <script async=true src="../../static/toc.js"></script>
  <body>
    <div id="wrapper">
 <h1><a href="../cli/npm-profile.html">npm-profile</a></h1> <p>Change settings on your registry profile</p>
 <h2 id="synopsis">SYNOPSIS</h2>
 <pre><code>npm profile get [--json|--parseable] [&lt;property&gt;]
 npm profile set [--json|--parseable] &lt;property&gt; &lt;value&gt;
 npm profile set password
 npm profile enable-2fa [auth-and-writes|auth-only]
 npm profile disable-2fa
 </code></pre><h2 id="description">DESCRIPTION</h2>
 <p>Change your profile information on the registry.  This not be available if
 you&#39;re using a non-npmjs registry.</p>
 <ul>
 <li><code>npm profile get [&lt;property&gt;]</code>:
 Display all of the properties of your profile, or one or more specific
 properties.  It looks like:</li>
 </ul>
 <pre><code>+-----------------+---------------------------+
 | name            | example                   |
 +-----------------+---------------------------+
 | email           | me@example.com (verified) |
 +-----------------+---------------------------+
 | two factor auth | auth-and-writes           |
 +-----------------+---------------------------+
 | fullname        | Example User              |
 +-----------------+---------------------------+
 | homepage        |                           |
 +-----------------+---------------------------+
 | freenode        |                           |
 +-----------------+---------------------------+
 | twitter         |                           |
 +-----------------+---------------------------+
 | github          |                           |
 +-----------------+---------------------------+
 | created         | 2015-02-26T01:38:35.892Z  |
 +-----------------+---------------------------+
 | updated         | 2017-10-02T21:29:45.922Z  |
 +-----------------+---------------------------+
 </code></pre><ul>
 <li><p><code>npm profile set &lt;property&gt; &lt;value&gt;</code>:
 Set the value of a profile property. You can set the following properties this way:
  email, fullname, homepage, freenode, twitter, github</p>
 </li>
 <li><p><code>npm profile set password</code>:
 Change your password.  This is interactive, you&#39;ll be prompted for your
 current password and a new password.  You&#39;ll also be prompted for an OTP
 if you have two-factor authentication enabled.</p>
 </li>
 <li><p><code>npm profile enable-2fa [auth-and-writes|auth-only]</code>:
 Enables two-factor authentication. Defaults to <code>auth-and-writes</code> mode. Modes are:</p>
 <ul>
 <li><code>auth-only</code>: Require an OTP when logging in or making changes to your
 account&#39;s authentication.  The OTP will be required on both the website
 and the command line.</li>
 <li><code>auth-and-writes</code>: Requires an OTP at all the times <code>auth-only</code> does, and also requires one when
 publishing a module, setting the <code>latest</code> dist-tag, or changing access
 via <code>npm access</code> and <code>npm owner</code>.</li>
 </ul>
 </li>
 <li><p><code>npm profile disable-2fa</code>:
 Disables two-factor authentication.</p>
 </li>
 </ul>
 <h2 id="details">DETAILS</h2>
 <p>All of the <code>npm profile</code> subcommands accept <code>--json</code> and <code>--parseable</code> and
 will tailor their output based on those.  Some of these commands may not be
 available on non npmjs.com registries.</p>
 <h2 id="see-also">SEE ALSO</h2>
 <ul>
 <li><a href="../misc/npm-config.html">npm-config(7)</a></li>
 </ul>
 </div>
 <table border=0 cellspacing=0 cellpadding=0 id=npmlogo>
 <tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18>&nbsp;</td></tr>
 <tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td><td style="width:40px;height:10px;background:#fff" colspan=4>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4>&nbsp;</td><td style="width:40px;height:10px;background:#fff" colspan=4>&nbsp;</td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td><td colspan=6 style="width:60px;height:10px;background:#fff">&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4>&nbsp;</td></tr>
 <tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:#fff" rowspan=3>&nbsp;</td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2>&nbsp;</td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2>&nbsp;</td><td style="width:10px;height:10px;background:#fff" rowspan=3>&nbsp;</td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:#fff" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3>&nbsp;</td></tr>
 <tr><td style="width:10px;height:10px;background:#fff" rowspan=2>&nbsp;</td></tr>
 <tr><td style="width:10px;height:10px;background:#fff">&nbsp;</td></tr>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
 <p id="footer">npm-profile &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-prune.html
+++ b/deps/npm/html/doc/cli/npm-prune.html
@ -40,5 +40,5 @@ negate <code>NODE_ENV</code> being set to <code>production</code>.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-prune &mdash; npm@5.3.0</p>
+<p id="footer">npm-prune &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-publish.html
+++ b/deps/npm/html/doc/cli/npm-publish.html
@ -11,7 +11,7 @@
 <h1><a href="../cli/npm-publish.html">npm-publish</a></h1> <p>Publish a package</p>
 <h2 id="synopsis">SYNOPSIS</h2>
-<pre><code>npm publish [&lt;tarball&gt;|&lt;folder&gt;] [--tag &lt;tag&gt;] [--access &lt;public|restricted&gt;]
+<pre><code>npm publish [&lt;tarball&gt;|&lt;folder&gt;] [--tag &lt;tag&gt;] [--access &lt;public|restricted&gt;] [--otp otpcode]
 Publishes &#39;.&#39; if no argument supplied
 Sets tag &#39;latest&#39; if no --tag specified
@ -45,6 +45,11 @@ restricted. Only applies to scoped packages, which default to <code>restricted</
 If you don&#39;t have a paid account, you must publish with <code>--access public</code>
 to publish scoped packages.</p>
 </li>
 <li><p><code>[--otp &lt;otpcode&gt;]</code>
 If you have two-factor authentication enabled in <code>auth-and-writes</code> mode
 then you can provide a code from your authenticator with this. If you
 don&#39;t include this and you&#39;re running from a TTY then you&#39;ll be prompted.</p>
 </li>
 </ul>
 <p>Fails if the package name and version combination already exists in
 the specified registry.</p>
@ -66,6 +71,7 @@ packs them into a tarball to be uploaded to the registry.</p>
 <li><a href="../cli/npm-deprecate.html">npm-deprecate(1)</a></li>
 <li><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></li>
 <li><a href="../cli/npm-pack.html">npm-pack(1)</a></li>
 <li><a href="../cli/npm-profile.html">npm-profile(1)</a></li>
 </ul>
 </div>
@ -79,5 +85,5 @@ packs them into a tarball to be uploaded to the registry.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-publish &mdash; npm@5.3.0</p>
+<p id="footer">npm-publish &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-rebuild.html
+++ b/deps/npm/html/doc/cli/npm-rebuild.html
@ -35,5 +35,5 @@ the new binary.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-rebuild &mdash; npm@5.3.0</p>
+<p id="footer">npm-rebuild &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-repo.html
+++ b/deps/npm/html/doc/cli/npm-repo.html
@ -41,5 +41,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-repo &mdash; npm@5.3.0</p>
+<p id="footer">npm-repo &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-restart.html
+++ b/deps/npm/html/doc/cli/npm-restart.html
@ -53,5 +53,5 @@ behavior will be accompanied by an increase in major version number</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-restart &mdash; npm@5.3.0</p>
+<p id="footer">npm-restart &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-root.html
+++ b/deps/npm/html/doc/cli/npm-root.html
@ -35,5 +35,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-root &mdash; npm@5.3.0</p>
+<p id="footer">npm-root &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-run-script.html
+++ b/deps/npm/html/doc/cli/npm-run-script.html
@ -29,7 +29,7 @@ all the arguments after the <code>--</code> directly to your script:</p>
 and not to any pre or post script.</p>
 <p>The <code>env</code> script is a special built-in command that can be used to list
 environment variables that will be available to the script at runtime. If an
-&quot;env&quot; command is defined in your package it will take precedence over the
+&quot;env&quot; command is defined in your package, it will take precedence over the
 built-in.</p>
 <p>In addition to the shell&#39;s pre-existing <code>PATH</code>, <code>npm run</code> adds
 <code>node_modules/.bin</code> to the <code>PATH</code> provided to scripts. Any binaries provided by
@ -37,7 +37,14 @@ locally-installed dependencies can be used without the <code>node_modules/.bin</
 prefix. For example, if there is a <code>devDependency</code> on <code>tap</code> in your package,
 you should write:</p>
 <pre><code>&quot;scripts&quot;: {&quot;test&quot;: &quot;tap test/\*.js&quot;}
-</code></pre><p>instead of <code>&quot;scripts&quot;: {&quot;test&quot;: &quot;node_modules/.bin/tap test/\*.js&quot;}</code> to run your tests.</p>
+</code></pre><p>instead of</p>
 <pre><code>&quot;scripts&quot;: {&quot;test&quot;: &quot;node_modules/.bin/tap test/\*.js&quot;}
 </code></pre><p>to run your tests.</p>
 <p>Scripts are run from the root of the module, regardless of what your current
 working directory is when you call <code>npm run</code>. If you want your script to
 use different behavior based on what subdirectory you&#39;re in, you can use the
 <code>INIT_CWD</code> environment variable, which holds the full path you were in when
 you ran <code>npm run</code>.</p>
 <p><code>npm run</code> sets the <code>NODE</code> environment variable to the <code>node</code> executable with
 which <code>npm</code> is executed. Also, if the <code>--scripts-prepend-node-path</code> is passed,
 the directory within which <code>node</code> resides is added to the
@ -67,5 +74,5 @@ you will be given a warning to run <code>npm install</code>, just in case you&#3
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-run-script &mdash; npm@5.3.0</p>
+<p id="footer">npm-run-script &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-search.html
+++ b/deps/npm/html/doc/cli/npm-search.html
@ -109,5 +109,5 @@ setting.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-search &mdash; npm@5.3.0</p>
+<p id="footer">npm-search &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-shrinkwrap.html
+++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html
@ -41,5 +41,5 @@ of package locks in npm, see <a href="../files/npm-package-locks.html">npm-packa
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-shrinkwrap &mdash; npm@5.3.0</p>
+<p id="footer">npm-shrinkwrap &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-star.html
+++ b/deps/npm/html/doc/cli/npm-star.html
@ -36,5 +36,5 @@ a vaguely positive way to show that you care.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-star &mdash; npm@5.3.0</p>
+<p id="footer">npm-star &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-stars.html
+++ b/deps/npm/html/doc/cli/npm-stars.html
@ -36,5 +36,5 @@ you will most certainly enjoy this command.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-stars &mdash; npm@5.3.0</p>
+<p id="footer">npm-stars &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-start.html
+++ b/deps/npm/html/doc/cli/npm-start.html
@ -39,5 +39,5 @@ more details.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-start &mdash; npm@5.3.0</p>
+<p id="footer">npm-start &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-stop.html
+++ b/deps/npm/html/doc/cli/npm-stop.html
@ -34,5 +34,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-stop &mdash; npm@5.3.0</p>
+<p id="footer">npm-stop &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-team.html
+++ b/deps/npm/html/doc/cli/npm-team.html
@ -67,5 +67,5 @@ use the <code>npm access</code> command to grant or revoke the appropriate permi
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-team &mdash; npm@5.3.0</p>
+<p id="footer">npm-team &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-test.html
+++ b/deps/npm/html/doc/cli/npm-test.html
@ -36,5 +36,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-test &mdash; npm@5.3.0</p>
+<p id="footer">npm-test &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-token.html
+++ b/deps/npm/html/doc/cli/npm-token.html
@ -0,0 +1,76 @@
 <!doctype html>
 <html>
  <title>npm-token</title>
  <meta charset="utf-8">
  <link rel="stylesheet" type="text/css" href="../../static/style.css">
  <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-token.html">
  <script async=true src="../../static/toc.js"></script>
  <body>
    <div id="wrapper">
 <h1><a href="../cli/npm-token.html">npm-token</a></h1> <p>Manage your authentication tokens</p>
 <h2 id="synopsis">SYNOPSIS</h2>
 <pre><code>npm token list [--json|--parseable]
 npm token create [--read-only] [--cidr=1.1.1.1/24,2.2.2.2/16]
 npm token delete &lt;id|token&gt;
 </code></pre><h2 id="description">DESCRIPTION</h2>
 <p>This list you list, create and delete authentication tokens. </p>
 <ul>
 <li><p><code>npm token list</code>:
 Shows a table of all active authentication tokens. You can request this as
 JSON with <code>--json</code> or tab-separated values with <code>--parseable</code>.</p>
 <pre><code>+--------+---------+------------+----------+----------------+
 | id     | token   | created    | read-only | CIDR whitelist |
 +--------+---------+------------+----------+----------------+
 | 7f3134 | 1fa9ba… | 2017-10-02 | yes      |                |
 +--------+---------+------------+----------+----------------+
 | c03241 | af7aef… | 2017-10-02 | no       | 192.168.0.1/24 |
 +--------+---------+------------+----------+----------------+
 | e0cf92 | 3a436a… | 2017-10-02 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 63eb9d | 74ef35… | 2017-09-28 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 2daaa8 | cbad5f… | 2017-09-26 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 68c2fe | 127e51… | 2017-09-23 | no       |                |
 +--------+---------+------------+----------+----------------+
 | 6334e1 | 1dadd1… | 2017-09-23 | no       |                |
 +--------+---------+------------+----------+----------------+
 </code></pre></li>
 <li><p><code>npm token create [--read-only] [--cidr=&lt;cidr-ranges&gt;]</code>:
 Create a new authentication token. It can be <code>--read-only</code> or accept a list of
 <a href="https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing">CIDR</a> ranges to
 limit use of this token to. This will prompt you for your password, and, if you have
 two-factor authentication enabled, an otp.</p>
 </li>
 </ul>
 <pre><code>+----------------+--------------------------------------+
 | token          | a73c9572-f1b9-8983-983d-ba3ac3cc913d |
 +----------------+--------------------------------------+
 | cidr_whitelist |                                      |
 +----------------+--------------------------------------+
 | readonly       | false                                |
 +----------------+--------------------------------------+
 | created        | 2017-10-02T07:52:24.838Z             |
 +----------------+--------------------------------------+
 </code></pre><ul>
 <li><code>npm token delete &lt;token|id&gt;</code>:
 This removes an authentication token, making it immediately unusable. This can accept
 both complete tokens (as you get back from <code>npm token create</code> and will
 find in your <code>.npmrc</code>) and ids as seen in the <code>npm token list</code> output.
 This will NOT accept the truncated token found in <code>npm token list</code> output.</li>
 </ul>
 </div>
 <table border=0 cellspacing=0 cellpadding=0 id=npmlogo>
 <tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18>&nbsp;</td></tr>
 <tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td><td style="width:40px;height:10px;background:#fff" colspan=4>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4>&nbsp;</td><td style="width:40px;height:10px;background:#fff" colspan=4>&nbsp;</td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td><td colspan=6 style="width:60px;height:10px;background:#fff">&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4>&nbsp;</td></tr>
 <tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:#fff" rowspan=3>&nbsp;</td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2>&nbsp;</td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2>&nbsp;</td><td style="width:10px;height:10px;background:#fff" rowspan=3>&nbsp;</td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:#fff" rowspan=3>&nbsp;</td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3>&nbsp;</td></tr>
 <tr><td style="width:10px;height:10px;background:#fff" rowspan=2>&nbsp;</td></tr>
 <tr><td style="width:10px;height:10px;background:#fff">&nbsp;</td></tr>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
 <p id="footer">npm-token &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-uninstall.html
+++ b/deps/npm/html/doc/cli/npm-uninstall.html
@ -63,5 +63,5 @@ npm uninstall lodash --no-save
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-uninstall &mdash; npm@5.3.0</p>
+<p id="footer">npm-uninstall &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-unpublish.html
+++ b/deps/npm/html/doc/cli/npm-unpublish.html
@ -51,5 +51,5 @@ contact support@npmjs.com.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-unpublish &mdash; npm@5.3.0</p>
+<p id="footer">npm-unpublish &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-update.html
+++ b/deps/npm/html/doc/cli/npm-update.html
@ -118,5 +118,5 @@ be <em>downgraded</em>.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-update &mdash; npm@5.3.0</p>
+<p id="footer">npm-update &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-version.html
+++ b/deps/npm/html/doc/cli/npm-version.html
@ -86,6 +86,12 @@ to the same value as the current version.</p>
 <li>Type: Boolean</li>
 </ul>
 <p>Commit and tag the version change.</p>
 <h3 id="commit-hooks">commit-hooks</h3>
 <ul>
 <li>Default: true</li>
 <li>Type: Boolean</li>
 </ul>
 <p>Run git commit hooks when committing the version change.</p>
 <h3 id="sign-git-tag">sign-git-tag</h3>
 <ul>
 <li>Default: false</li>
@ -114,5 +120,5 @@ to the same value as the current version.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-version &mdash; npm@5.3.0</p>
+<p id="footer">npm-version &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-view.html
+++ b/deps/npm/html/doc/cli/npm-view.html
@ -86,5 +86,5 @@ the field name.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-view &mdash; npm@5.3.0</p>
+<p id="footer">npm-view &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm-whoami.html
+++ b/deps/npm/html/doc/cli/npm-whoami.html
@ -33,5 +33,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-whoami &mdash; npm@5.3.0</p>
+<p id="footer">npm-whoami &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/cli/npm.html
+++ b/deps/npm/html/doc/cli/npm.html
@ -13,7 +13,7 @@
 <h2 id="synopsis">SYNOPSIS</h2>
 <pre><code>npm &lt;command&gt; [args]
 </code></pre><h2 id="version">VERSION</h2>
-<p>5.3.0</p>
+<p>5.5.1</p>
 <h2 id="description">DESCRIPTION</h2>
 <p>npm is the package manager for the Node JavaScript platform.  It puts
 modules in place so that node can find them, and manages dependency
@ -126,7 +126,7 @@ will no doubt tell you to put the output in a gist or email.</p>
 <p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> ::
 <a href="https://github.com/isaacs/">isaacs</a> ::
 <a href="http://twitter.com/izs">@izs</a> ::
-<a href="&#x6d;&#x61;&#x69;&#x6c;&#x74;&#111;&#58;&#x69;&#64;&#x69;&#x7a;&#115;&#46;&#109;&#x65;">&#x69;&#64;&#x69;&#x7a;&#115;&#46;&#109;&#x65;</a></p>
+<a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#105;&#64;&#x69;&#x7a;&#x73;&#x2e;&#109;&#x65;">&#105;&#64;&#x69;&#x7a;&#x73;&#x2e;&#109;&#x65;</a></p>
 <h2 id="see-also">SEE ALSO</h2>
 <ul>
 <li><a href="../cli/npm-help.html">npm-help(1)</a></li>
@ -150,5 +150,5 @@ will no doubt tell you to put the output in a gist or email.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm &mdash; npm@5.3.0</p>
+<p id="footer">npm &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/npm-folders.html
+++ b/deps/npm/html/doc/files/npm-folders.html
@ -181,5 +181,5 @@ cannot be found elsewhere.  See <code><a href="../files/package.json.html">packa
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-folders &mdash; npm@5.3.0</p>
+<p id="footer">npm-folders &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/npm-global.html
+++ b/deps/npm/html/doc/files/npm-global.html
@ -181,5 +181,5 @@ cannot be found elsewhere.  See <code><a href="../files/package.json.html">packa
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-folders &mdash; npm@5.3.0</p>
+<p id="footer">npm-folders &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/npm-json.html
+++ b/deps/npm/html/doc/files/npm-json.html
@ -129,13 +129,21 @@ is an object with a &quot;name&quot; field and optionally &quot;url&quot; and &q
 </code></pre><p>Both email and url are optional either way.</p>
 <p>npm also sets a top-level &quot;maintainers&quot; field with your npm user info.</p>
 <h2 id="files">files</h2>
-<p>The &quot;files&quot; field is an array of files to include in your project.  If
+<p>The optional &quot;files&quot; field is an array of file patterns that describes
-you name a folder in the array, then it will also include the files
+the entries to be included when your package is installed as a
-inside that folder. (Unless they would be ignored by another rule.)</p>
+dependency. If the files array is omitted, everything except
-<p>You can also provide a &quot;.npmignore&quot; file in the root of your package or
+automatically-excluded files will be included in your publish. If you
-in subdirectories, which will keep files from being included, even
+name a folder in the array, then it will also include the files inside
-if they would be picked up by the files array.  The <code>.npmignore</code> file
+that folder (unless they would be ignored by another rule in this
-works just like a <code>.gitignore</code>.</p>
+section.).</p>
 <p>You can also provide a <code>.npmignore</code> file in the root of your package or
 in subdirectories, which will keep files from being included. At the
 root of your package it will not override the &quot;files&quot; field, but in
 subdirectories it will. The <code>.npmignore</code> file works just like a
 <code>.gitignore</code>. If there is a <code>.gitignore</code> file, and <code>.npmignore</code> is
 missing, <code>.gitignore</code>&#39;s contents will be used instead.</p>
 <p>Files included with the &quot;package.json#files&quot; field <em>cannot</em> be excluded
 through <code>.npmignore</code> or <code>.gitignore</code>.</p>
 <p>Certain files are always included, regardless of settings:</p>
 <ul>
 <li><code>package.json</code></li>
@ -593,5 +601,5 @@ ignored.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">package.json &mdash; npm@5.3.0</p>
+<p id="footer">package.json &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/npm-package-locks.html
+++ b/deps/npm/html/doc/files/npm-package-locks.html
@ -87,7 +87,7 @@ which will look something like this:</p>
  }
 }
 </code></pre><p>This file describes an <em>exact</em>, and more importantly <em>reproducible</em>
-<code>node_modules</code> tree. Once it&#39;s present, and future installation will base its
+<code>node_modules</code> tree. Once it&#39;s present, any future installation will base its
 work off this file, instead of recalculating dependency versions off
 p<a href="../files/ackage.json.html">ackage.json(5)</a>.</p>
 <p>The presence of a package lock changes the installation behavior such that:</p>
@ -145,4 +145,4 @@ if any transitive dependencies were updated, hoisted, etc.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-package-locks &mdash; npm@5.3.0</p>
+<p id="footer">npm-package-locks &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/npm-shrinkwrap.json.html
+++ b/deps/npm/html/doc/files/npm-shrinkwrap.json.html
@ -42,4 +42,4 @@ to the manual page for <a href="../files/package-lock.json.html">package-lock.js
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-shrinkwrap.json &mdash; npm@5.3.0</p>
+<p id="footer">npm-shrinkwrap.json &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/npmrc.html
+++ b/deps/npm/html/doc/files/npmrc.html
@ -85,5 +85,5 @@ manner.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npmrc &mdash; npm@5.3.0</p>
+<p id="footer">npmrc &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/package-lock.json.html
+++ b/deps/npm/html/doc/files/package-lock.json.html
@ -124,4 +124,4 @@ on the current platform.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">package-lock.json &mdash; npm@5.3.0</p>
+<p id="footer">package-lock.json &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/files/package.json.html
+++ b/deps/npm/html/doc/files/package.json.html
@ -129,13 +129,21 @@ is an object with a &quot;name&quot; field and optionally &quot;url&quot; and &q
 </code></pre><p>Both email and url are optional either way.</p>
 <p>npm also sets a top-level &quot;maintainers&quot; field with your npm user info.</p>
 <h2 id="files">files</h2>
-<p>The &quot;files&quot; field is an array of files to include in your project.  If
+<p>The optional &quot;files&quot; field is an array of file patterns that describes
-you name a folder in the array, then it will also include the files
+the entries to be included when your package is installed as a
-inside that folder. (Unless they would be ignored by another rule.)</p>
+dependency. If the files array is omitted, everything except
-<p>You can also provide a &quot;.npmignore&quot; file in the root of your package or
+automatically-excluded files will be included in your publish. If you
-in subdirectories, which will keep files from being included, even
+name a folder in the array, then it will also include the files inside
-if they would be picked up by the files array.  The <code>.npmignore</code> file
+that folder (unless they would be ignored by another rule in this
-works just like a <code>.gitignore</code>.</p>
+section.).</p>
 <p>You can also provide a <code>.npmignore</code> file in the root of your package or
 in subdirectories, which will keep files from being included. At the
 root of your package it will not override the &quot;files&quot; field, but in
 subdirectories it will. The <code>.npmignore</code> file works just like a
 <code>.gitignore</code>. If there is a <code>.gitignore</code> file, and <code>.npmignore</code> is
 missing, <code>.gitignore</code>&#39;s contents will be used instead.</p>
 <p>Files included with the &quot;package.json#files&quot; field <em>cannot</em> be excluded
 through <code>.npmignore</code> or <code>.gitignore</code>.</p>
 <p>Certain files are always included, regardless of settings:</p>
 <ul>
 <li><code>package.json</code></li>
@ -593,5 +601,5 @@ ignored.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">package.json &mdash; npm@5.3.0</p>
+<p id="footer">package.json &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/index.html
+++ b/deps/npm/html/doc/index.html
@ -74,6 +74,8 @@
 <p>Ping npm registry</p>
 <h3 id="npm-prefix-1-"><a href="cli/npm-prefix.html">npm-prefix(1)</a></h3>
 <p>Display prefix</p>
 <h3 id="npm-profile-1-"><a href="cli/npm-profile.html">npm-profile(1)</a></h3>
 <p>Change settings on your registry profile</p>
 <h3 id="npm-prune-1-"><a href="cli/npm-prune.html">npm-prune(1)</a></h3>
 <p>Remove extraneous packages</p>
 <h3 id="npm-publish-1-"><a href="cli/npm-publish.html">npm-publish(1)</a></h3>
@ -104,6 +106,8 @@
 <p>Manage organization teams and team memberships</p>
 <h3 id="npm-test-1-"><a href="cli/npm-test.html">npm-test(1)</a></h3>
 <p>Test a package</p>
 <h3 id="npm-token-1-"><a href="cli/npm-token.html">npm-token(1)</a></h3>
 <p>Manage your authentication tokens</p>
 <h3 id="npm-uninstall-1-"><a href="cli/npm-uninstall.html">npm-uninstall(1)</a></h3>
 <p>Remove a package</p>
 <h3 id="npm-unpublish-1-"><a href="cli/npm-unpublish.html">npm-unpublish(1)</a></h3>
@ -168,5 +172,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-index &mdash; npm@5.3.0</p>
+<p id="footer">npm-index &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-coding-style.html
+++ b/deps/npm/html/doc/misc/npm-coding-style.html
@ -153,5 +153,5 @@ set to anything.&quot;</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-coding-style &mdash; npm@5.3.0</p>
+<p id="footer">npm-coding-style &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-config.html
+++ b/deps/npm/html/doc/misc/npm-config.html
@ -33,6 +33,8 @@ same. However, please note that inside <a href="/misc/scripts">npm-scripts</a>
 npm will set its own environment variables and Node will prefer
 those lowercase versions over any uppercase ones that you might set.
 For details see <a href="https://github.com/npm/npm/issues/14528">this issue</a>.</p>
 <p>Notice that you need to use underscores instead of dashes, so <code>--allow-same-version</code>
 would become <code>npm_config_allow_same_version=true</code>.</p>
 <h3 id="npmrc-files">npmrc Files</h3>
 <p>The four relevant files are:</p>
 <ul>
@ -160,7 +162,7 @@ ostensibly Unix systems.</p>
 <li>Type: String, Array or null</li>
 </ul>
 <p>The Certificate Authority signing certificate that is trusted for SSL
-connections to the registry. Values should be in PEM format with newlines
+connections to the registry. Values should be in PEM format (Windows calls it &quot;Base-64 encoded X.509 (.CER)&quot;) with newlines
 replaced by the string &quot;\n&quot;. For example:</p>
 <pre><code>ca=&quot;-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----&quot;
 </code></pre><p>Set to <code>null</code> to only allow &quot;known&quot; registrars, or to a specific CA cert
@ -221,9 +223,15 @@ well as for the CA information to be stored in a file on disk.</p>
 <li>Type: String</li>
 </ul>
 <p>A client certificate to pass when accessing the registry.  Values should be in
-PEM format with newlines replaced by the string &quot;\n&quot;. For example:</p>
+PEM format (Windows calls it &quot;Base-64 encoded X.509 (.CER)&quot;) with newlines replaced by the string &quot;\n&quot;. For example:</p>
 <pre><code>cert=&quot;-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----&quot;
 </code></pre><p>It is <em>not</em> the path to a certificate file (and there is no &quot;certfile&quot; option).</p>
 <h3 id="cidr">cidr</h3>
 <ul>
 <li>Default: <code>null</code></li>
 <li>Type: String, Array, null</li>
 </ul>
 <p>This is a list of CIDR address to be used when configuring limited access tokens with the <code>npm token create</code> command.</p>
 <h3 id="color">color</h3>
 <ul>
 <li>Default: true</li>
@ -333,6 +341,12 @@ the git binary.</p>
 <li>Type: Boolean</li>
 </ul>
 <p>Tag the commit when using the <code>npm version</code> command.</p>
 <h3 id="commit-hooks">commit-hooks</h3>
 <ul>
 <li>Default: <code>true</code></li>
 <li>Type: Boolean</li>
 </ul>
 <p>Run git commit hooks when using the <code>npm version</code> command.</p>
 <h3 id="global">global</h3>
 <ul>
 <li>Default: false</li>
@ -498,14 +512,14 @@ being installed locally.</li>
 to the npm registry.  Must be IPv4 in versions of Node prior to 0.12.</p>
 <h3 id="loglevel">loglevel</h3>
 <ul>
-<li>Default: &quot;warn&quot;</li>
+<li>Default: &quot;notice&quot;</li>
 <li>Type: String</li>
-<li>Values: &quot;silent&quot;, &quot;error&quot;, &quot;warn&quot;, &quot;http&quot;, &quot;info&quot;, &quot;verbose&quot;, &quot;silly&quot;</li>
+<li>Values: &quot;silent&quot;, &quot;error&quot;, &quot;warn&quot;, &quot;notice&quot;, &quot;http&quot;, &quot;timing&quot;, &quot;info&quot;,
 &quot;verbose&quot;, &quot;silly&quot;</li>
 </ul>
 <p>What level of logs to report.  On failure, <em>all</em> logs are written to
 <code>npm-debug.log</code> in the current working directory.</p>
-<p>Any logs of a higher level than the setting are shown.
+<p>Any logs of a higher level than the setting are shown. The default is &quot;notice&quot;.</p>
 The default is &quot;warn&quot;, which shows warn and error output.</p>
 <h3 id="logstream">logstream</h3>
 <ul>
 <li>Default: process.stderr</li>
@ -592,6 +606,13 @@ installed.</p>
 <p>Attempt to install packages in the <code>optionalDependencies</code> object.  Note
 that if these packages fail to install, the overall installation
 process is not aborted.</p>
 <h3 id="otp">otp</h3>
 <ul>
 <li>Default: null</li>
 <li>Type: Number</li>
 </ul>
 <p>This is a one-time password from a two-factor authenticator.  It&#39;s needed
 when publishing or changing package permissions with <code>npm access</code>.</p>
 <h3 id="package-lock">package-lock</h3>
 <ul>
 <li>Default: true</li>
@ -648,16 +669,6 @@ local <code>npm install</code> without any arguments.</li>
 <p>When set to <code>true</code>, npm will display a progress bar during time intensive
 operations, if <code>process.stderr</code> is a TTY.</p>
 <p>Set to <code>false</code> to suppress the progress bar.</p>
 <h3 id="proprietary-attribs">proprietary-attribs</h3>
 <ul>
 <li>Default: true</li>
 <li>Type: Boolean</li>
 </ul>
 <p>Whether or not to include proprietary extended attributes in the
 tarballs created by npm.</p>
 <p>Unless you are expecting to unpack package tarballs with something other
 than npm -- particularly a very outdated tar implementation -- leave
 this as true.</p>
 <h3 id="proxy">proxy</h3>
 <ul>
 <li>Default: null</li>
@ -666,6 +677,12 @@ this as true.</p>
 <p>A proxy to use for outgoing http requests. If the <code>HTTP_PROXY</code> or
 <code>http_proxy</code> environment variables are set, proxy settings will be
 honored by the underlying <code>request</code> library.</p>
 <h3 id="read-only">read-only</h3>
 <ul>
 <li>Default: false</li>
 <li>Type: Boolean</li>
 </ul>
 <p>This is used to mark a token as unable to publish when configuring limited access tokens with the <code>npm token create</code> command.</p>
 <h3 id="rebuild-bundle">rebuild-bundle</h3>
 <ul>
 <li>Default: true</li>
@ -992,5 +1009,5 @@ exit successfully.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-config &mdash; npm@5.3.0</p>
+<p id="footer">npm-config &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-developers.html
+++ b/deps/npm/html/doc/misc/npm-developers.html
@ -131,6 +131,16 @@ bother adding <code>node_modules</code> to <code>.npmignore</code>.</p>
 <li><code>CHANGELOG</code> (and its variants)</li>
 <li><code>LICENSE</code> / <code>LICENCE</code></li>
 </ul>
 <p>If, given the structure of your project, you find <code>.npmignore</code> to be a
 maintenance headache, you might instead try populating the <code>files</code>
 property of <code>package.json</code>, which is an array of file or directory names
 that should be included in your package. Sometimes a whitelist is easier
 to manage than a blacklist.</p>
 <h3 id="testing-whether-your-npmignore-or-files-config-works">Testing whether your <code>.npmignore</code> or <code>files</code> config works</h3>
 <p>If you want to double check that your package will include only the files
 you intend it to when published, you can run the <code>npm pack</code> command locally
 which will generate a tarball in the working directory, the same way it
 does for publishing.</p>
 <h2 id="link-packages">Link Packages</h2>
 <p><code>npm link</code> is designed to install a development package and see the
 changes in real time without having to keep re-installing it.  (You do
@ -194,5 +204,5 @@ from a fresh checkout.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-developers &mdash; npm@5.3.0</p>
+<p id="footer">npm-developers &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-disputes.html
+++ b/deps/npm/html/doc/misc/npm-disputes.html
@ -20,7 +20,7 @@ Conduct.</p>
 <h2 id="tl-dr">TL;DR</h2>
 <ol>
 <li>Get the author email with <code>npm owner ls &lt;pkgname&gt;</code></li>
-<li>Email the author, CC <a href="&#x6d;&#x61;&#x69;&#108;&#x74;&#111;&#58;&#115;&#x75;&#112;&#x70;&#111;&#114;&#116;&#x40;&#110;&#x70;&#x6d;&#x6a;&#x73;&#x2e;&#x63;&#x6f;&#109;">&#115;&#x75;&#112;&#x70;&#111;&#114;&#116;&#x40;&#110;&#x70;&#x6d;&#x6a;&#x73;&#x2e;&#x63;&#x6f;&#109;</a></li>
+<li>Email the author, CC <a href="&#x6d;&#97;&#105;&#108;&#x74;&#x6f;&#x3a;&#x73;&#x75;&#x70;&#x70;&#111;&#114;&#116;&#64;&#x6e;&#112;&#x6d;&#106;&#115;&#x2e;&#x63;&#x6f;&#109;">&#x73;&#x75;&#x70;&#x70;&#111;&#114;&#116;&#64;&#x6e;&#112;&#x6d;&#106;&#115;&#x2e;&#x63;&#x6f;&#109;</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>
@ -55,12 +55,12 @@ because Yusuf&#39;s <code>foo</code> is in the way.</p>
 </li>
 <li>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>,
 and what she would like to do with the module name. She adds the npm support
-staff <a href="&#x6d;&#x61;&#105;&#108;&#x74;&#x6f;&#58;&#x73;&#x75;&#x70;&#x70;&#x6f;&#x72;&#x74;&#64;&#110;&#112;&#x6d;&#x6a;&#x73;&#x2e;&#x63;&#x6f;&#109;">&#x73;&#x75;&#x70;&#x70;&#x6f;&#x72;&#x74;&#64;&#110;&#112;&#x6d;&#x6a;&#x73;&#x2e;&#x63;&#x6f;&#109;</a> to the CC list of the email. Mention in the email
+staff <a href="&#x6d;&#x61;&#105;&#108;&#116;&#x6f;&#58;&#x73;&#x75;&#x70;&#x70;&#111;&#x72;&#116;&#64;&#110;&#112;&#x6d;&#106;&#x73;&#x2e;&#x63;&#111;&#x6d;">&#x73;&#x75;&#x70;&#x70;&#111;&#x72;&#116;&#64;&#110;&#112;&#x6d;&#106;&#x73;&#x2e;&#x63;&#111;&#x6d;</a> to the CC list of the email. Mention in the email
 that Yusuf can run npm owner <code>add alice foo</code> to add Alice as an owner of the
 foo package.</li>
 <li>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf
 and Alice can&#39;t come to any sort of resolution, email support
-<a href="&#109;&#97;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#x73;&#x75;&#x70;&#x70;&#111;&#114;&#x74;&#64;&#x6e;&#x70;&#109;&#x6a;&#115;&#x2e;&#x63;&#x6f;&#x6d;">&#x73;&#x75;&#x70;&#x70;&#111;&#114;&#x74;&#64;&#x6e;&#x70;&#109;&#x6a;&#115;&#x2e;&#x63;&#x6f;&#x6d;</a> and we&#39;ll sort it out. (&quot;Reasonable&quot; is usually at least
+<a href="&#x6d;&#97;&#105;&#108;&#116;&#111;&#58;&#115;&#117;&#x70;&#x70;&#111;&#x72;&#116;&#x40;&#110;&#112;&#109;&#106;&#x73;&#46;&#x63;&#x6f;&#109;">&#115;&#117;&#x70;&#x70;&#111;&#x72;&#116;&#x40;&#110;&#112;&#109;&#106;&#x73;&#46;&#x63;&#x6f;&#109;</a> and we&#39;ll sort it out. (&quot;Reasonable&quot; is usually at least
 4 weeks.)</li>
 </ol>
 <h2 id="reasoning">REASONING</h2>
@ -96,12 +96,12 @@ application database or otherwise putting non-packagey things into it.</li>
 <a href="https://www.npmjs.com/policies/conduct">Code of Conduct</a> such as hateful
 language, pornographic content, or harassment.</li>
 </ol>
-<p>If you see bad behavior like this, please report it to <a href="&#x6d;&#x61;&#x69;&#108;&#116;&#x6f;&#58;&#97;&#x62;&#117;&#x73;&#101;&#64;&#x6e;&#112;&#109;&#x6a;&#x73;&#46;&#99;&#111;&#x6d;">&#97;&#x62;&#117;&#x73;&#101;&#64;&#x6e;&#112;&#109;&#x6a;&#x73;&#46;&#99;&#111;&#x6d;</a> right
+<p>If you see bad behavior like this, please report it to <a href="&#x6d;&#x61;&#105;&#108;&#x74;&#x6f;&#58;&#97;&#98;&#117;&#x73;&#x65;&#64;&#x6e;&#112;&#x6d;&#x6a;&#x73;&#46;&#99;&#111;&#109;">&#97;&#98;&#117;&#x73;&#x65;&#64;&#x6e;&#112;&#x6d;&#x6a;&#x73;&#46;&#99;&#111;&#109;</a> right
 away. <strong>You are never expected to resolve abusive behavior on your own. We are
 here to help.</strong></p>
 <h2 id="trademarks">TRADEMARKS</h2>
 <p>If you think another npm publisher is infringing your trademark, such as by
-using a confusingly similar package name, email <a href="&#109;&#97;&#105;&#x6c;&#x74;&#x6f;&#x3a;&#97;&#x62;&#117;&#x73;&#x65;&#x40;&#110;&#112;&#109;&#106;&#x73;&#x2e;&#99;&#111;&#109;">&#97;&#x62;&#117;&#x73;&#x65;&#x40;&#110;&#112;&#109;&#106;&#x73;&#x2e;&#99;&#111;&#109;</a> with a link to
+using a confusingly similar package name, email <a href="&#109;&#97;&#x69;&#x6c;&#116;&#x6f;&#x3a;&#x61;&#98;&#117;&#x73;&#x65;&#64;&#110;&#x70;&#x6d;&#106;&#115;&#x2e;&#99;&#x6f;&#109;">&#x61;&#98;&#117;&#x73;&#x65;&#64;&#110;&#x70;&#x6d;&#106;&#115;&#x2e;&#99;&#x6f;&#109;</a> with a link to
 the package or user account on <a href="https://npmjs.com">https://npmjs.com</a>. Attach a
 copy of your trademark registration certificate.</p>
 <p>If we see that the package&#39;s publisher is intentionally misleading others by
@ -134,5 +134,5 @@ License.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-disputes &mdash; npm@5.3.0</p>
+<p id="footer">npm-disputes &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-index.html
+++ b/deps/npm/html/doc/misc/npm-index.html
@ -74,6 +74,8 @@
 <p>Ping npm registry</p>
 <h3 id="npm-prefix-1-"><a href="../cli/npm-prefix.html">npm-prefix(1)</a></h3>
 <p>Display prefix</p>
 <h3 id="npm-profile-1-"><a href="../cli/npm-profile.html">npm-profile(1)</a></h3>
 <p>Change settings on your registry profile</p>
 <h3 id="npm-prune-1-"><a href="../cli/npm-prune.html">npm-prune(1)</a></h3>
 <p>Remove extraneous packages</p>
 <h3 id="npm-publish-1-"><a href="../cli/npm-publish.html">npm-publish(1)</a></h3>
@ -104,6 +106,8 @@
 <p>Manage organization teams and team memberships</p>
 <h3 id="npm-test-1-"><a href="../cli/npm-test.html">npm-test(1)</a></h3>
 <p>Test a package</p>
 <h3 id="npm-token-1-"><a href="../cli/npm-token.html">npm-token(1)</a></h3>
 <p>Manage your authentication tokens</p>
 <h3 id="npm-uninstall-1-"><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></h3>
 <p>Remove a package</p>
 <h3 id="npm-unpublish-1-"><a href="../cli/npm-unpublish.html">npm-unpublish(1)</a></h3>
@ -168,5 +172,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-index &mdash; npm@5.3.0</p>
+<p id="footer">npm-index &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-orgs.html
+++ b/deps/npm/html/doc/misc/npm-orgs.html
@ -86,5 +86,5 @@
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-orgs &mdash; npm@5.3.0</p>
+<p id="footer">npm-orgs &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-registry.html
+++ b/deps/npm/html/doc/misc/npm-registry.html
@ -90,5 +90,5 @@ effectively implement the entire CouchDB API anyway.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-registry &mdash; npm@5.3.0</p>
+<p id="footer">npm-registry &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-scope.html
+++ b/deps/npm/html/doc/misc/npm-scope.html
@ -99,5 +99,5 @@ that registry instead.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-scope &mdash; npm@5.3.0</p>
+<p id="footer">npm-scope &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/npm-scripts.html
+++ b/deps/npm/html/doc/misc/npm-scripts.html
@ -11,7 +11,7 @@
 <h1><a href="../misc/npm-scripts.html">npm-scripts</a></h1> <p>How npm handles the &quot;scripts&quot; field</p>
 <h2 id="description">DESCRIPTION</h2>
-<p>npm supports the &quot;scripts&quot; property of the package.json script, for the
+<p>npm supports the &quot;scripts&quot; property of the package.json file, for the
 following scripts:</p>
 <ul>
 <li>prepublish:
@ -239,5 +239,5 @@ scripts is for compilation which must be done on the target architecture.</li>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-scripts &mdash; npm@5.3.0</p>
+<p id="footer">npm-scripts &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/removing-npm.html
+++ b/deps/npm/html/doc/misc/removing-npm.html
@ -57,5 +57,5 @@ modules.  To track those down, you can do the following:</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">removing-npm &mdash; npm@5.3.0</p>
+<p id="footer">removing-npm &mdash; npm@5.5.1</p>
--- a/deps/npm/html/doc/misc/semver.html
+++ b/deps/npm/html/doc/misc/semver.html
@ -10,10 +10,13 @@
    <div id="wrapper">
 <h1><a href="../misc/semver.html">semver</a></h1> <p>The semantic versioner for npm</p>
 <h2 id="install">Install</h2>
 <pre><code class="lang-bash">npm install --save semver
 `
 </code></pre>
 <h2 id="usage">Usage</h2>
-<pre><code>$ npm install semver
+<p>As a node module:</p>
-$ node
+<pre><code class="lang-js">const semver = require(&#39;semver&#39;)
 var semver = require(&#39;semver&#39;)
 semver.valid(&#39;1.2.3&#39;) // &#39;1.2.3&#39;
 semver.valid(&#39;a.b.c&#39;) // null
@ -21,10 +24,11 @@ semver.clean(&#39;  =v1.2.3   &#39;) // &#39;1.2.3&#39;
 semver.satisfies(&#39;1.2.3&#39;, &#39;1.x || &gt;=2.5.0 || 5.0.0 - 7.2.3&#39;) // true
 semver.gt(&#39;1.2.3&#39;, &#39;9.8.7&#39;) // false
 semver.lt(&#39;1.2.3&#39;, &#39;9.8.7&#39;) // true
-</code></pre><p>As a command-line utility:</p>
+</code></pre>
 <p>As a command-line utility:</p>
 <pre><code>$ semver -h
-SemVer 5.1.0
+SemVer 5.3.0
 A JavaScript implementation of the http://semver.org/ specification
 Copyright Isaac Z. Schlueter
@ -113,15 +117,15 @@ similar risk on the <em>next</em> set of prerelease versions.</p>
 <h4 id="prerelease-identifiers">Prerelease Identifiers</h4>
 <p>The method <code>.inc</code> takes an additional <code>identifier</code> string argument that
 will append the value of the string as a prerelease identifier:</p>
-<pre><code class="lang-javascript">&gt; semver.inc(&#39;1.2.3&#39;, &#39;prerelease&#39;, &#39;beta&#39;)
+<pre><code class="lang-javascript">semver.inc(&#39;1.2.3&#39;, &#39;prerelease&#39;, &#39;beta&#39;)
-&#39;1.2.4-beta.0&#39;
+// &#39;1.2.4-beta.0&#39;
 </code></pre>
 <p>command-line example:</p>
-<pre><code class="lang-shell">$ semver 1.2.3 -i prerelease --preid beta
+<pre><code class="lang-bash">$ semver 1.2.3 -i prerelease --preid beta
 1.2.4-beta.0
 </code></pre>
 <p>Which then can be used to increment further:</p>
-<pre><code class="lang-shell">$ semver 1.2.4-beta.0 -i prerelease
+<pre><code class="lang-bash">$ semver 1.2.4-beta.0 -i prerelease
 1.2.4-beta.1
 </code></pre>
 <h3 id="advanced-range-syntax">Advanced Range Syntax</h3>
@ -263,6 +267,8 @@ if none exist. Example: <code>prerelease(&#39;1.2.3-alpha.1&#39;) -&gt; [&#39;al
 <li><code>major(v)</code>: Return the major version number.</li>
 <li><code>minor(v)</code>: Return the minor version number.</li>
 <li><code>patch(v)</code>: Return the patch version number.</li>
 <li><code>intersects(r1, r2, loose)</code>: Return true if the two supplied ranges
 or comparators intersect.</li>
 </ul>
 <h3 id="comparison">Comparison</h3>
 <ul>
@ -286,6 +292,10 @@ in descending order when passed to <code>Array.sort()</code>.</li>
 (<code>major</code>, <code>premajor</code>, <code>minor</code>, <code>preminor</code>, <code>patch</code>, <code>prepatch</code>, or <code>prerelease</code>),
 or null if the versions are the same.</li>
 </ul>
 <h3 id="comparators">Comparators</h3>
 <ul>
 <li><code>intersects(comparator)</code>: Return true if the comparators intersect</li>
 </ul>
 <h3 id="ranges">Ranges</h3>
 <ul>
 <li><code>validRange(range)</code>: Return the valid range or null if it&#39;s not valid</li>
@ -303,6 +313,7 @@ versions possible in the range.</li>
 the bounds of the range in either the high or low direction.  The
 <code>hilo</code> argument must be either the string <code>&#39;&gt;&#39;</code> or <code>&#39;&lt;&#39;</code>.  (This is
 the function called by <code>gtr</code> and <code>ltr</code>.)</li>
 <li><code>intersects(range)</code>: Return true if any of the ranges comparators intersect</li>
 </ul>
 <p>Note that, since ranges may be non-contiguous, a version might not be
 greater than a range, less than a range, <em>or</em> satisfy a range!  For
@ -325,5 +336,5 @@ range, use the <code>satisfies(version, range)</code> function.</p>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">semver &mdash; npm@5.3.0</p>
+<p id="footer">semver &mdash; npm@5.5.1</p>
--- a/deps/npm/lib/auth/legacy.js
+++ b/deps/npm/lib/auth/legacy.js
@ -1,142 +1,52 @@
-var log = require('npmlog')
+'use strict'
-var npm = require('../npm.js')
+const read = require('../utils/read-user-info.js')
-var read = require('read')
+const profile = require('npm-profile')
-var userValidate = require('npm-user-validate')
+const log = require('npmlog')
-var output = require('../utils/output')
+const npm = require('../npm.js')
-var chain = require('slide').chain
+const output = require('../utils/output.js')
 module.exports.login = function login (creds, registry, scope, cb) {
-  var c = {
+  let username = creds.username || ''
-    u: creds.username || '',
+  let password = creds.password || ''
-    p: creds.password || '',
+  let email = creds.email || ''
-    e: creds.email || ''
+  const auth = {}
-  }
+  if (npm.config.get('otp')) auth.otp = npm.config.get('otp')
  var u = {}
-  chain([
+  return read.username('Username:', username, {log: log}).then((u) => {
-    [readUsername, c, u],
+    username = u
-    [readPassword, c, u],
+    return read.password('Password: ', password)
-    [readEmail, c, u],
+  }).then((p) => {
-    [save, c, u, registry, scope]
+    password = p
-  ], function (err, res) {
+    return read.email('Email: (this IS public) ', email, {log: log})
-    cb(err, res && res[res.length - 1])
+  }).then((e) => {
-  })
+    email = e
-}
+    return profile.login(username, password, {registry: registry, auth: auth}).catch((err) => {
-
+      if (err.code === 'EOTP') throw err
-function readUsername (c, u, cb) {
+      return profile.adduser(username, email, password, {registry: registry})
-  var v = userValidate.username
+    }).catch((err) => {
-  read({prompt: 'Username: ', default: c.u || ''}, function (er, un) {
+      if (err.code === 'EOTP' && !auth.otp) {
-    if (er) {
+        return read.otp('Authenicator provided OTP:').then((otp) => {
-      return cb(er.message === 'cancelled' ? er.message : er)
+          auth.otp = otp
          return profile.login(username, password, {registry: registry, auth: auth})
        })
      } else {
        throw err
      }
    })
  }).then((result) => {
    const newCreds = {}
    if (result && result.token) {
      newCreds.token = result.token
    } else {
      newCreds.username = username
      newCreds.password = password
      newCreds.email = email
      newCreds.alwaysAuth = npm.config.get('always-auth')
    }
-    // make sure it's valid.  we have to do this here, because
+    log.info('adduser', 'Authorized user %s', username)
-    // couchdb will only ever say "bad password" with a 401 when
+    const scopeMessage = scope ? ' to scope ' + scope : ''
-    // you try to PUT a _users record that the validate_doc_update
+    output('Logged in as %s%s on %s.', username, scopeMessage, registry)
    // rejects for *any* reason.
    if (!un) {
      return readUsername(c, u, cb)
    }
    var error = v(un)
    if (error) {
      log.warn(error.message)
      return readUsername(c, u, cb)
    }
    c.changed = c.u !== un
    u.u = un
    cb(er)
  })
 }
 function readPassword (c, u, cb) {
  var v = userValidate.pw
  var prompt
  if (c.p && !c.changed) {
    prompt = 'Password: (or leave unchanged) '
  } else {
    prompt = 'Password: '
  }
  read({prompt: prompt, silent: true}, function (er, pw) {
    if (er) {
      return cb(er.message === 'cancelled' ? er.message : er)
    }
    if (!c.changed && pw === '') {
      // when the username was not changed,
      // empty response means "use the old value"
      pw = c.p
    }
    if (!pw) {
      return readPassword(c, u, cb)
    }
    var error = v(pw)
    if (error) {
      log.warn(error.message)
      return readPassword(c, u, cb)
    }
    c.changed = c.changed || c.p !== pw
    u.p = pw
    cb(er)
  })
 }
 function readEmail (c, u, cb) {
  var v = userValidate.email
  var r = { prompt: 'Email: (this IS public) ', default: c.e || '' }
  read(r, function (er, em) {
    if (er) {
      return cb(er.message === 'cancelled' ? er.message : er)
    }
    if (!em) {
      return readEmail(c, u, cb)
    }
    var error = v(em)
    if (error) {
      log.warn(error.message)
      return readEmail(c, u, cb)
    }
    u.e = em
    cb(er)
  })
 }
 function save (c, u, registry, scope, cb) {
  var params = {
    auth: {
      username: u.u,
      password: u.p,
      email: u.e
    }
  }
  npm.registry.adduser(registry, params, function (er, doc) {
    if (er) return cb(er)
    var newCreds = (doc && doc.token)
    ? {
      token: doc.token
    }
    : {
      username: u.u,
      password: u.p,
      email: u.e,
      alwaysAuth: npm.config.get('always-auth')
    }
    log.info('adduser', 'Authorized user %s', u.u)
    var scopeMessage = scope ? ' to scope ' + scope : ''
    output('Logged in as %s%s on %s.', u.u, scopeMessage, registry)
    cb(null, newCreds)
-  })
+  }).catch(cb)
 }
--- a/deps/npm/lib/build.js
+++ b/deps/npm/lib/build.js
@ -18,6 +18,8 @@ var link = require('./utils/link.js')
 var linkIfExists = link.ifExists
 var cmdShim = require('cmd-shim')
 var cmdShimIfExists = cmdShim.ifExists
 var isHashbangFile = require('./utils/is-hashbang-file.js')
 var dos2Unix = require('./utils/convert-line-endings.js').dos2Unix
 var asyncMap = require('slide').asyncMap
 var ini = require('ini')
 var writeFile = require('write-file-atomic')
@ -187,13 +189,18 @@ function linkBins (pkg, folder, parent, gtop, cb) {
          if (er && er.code === 'ENOENT' && npm.config.get('ignore-scripts')) {
            return cb()
          }
-          if (er || !gtop) return cb(er)
+          if (er) return cb(er)
-          var dest = path.resolve(binRoot, b)
+          isHashbangFile(src).then((isHashbang) => {
-          var out = npm.config.get('parseable')
+            if (isHashbang) return dos2Unix(src)
-                  ? dest + '::' + src + ':BINFILE'
+          }).then(() => {
-                  : dest + ' -> ' + src
+            if (!gtop) return cb()
-          if (!npm.config.get('json') && !npm.config.get('parseable')) output(out)
+            var dest = path.resolve(binRoot, b)
-          cb()
+            var out = npm.config.get('parseable')
                    ? dest + '::' + src + ':BINFILE'
                    : dest + ' -> ' + src
            if (!npm.config.get('json') && !npm.config.get('parseable')) output(out)
            cb()
          }).catch(cb)
        })
      }
    )
--- a/Show More
+++ b/Show More