diff --git a/deps/npm/AUTHORS b/deps/npm/AUTHORS
index 4b9b627102d6..728ed4cc5f4b 100644
--- a/deps/npm/AUTHORS
+++ b/deps/npm/AUTHORS
@@ -584,3 +584,20 @@ Geoffrey Mattie
Luis Lobo Borobia
Aaron Tribou
刘祺
+Brad Johnson
+Artem Varaksa
+Mary
+Darryl Pogue
+Rick Schubert
+Daniel W
+XhmikosR
+Martin Kühl
+Valentin Ouvrard
+Noah Benham
+Brian Olore
+Mat Warger
+Federico Rampazzo
+SneakyFish5 <32284796+SneakyFish5@users.noreply.github.com>
+Nikki Everett
+Erik Price
+Lars Willighagen
diff --git a/deps/npm/CHANGELOG.md b/deps/npm/CHANGELOG.md
index f07b39a2e556..85778a9dceff 100644
--- a/deps/npm/CHANGELOG.md
+++ b/deps/npm/CHANGELOG.md
@@ -1,3 +1,275 @@
+## v6.4.1 (2018-08-22):
+
+### BUGFIXES
+
+* [`4bd40f543`](https://github.com/npm/cli/commit/4bd40f543dc89f0721020e7d0bb3497300d74818)
+ [#42](https://github.com/npm/cli/pull/42)
+ Prevent blowing up on malformed responses from the `npm audit` endpoint, such
+ as with third-party registries.
+ ([@framp](https://github.com/framp))
+* [`0e576f0aa`](https://github.com/npm/cli/commit/0e576f0aa6ea02653d948c10f29102a2d4a31944)
+ [#46](https://github.com/npm/cli/pull/46)
+ Fix `NO_PROXY` support by renaming npm-side config to `--noproxy`. The
+ environment variable should still work.
+ ([@SneakyFish5](https://github.com/SneakyFish5))
+* [`d8e811d6a`](https://github.com/npm/cli/commit/d8e811d6adf3d87474982cb831c11316ac725605)
+ [#33](https://github.com/npm/cli/pull/33)
+ Disable `update-notifier` checks when a CI environment is detected.
+ ([@Sibiraj-S](https://github.com/Sibiraj-S))
+* [`1bc5b8cea`](https://github.com/npm/cli/commit/1bc5b8ceabc86bfe4777732f25ffef0f3de81bd1)
+ [#47](https://github.com/npm/cli/pull/47)
+ Fix issue where `postpack` scripts would break if `pack` was used with
+ `--dry-run`.
+ ([@larsgw](https://github.com/larsgw))
+
+### DEPENDENCY BUMPS
+
+* [`4c57316d5`](https://github.com/npm/cli/commit/4c57316d5633e940105fa545b52d8fbfd2eb9f75)
+ `figgy-pudding@3.4.1`
+ ([@zkat](https://github.com/zkat))
+* [`85f4d7905`](https://github.com/npm/cli/commit/85f4d79059865d5267f3516b6cdbc746012202c6)
+ `cacache@11.2.0`
+ ([@zkat](https://github.com/zkat))
+* [`d20ac242a`](https://github.com/npm/cli/commit/d20ac242aeb44aa3581c65c052802a02d5eb22f3)
+ `npm-packlist@1.1.11`:
+ No real changes in npm-packlist, but npm-bundled included a
+ circular dependency fix, as well as adding a proper LICENSE file.
+ ([@isaacs](https://github.com/isaacs))
+* [`e8d5f4418`](https://github.com/npm/cli/commit/e8d5f441821553a31fc8cd751670663699d2c8ce)
+ [npm.community#632](https://npm.community/t/https://npm.community/t/using-npm-ci-does-not-run-prepare-script-for-git-modules/632)
+ `libcipm@2.0.2`:
+ Fixes issue where `npm ci` wasn't running the `prepare` lifecycle script when
+ installing git dependencies
+ ([@edahlseng](https://github.com/edahlseng))
+* [`a5e6f78e9`](https://github.com/npm/cli/commit/a5e6f78e916873f7d18639ebdb8abd20479615a9)
+ `JSONStream@1.3.4`:
+ Fixes memory leak problem when streaming large files (like legacy npm search).
+ ([@daern91](https://github.com/daern91))
+* [`3b940331d`](https://github.com/npm/cli/commit/3b940331dcccfa67f92366adb7ffd9ecf7673a9a)
+ [npm.community#1042](https://npm.community/t/3-path-variables-are-assigned-to-child-process-launched-by-npm/1042)
+ `npm-lifecycle@2.1.0`:
+ Fixes issue for Windows user where multiple `Path`/`PATH` variables were being
+ added to the environment and breaking things in all sorts of fun and
+ interesting ways.
+ ([@JimiC](https://github.com/JimiC))
+* [`d612d2ce8`](https://github.com/npm/cli/commit/d612d2ce8fab72026f344f125539ecbf3746af9a)
+ `npm-registry-client@8.6.0`
+ ([@iarna](https://github.com/iarna))
+* [`1f6ba1cb1`](https://github.com/npm/cli/commit/1f6ba1cb174590c1f5d2b00e2ca238dfa39d507a)
+ `opener@1.5.0`
+ ([@domenic](https://github.com/domenic))
+* [`37b8f405f`](https://github.com/npm/cli/commit/37b8f405f35c861b7beeed56f71ad20b0bf87889)
+ `request@2.88.0`
+ ([@mikeal](https://github.com/mikeal))
+* [`bb91a2a14`](https://github.com/npm/cli/commit/bb91a2a14562e77769057f1b6d06384be6d6bf7f)
+ `tacks@1.2.7`
+ ([@iarna](https://github.com/iarna))
+* [`30bc9900a`](https://github.com/npm/cli/commit/30bc9900ae79c80bf0bdee0ae6372da6f668124c)
+ `ci-info@1.4.0`:
+ Adds support for two more CI services
+ ([@watson](https://github.com/watson))
+* [`1d2fa4ddd`](https://github.com/npm/cli/commit/1d2fa4dddcab8facfee92096cc24b299387f3182)
+ `marked@0.5.0`
+ ([@joshbruce](https://github.com/joshbruce))
+
+### DOCUMENTATION
+
+* [`08ecde292`](https://github.com/npm/cli/commit/08ecde2928f8c89a2fdaa800ae845103750b9327)
+ [#54](https://github.com/npm/cli/pull/54)
+ Mention registry terms of use in manpage and registry docs and update language
+ in README for it.
+ ([@kemitchell](https://github.com/kemitchell))
+* [`de956405d`](https://github.com/npm/cli/commit/de956405d8b72354f98579d00c6dd30ac3b9bddf)
+ [#41](https://github.com/npm/cli/pull/41)
+ Add documentation for `--dry-run` in `install` and `pack` docs.
+ ([@reconbot](https://github.com/reconbot))
+* [`95031b90c`](https://github.com/npm/cli/commit/95031b90ce0b0c4dcd5e4eafc86e3e5bfd59fb3e)
+ [#48](https://github.com/npm/cli/pull/48)
+ Update republish time and lightly reorganize republish info.
+ ([@neverett](https://github.com/neverett))
+* [`767699b68`](https://github.com/npm/cli/commit/767699b6829b8b899d5479445e99b0ffc43ff92d)
+ [#53](https://github.com/npm/cli/pull/53)
+ Correct `npm@6.4.0` release date in changelog.
+ ([@charmander](https://github.com/charmander))
+* [`3fea3166e`](https://github.com/npm/cli/commit/3fea3166eb4f43f574fcfd9ee71a171feea2bc29)
+ [#55](https://github.com/npm/cli/pull/55)
+ Align command descriptions in help text.
+ ([@erik](https://github.com/erik))
+
+## v6.4.0 (2018-08-09):
+
+### NEW FEATURES
+
+* [`6e9f04b0b`](https://github.com/npm/cli/commit/6e9f04b0baed007169d4e0c341f097cf133debf7)
+ [npm/cli#8](https://github.com/npm/cli/pull/8)
+ Search for authentication token defined by environment variables by preventing
+ the translation layer from env variable to npm option from breaking
+ `:_authToken`.
+ ([@mkhl](https://github.com/mkhl))
+* [`84bfd23e7`](https://github.com/npm/cli/commit/84bfd23e7d6434d30595594723a6e1976e84b022)
+ [npm/cli#35](https://github.com/npm/cli/pull/35)
+ Stop filtering out non-IPv4 addresses from `local-addrs`, making npm actually
+ use IPv6 addresses when it must.
+ ([@valentin2105](https://github.com/valentin2105))
+* [`792c8c709`](https://github.com/npm/cli/commit/792c8c709dc7a445687aa0c8cba5c50bc4ed83fd)
+ [npm/cli#31](https://github.com/npm/cli/pull/31)
+ configurable audit level for non-zero exit
+ `npm audit` currently exits with exit code 1 if any vulnerabilities are found of any level.
+ Add a flag of `--audit-level` to `npm audit` to allow it to pass if only vulnerabilities below a certain level are found.
+ Example: `npm audit --audit-level=high` will exit with 0 if only low or moderate level vulns are detected.
+ ([@lennym](https://github.com/lennym))
+
+### BUGFIXES
+
+* [`d81146181`](https://github.com/npm/cli/commit/d8114618137bb5b9a52a86711bb8dc18bfc8e60c)
+ [npm/cli#32](https://github.com/npm/cli/pull/32)
+ Don't check for updates to npm when we are updating npm itself.
+ ([@olore](https://github.com/olore))
+
+### DEPENDENCY UPDATES
+
+A very special dependency update event! Since the [release of
+`node-gyp@3.8.0`](https://github.com/nodejs/node-gyp/pull/1521), an awkward
+version conflict that was preventing `request` from begin flattened was
+resolved. This means two things:
+
+1. We've cut down the npm tarball size by another 200kb, to 4.6MB
+2. `npm audit` now shows no vulnerabilities for npm itself!
+
+Thanks, [@rvagg](https://github.com/rvagg)!
+
+* [`866d776c2`](https://github.com/npm/cli/commit/866d776c27f80a71309389aaab42825b2a0916f6)
+ `request@2.87.0`
+ ([@simov](https://github.com/simov))
+* [`f861c2b57`](https://github.com/npm/cli/commit/f861c2b579a9d4feae1653222afcefdd4f0e978f)
+ `node-gyp@3.8.0`
+ ([@rvagg](https://github.com/rvagg))
+* [`32e6947c6`](https://github.com/npm/cli/commit/32e6947c60db865257a0ebc2f7e754fedf7a6fc9)
+ [npm/cli#39](https://github.com/npm/cli/pull/39)
+ `colors@1.1.2`:
+ REVERT REVERT, newer versions of this library are broken and print ansi
+ codes even when disabled.
+ ([@iarna](https://github.com/iarna))
+* [`beb96b92c`](https://github.com/npm/cli/commit/beb96b92caf061611e3faafc7ca10e77084ec335)
+ `libcipm@2.0.1`
+ ([@zkat](https://github.com/zkat))
+* [`348fc91ad`](https://github.com/npm/cli/commit/348fc91ad223ff91cd7bcf233018ea1d979a2af1)
+ `validate-npm-package-license@3.0.4`: Fixes errors with empty or string-only
+ license fields.
+ ([@Gudahtt](https://github.com/Gudahtt))
+* [`e57d34575`](https://github.com/npm/cli/commit/e57d3457547ef464828fc6f82ae4750f3e511550)
+ `iferr@1.0.2`
+ ([@shesek](https://github.com/shesek))
+* [`46f1c6ad4`](https://github.com/npm/cli/commit/46f1c6ad4b2fd5b0d7ec879b76b76a70a3a2595c)
+ `tar@4.4.6`
+ ([@isaacs](https://github.com/isaacs))
+* [`50df1bf69`](https://github.com/npm/cli/commit/50df1bf691e205b9f13e0fff0d51a68772c40561)
+ `hosted-git-info@2.7.1`
+ ([@iarna](https://github.com/iarna))
+ ([@Erveon](https://github.com/Erveon))
+ ([@huochunpeng](https://github.com/huochunpeng))
+
+### DOCUMENTATION
+
+* [`af98e76ed`](https://github.com/npm/cli/commit/af98e76ed96af780b544962aa575585b3fa17b9a)
+ [npm/cli#34](https://github.com/npm/cli/pull/34)
+ Remove `npm publish` from list of commands not affected by `--dry-run`.
+ ([@joebowbeer](https://github.com/joebowbeer))
+* [`e2b0f0921`](https://github.com/npm/cli/commit/e2b0f092193c08c00f12a6168ad2bd9d6e16f8ce)
+ [npm/cli#36](https://github.com/npm/cli/pull/36)
+ Tweak formatting in repository field examples.
+ ([@noahbenham](https://github.com/noahbenham))
+* [`e2346e770`](https://github.com/npm/cli/commit/e2346e7702acccefe6d711168c2b0e0e272e194a)
+ [npm/cli#14](https://github.com/npm/cli/pull/14)
+ Used `process.env` examples to make accessing certain `npm run-scripts`
+ environment variables more clear.
+ ([@mwarger](https://github.com/mwarger))
+
+## v6.3.0 (2018-08-01):
+
+This is basically the same as the prerelease, but two dependencies have been
+bumped due to bugs that had been around for a while.
+
+* [`0a22be42e`](https://github.com/npm/cli/commit/0a22be42eb0d40cd0bd87e68c9e28fc9d72c0e19)
+ `figgy-pudding@3.2.0`
+ ([@zkat](https://github.com/zkat))
+* [`0096f6997`](https://github.com/npm/cli/commit/0096f69978d2f40b170b28096f269b0b0008a692)
+ `cacache@11.1.0`
+ ([@zkat](https://github.com/zkat))
+
+## v6.3.0-next.0 (2018-07-25):
+
+### NEW FEATURES
+
+* [`ad0dd226f`](https://github.com/npm/cli/commit/ad0dd226fb97a33dcf41787ae7ff282803fb66f2)
+ [npm/cli#26](https://github.com/npm/cli/pull/26)
+ `npm version` now supports a `--preid` option to specify the preid for
+ prereleases. For example, `npm version premajor --preid rc` will tag a version
+ like `2.0.0-rc.0`.
+ ([@dwilches](https://github.com/dwilches))
+
+### MESSAGING IMPROVEMENTS
+
+* [`c1dad1e99`](https://github.com/npm/cli/commit/c1dad1e994827f2eab7a13c0f6454f4e4c22ebc2)
+ [npm/cli#6](https://github.com/npm/cli/pull/6)
+ Make `npm audit fix` message provide better instructions for vulnerabilities
+ that require manual review.
+ ([@bradsk88](https://github.com/bradsk88))
+* [`15c1130fe`](https://github.com/npm/cli/commit/15c1130fe81961706667d845aad7a5a1f70369f3)
+ Fix missing colon next to tarball url in new `npm view` output.
+ ([@zkat](https://github.com/zkat))
+* [`21cf0ab68`](https://github.com/npm/cli/commit/21cf0ab68cf528d5244ae664133ef400bdcfbdb6)
+ [npm/cli#24](https://github.com/npm/cli/pull/24)
+ Use the defaut OTP explanation everywhere except when the context is
+ "OTP-aware" (like when setting double-authentication). This improves the
+ overall CLI messaging when prompting for an OTP code.
+ ([@jdeniau](https://github.com/jdeniau))
+
+### MISC
+
+* [`a9ac8712d`](https://github.com/npm/cli/commit/a9ac8712dfafcb31a4e3deca24ddb92ff75e942d)
+ [npm/cli#21](https://github.com/npm/cli/pull/21)
+ Use the extracted `stringify-package` package.
+ ([@dpogue](https://github.com/dpogue))
+* [`9db15408c`](https://github.com/npm/cli/commit/9db15408c60be788667cafc787116555507dc433)
+ [npm/cli#27](https://github.com/npm/cli/pull/27)
+ `wrappy` was previously added to dependencies in order to flatten it, but we
+ no longer do legacy-style for npm itself, so it has been removed from
+ `package.json`.
+ ([@rickschubert](https://github.com/rickschubert))
+
+### DOCUMENTATION
+
+* [`3242baf08`](https://github.com/npm/cli/commit/3242baf0880d1cdc0e20b546d3c1da952e474444)
+ [npm/cli#13](https://github.com/npm/cli/pull/13)
+ Update more dead links in README.md.
+ ([@u32i64](https://github.com/u32i64))
+* [`06580877b`](https://github.com/npm/cli/commit/06580877b6023643ec780c19d84fbe120fe5425c)
+ [npm/cli#19](https://github.com/npm/cli/pull/19)
+ Update links in docs' `index.html` to refer to new bug/PR URLs.
+ ([@watilde](https://github.com/watilde))
+* [`ca03013c2`](https://github.com/npm/cli/commit/ca03013c23ff38e12902e9569a61265c2d613738)
+ [npm/cli#15](https://github.com/npm/cli/pull/15)
+ Fix some typos in file-specifiers docs.
+ ([@Mstrodl](https://github.com/Mstrodl))
+* [`4f39f79bc`](https://github.com/npm/cli/commit/4f39f79bcacef11bf2f98d09730bc94d0379789b)
+ [npm/cli#16](https://github.com/npm/cli/pull/16)
+ Fix some typos in file-specifiers and package-lock docs.
+ ([@watilde](https://github.com/watilde))
+* [`35e51f79d`](https://github.com/npm/cli/commit/35e51f79d1a285964aad44f550811aa9f9a72cd8)
+ [npm/cli#18](https://github.com/npm/cli/pull/18)
+ Update build status badge url in README.
+ ([@watilde](https://github.com/watilde))
+* [`a67db5607`](https://github.com/npm/cli/commit/a67db5607ba2052b4ea44f66657f98b758fb4786)
+ [npm/cli#17](https://github.com/npm/cli/pull/17/)
+ Replace TROUBLESHOOTING.md with [posts in
+ npm.community](https://npm.community/c/support/troubleshooting).
+ ([@watilde](https://github.com/watilde))
+* [`e115f9de6`](https://github.com/npm/cli/commit/e115f9de65bf53711266152fc715a5012f7d3462)
+ [npm/cli#7](https://github.com/npm/cli/pull/7)
+ Use https URLs in documentation when appropriate. Happy [Not Secure Day](https://arstechnica.com/gadgets/2018/07/todays-the-day-that-chrome-brands-plain-old-http-as-not-secure/)!
+ ([@XhmikosR](https://github.com/XhmikosR))
+
## v6.2.0 (2018-07-13):
In case you missed it, [we
@@ -13,7 +285,8 @@ quite ready on time but that we'd still like to include. Enjoy!
* [`244b18380`](https://github.com/npm/npm/commit/244b18380ee55950b13c293722771130dbad70de)
[#20554](https://github.com/npm/npm/pull/20554)
- add support for --parseable output
+ Add support for tab-separated output for `npm audit` data with the
+ `--parseable` flag.
([@luislobo](https://github.com/luislobo))
* [`7984206e2`](https://github.com/npm/npm/commit/7984206e2f41b8d8361229cde88d68f0c96ed0b8)
[#12697](https://github.com/npm/npm/pull/12697)
diff --git a/deps/npm/CONTRIBUTING.md b/deps/npm/CONTRIBUTING.md
index f412dc93ed82..3fc4ff5dc7a8 100644
--- a/deps/npm/CONTRIBUTING.md
+++ b/deps/npm/CONTRIBUTING.md
@@ -35,7 +35,7 @@ This includes anyone who may show up to the npm/npm repo with issues, PRs, comme
* Comment on issues when they have a reference to the answer.
* If community members aren't sure they are correct and don't have a reference to the answer, please leave the issue and try another one.
* Defer to collaborators and npm employees for answers.
-* Make sure to search for [the troubleshooting doc](./TROUBLESHOOTING.md) and search on the issue tracker for similar issues before opening a new one.
+* Make sure to search for [the troubleshooting posts on npm.community](https://npm.community/c/support/troubleshooting) and search on the issue tracker for similar issues before opening a new one.
* Any users with urgent support needs are welcome to email support@npmjs.com, and our dedicated support team will be happy to help.
PLEASE don't @ collaborators or npm employees on issues. The CLI team is small, and has many outstanding commitments to fulfill.
diff --git a/deps/npm/README.md b/deps/npm/README.md
index 87aab26d90bc..bb33879fd011 100644
--- a/deps/npm/README.md
+++ b/deps/npm/README.md
@@ -1,7 +1,7 @@
npm(1) -- a JavaScript package manager
==============================
-[](https://travis-ci.org/npm/npm)
+[](https://travis-ci.org/npm/cli)
## SYNOPSIS
@@ -16,17 +16,14 @@ Much more info will be available via `npm help` once it's installed.
To install an old **and unsupported** version of npm that works on node v5
and prior, clone the git repo and dig through the old tags and branches.
-**npm is configured to use npm, Inc.'s public package registry at
- by default.**
+**npm is configured to use npm, Inc.'s public registry at
+ by default.** Use of the npm public registry
+is subject to terms of use available at .
You can configure npm to use any compatible registry you
like, and even run your own registry. Check out the [doc on
registries](https://docs.npmjs.com/misc/registry).
-Use of someone else's registry may be governed by terms of use. The
-terms of use for the default public registry are available at
-.
-
## Super Easy Install
npm is bundled with [node](https://nodejs.org/en/download/).
@@ -88,7 +85,7 @@ experience if you run a recent version of npm. To upgrade, either use [Microsoft
upgrade tool](https://github.com/felixrieseberg/npm-windows-upgrade),
[download a new version of Node](https://nodejs.org/en/download/),
or follow the Windows upgrade instructions in the
-[npm Troubleshooting Guide](./TROUBLESHOOTING.md).
+[Installing/upgrading npm](https://npm.community/t/installing-upgrading-npm/251/2) post.
If that's not fancy enough for you, then you can fetch the code with
git, and mess with it directly.
diff --git a/deps/npm/bin/npm-cli.js b/deps/npm/bin/npm-cli.js
index a38009d276e3..6f76b2382853 100755
--- a/deps/npm/bin/npm-cli.js
+++ b/deps/npm/bin/npm-cli.js
@@ -69,20 +69,25 @@
npm.command = 'help'
}
+ var isGlobalNpmUpdate = conf.global && ['install', 'update'].includes(npm.command) && npm.argv.includes('npm')
+
// now actually fire up npm and run the command.
// this is how to use npm programmatically:
conf._exit = true
npm.load(conf, function (er) {
if (er) return errorHandler(er)
if (
+ !isGlobalNpmUpdate &&
npm.config.get('update-notifier') &&
!unsupported.checkVersion(process.version).unsupported
) {
const pkg = require('../package.json')
let notifier = require('update-notifier')({pkg})
+ const isCI = require('ci-info').isCI
if (
notifier.update &&
- notifier.update.latest !== pkg.version
+ notifier.update.latest !== pkg.version &&
+ !isCI
) {
const color = require('ansicolors')
const useColor = npm.config.get('color')
diff --git a/deps/npm/doc/cli/npm-hook.md b/deps/npm/doc/cli/npm-hook.md
index 34deecaf921b..519287242574 100644
--- a/deps/npm/doc/cli/npm-hook.md
+++ b/deps/npm/doc/cli/npm-hook.md
@@ -48,7 +48,7 @@ $ npm hook rm id-deadbeef
## DESCRIPTION
Allows you to manage [npm
-hooks](http://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm),
+hooks](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm),
including adding, removing, listing, and updating.
Hooks allow you to configure URL endpoints that will be notified whenever a
@@ -69,4 +69,4 @@ request came from your own configured hook.
## SEE ALSO
-* ["Introducing Hooks" blog post](http://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm)
+* ["Introducing Hooks" blog post](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm)
diff --git a/deps/npm/doc/cli/npm-pack.md b/deps/npm/doc/cli/npm-pack.md
index f44f5e3620c2..807663ac210f 100644
--- a/deps/npm/doc/cli/npm-pack.md
+++ b/deps/npm/doc/cli/npm-pack.md
@@ -3,7 +3,7 @@ npm-pack(1) -- Create a tarball from a package
## SYNOPSIS
- npm pack [[<@scope>/]...]
+ npm pack [[<@scope>/]...] [--dry-run]
## DESCRIPTION
@@ -18,6 +18,9 @@ overwritten the second time.
If no arguments are supplied, then npm packs the current package folder.
+The `--dry-run` argument will do everything that pack usually does without
+actually packing anything. Reports on what would have gone into the tarball.
+
## SEE ALSO
* npm-cache(1)
diff --git a/deps/npm/doc/cli/npm-publish.md b/deps/npm/doc/cli/npm-publish.md
index 7e173ec00aff..a317ff45e148 100644
--- 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 [|] [--tag ] [--access ] [--otp otpcode]
+ npm publish [|] [--tag ] [--access ] [--otp otpcode] [--dry-run]
Publishes '.' if no argument supplied
Sets tag 'latest' if no --tag specified
@@ -46,6 +46,10 @@ specifying a different default registry or using a `npm-scope(7)` in the name
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.
+* `[--dry-run]`
+ Does everything publish would do except actually publishing to the registry.
+ Reports the details of what would have been published.
+
Fails if the package name and version combination already exists in
the specified registry.
@@ -57,9 +61,8 @@ As of `npm@5`, both a sha1sum and an integrity field with a sha512sum of the
tarball will be submitted to the registry during publication. Subsequent
installs will use the strongest supported algorithm to verify downloads.
-For a "dry run" that does everything except actually publishing to the
-registry, see `npm-pack(1)`, which figures out the files to be included and
-packs them into a tarball to be uploaded to the registry.
+Similar to `--dry-run` see `npm-pack(1)`, which figures out the files to be
+included and packs them into a tarball to be uploaded to the registry.
## SEE ALSO
diff --git a/deps/npm/doc/cli/npm-run-script.md b/deps/npm/doc/cli/npm-run-script.md
index dc2c93ef9496..18c5736604fa 100644
--- a/deps/npm/doc/cli/npm-run-script.md
+++ b/deps/npm/doc/cli/npm-run-script.md
@@ -15,9 +15,9 @@ used by the test, start, restart, and stop commands, but can be called
directly, as well. When the scripts in the package are printed out, they're
separated into lifecycle (test, start, restart) and directly-run scripts.
-As of [`npm@2.0.0`](http://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
+As of [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
use custom arguments when executing scripts. The special option `--` is used by
-[getopt](http://goo.gl/KxMmtG) to delimit the end of the options. npm will pass
+[getopt](https://goo.gl/KxMmtG) to delimit the end of the options. npm will pass
all the arguments after the `--` directly to your script:
npm run test -- --grep="pattern"
diff --git a/deps/npm/doc/cli/npm-start.md b/deps/npm/doc/cli/npm-start.md
index 94c468c296df..e43f02149935 100644
--- a/deps/npm/doc/cli/npm-start.md
+++ b/deps/npm/doc/cli/npm-start.md
@@ -11,7 +11,7 @@ This runs an arbitrary command specified in the package's `"start"` property of
its `"scripts"` object. If no `"start"` property is specified on the
`"scripts"` object, it will run `node server.js`.
-As of [`npm@2.0.0`](http://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
+As of [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
use custom arguments when executing scripts. Refer to npm-run-script(1) for
more details.
diff --git a/deps/npm/doc/cli/npm-unpublish.md b/deps/npm/doc/cli/npm-unpublish.md
index 57df24d1a0c3..b5b02154e930 100644
--- a/deps/npm/doc/cli/npm-unpublish.md
+++ b/deps/npm/doc/cli/npm-unpublish.md
@@ -24,14 +24,15 @@ If no version is specified, or if all versions are removed then
the root package entry is removed from the registry entirely.
Even if a package version is unpublished, that specific name and
-version combination can never be reused. In order to publish the
-package again, a new version number must be used.
+version combination can never be reused. In order to publish the
+package again, a new version number must be used. Additionally,
+new versions of packages with every version unpublished may not
+be republished until 24 hours have passed.
With the default registry (`registry.npmjs.org`), unpublish is
-only allowed with versions published in the last 72 hours. Similarly,
-new versions of unpublished packages may not be republished until 72 hours
-have passed. If you are trying to unpublish a version published longer
-ago than that, contact support@npmjs.com.
+only allowed with versions published in the last 72 hours. If you
+are trying to unpublish a version published longer ago than that,
+contact support@npmjs.com.
The scope is optional and follows the usual rules for `npm-scope(7)`.
diff --git a/deps/npm/doc/cli/npm-version.md b/deps/npm/doc/cli/npm-version.md
index f1a9bfccda66..4cbc51eddd03 100644
--- a/deps/npm/doc/cli/npm-version.md
+++ b/deps/npm/doc/cli/npm-version.md
@@ -3,7 +3,7 @@ npm-version(1) -- Bump a package version
## SYNOPSIS
- npm version [ | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git]
+ npm version [ | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=] | from-git]
'npm [-v | --version]' to print npm version
'npm view version' to view a package's published version
diff --git a/deps/npm/doc/cli/npm.md b/deps/npm/doc/cli/npm.md
index 82f78a0f9b94..32384547bcb0 100644
--- a/deps/npm/doc/cli/npm.md
+++ b/deps/npm/doc/cli/npm.md
@@ -21,6 +21,16 @@ programs.
Run `npm help` to get a list of available commands.
+## IMPORTANT
+
+npm is configured to use npm, Inc.'s public registry at
+https://registry.npmjs.org by default. Use of the npm public registry is
+subject to terms of use available at https://www.npmjs.com/policies/terms.
+
+You can configure npm to use any compatible registry you like, and even run
+your own registry. Use of someone else's registry may be governed by their
+terms of use.
+
## INTRODUCTION
You probably got npm because you want to install stuff.
@@ -140,7 +150,7 @@ reproduction to report.
[Isaac Z. Schlueter](http://blog.izs.me/) ::
[isaacs](https://github.com/isaacs/) ::
-[@izs](http://twitter.com/izs) ::
+[@izs](https://twitter.com/izs) ::
## SEE ALSO
diff --git a/deps/npm/doc/files/package.json.md b/deps/npm/doc/files/package.json.md
index d1fbe525418a..dd6492af0843 100644
--- a/deps/npm/doc/files/package.json.md
+++ b/deps/npm/doc/files/package.json.md
@@ -106,7 +106,7 @@ Ideally you should pick one that is
[OSI](https://opensource.org/licenses/alphabetical) approved.
If your package is licensed under multiple common licenses, use an [SPDX license
-expression syntax version 2.0 string](https://npmjs.com/package/spdx), like this:
+expression syntax version 2.0 string](https://www.npmjs.com/package/spdx), like this:
{ "license" : "(ISC OR GPL-3.0)" }
@@ -366,15 +366,15 @@ command will be able to find you.
Do it like this:
- "repository" :
- { "type" : "git"
- , "url" : "https://github.com/npm/cli.git"
- }
+ "repository": {
+ "type" : "git",
+ "url" : "https://github.com/npm/cli.git"
+ }
- "repository" :
- { "type" : "svn"
- , "url" : "https://v8.googlecode.com/svn/trunk/"
- }
+ "repository": {
+ "type" : "svn",
+ "url" : "https://v8.googlecode.com/svn/trunk/"
+ }
The URL should be a publicly available (perhaps read-only) url that can be handed
directly to a VCS program without any modification. It should not be a url to an
@@ -608,7 +608,7 @@ Trying to install another plugin with a conflicting requirement will cause an
error. For this reason, make sure your plugin requirement is as broad as
possible, and not to lock it down to specific patch versions.
-Assuming the host complies with [semver](http://semver.org/), only changes in
+Assuming the host complies with [semver](https://semver.org/), only changes in
the host package's major version will break your plugin. Thus, if you've worked
with every 1.x version of the host package, use `"^1.0"` or `"1.x"` to express
this. If you depend on features introduced in 1.5.2, use `">= 1.5.2 < 2"`.
diff --git a/deps/npm/doc/misc/npm-config.md b/deps/npm/doc/misc/npm-config.md
index 45aaf9be9df2..8f04a76010c1 100644
--- a/deps/npm/doc/misc/npm-config.md
+++ b/deps/npm/doc/misc/npm-config.md
@@ -164,6 +164,14 @@ When "true" submit audit reports alongside `npm install` runs to the default
registry and all registries configured for scopes. See the documentation
for npm-audit(1) for details on what is submitted.
+### audit-level
+
+* Default: `"low"`
+* Type: `'low'`, `'moderate'`, `'high'`, `'critical'`
+
+The minimum level of vulnerability for `npm audit` to exit with
+a non-zero exit code.
+
### auth-type
* Default: `'legacy'`
@@ -331,8 +339,8 @@ Install `dev-dependencies` along with packages.
Indicates that you don't want npm to make any changes and that it should
only report what it would have done. This can be passed into any of the
commands that modify your local installation, eg, `install`, `update`,
-`dedupe`, `uninstall`. This is NOT currently honored by network related
-commands, eg `dist-tags`, `owner`, `publish`, etc.
+`dedupe`, `uninstall`. This is NOT currently honored by some network related
+commands, eg `dist-tags`, `owner`, etc.
### editor
@@ -684,7 +692,7 @@ impact how lifecycle scripts are called.
The node version to use when checking a package's `engines` map.
-### no-proxy
+### noproxy
* Default: null
* Type: String or Array
@@ -798,6 +806,14 @@ for updates immediately even for fresh package data.
The location to install global items. If set on the command line, then
it forces non-global commands to run in the specified folder.
+### preid
+
+* Default: ""
+* Type: String
+
+The "prerelease identifier" to use as a prefix for the "prerelease" part of a
+semver. Like the `rc` in `1.2.0-rc.8`.
+
### production
* Default: false
diff --git a/deps/npm/doc/misc/npm-disputes.md b/deps/npm/doc/misc/npm-disputes.md
index 2d8885ecfe27..8c9f0489f923 100644
--- a/deps/npm/doc/misc/npm-disputes.md
+++ b/deps/npm/doc/misc/npm-disputes.md
@@ -102,8 +102,8 @@ here to help.**
If you think another npm publisher is infringing your trademark, such as by
using a confusingly similar package name, email with a link to
-the package or user account on [https://npmjs.com](https://npmjs.com). Attach a
-copy of your trademark registration certificate.
+the package or user account on [https://www.npmjs.com/](https://www.npmjs.com/).
+Attach a copy of your trademark registration certificate.
If we see that the package's publisher is intentionally misleading others by
misusing your registered mark without permission, we will transfer the package
diff --git a/deps/npm/doc/misc/npm-registry.md b/deps/npm/doc/misc/npm-registry.md
index ee8ecc147906..ffbf0214bbf8 100644
--- a/deps/npm/doc/misc/npm-registry.md
+++ b/deps/npm/doc/misc/npm-registry.md
@@ -7,12 +7,20 @@ To resolve packages by name and version, npm talks to a registry website
that implements the CommonJS Package Registry specification for reading
package info.
-Additionally, npm's package registry implementation supports several
+npm is configured to use npm, Inc.'s public registry at
+ by default. Use of the npm public registry is
+subject to terms of use available at .
+
+You can configure npm to use any compatible registry you like, and even run
+your own registry. Use of someone else's registry may be governed by their
+terms of use.
+
+npm's package registry implementation supports several
write APIs as well, to allow for publishing packages and managing user
account information.
-The official public npm registry is at . It
-is powered by a CouchDB database, of which there is a public mirror at
+The npm public registry is powered by a CouchDB database,
+of which there is a public mirror at
. The code for the couchapp is
available at .
@@ -81,7 +89,7 @@ effectively implement the entire CouchDB API anyway.
## Is there a website or something to see package docs and such?
-Yes, head over to
+Yes, head over to
## SEE ALSO
diff --git a/deps/npm/doc/misc/npm-scripts.md b/deps/npm/doc/misc/npm-scripts.md
index 259bf28a6b7e..9ceb7f2c43a5 100644
--- a/deps/npm/doc/misc/npm-scripts.md
+++ b/deps/npm/doc/misc/npm-scripts.md
@@ -143,7 +143,9 @@ The package.json fields are tacked onto the `npm_package_` prefix. So,
for instance, if you had `{"name":"foo", "version":"1.2.5"}` in your
package.json file, then your package scripts would have the
`npm_package_name` environment variable set to "foo", and the
-`npm_package_version` set to "1.2.5"
+`npm_package_version` set to "1.2.5". You can access these variables
+in your code with `process.env.npm_package_name` and
+`process.env.npm_package_version`, and so on for other fields.
### configuration
diff --git a/deps/npm/doc/spec/file-specifiers.md b/deps/npm/doc/spec/file-specifiers.md
index 226f6d013672..e737909db525 100644
--- a/deps/npm/doc/spec/file-specifiers.md
+++ b/deps/npm/doc/spec/file-specifiers.md
@@ -14,7 +14,7 @@ URLs and URL-like strings for other types.
slashes on a file specifier will be removed, that is 'file://../foo/bar`
references the same package as same as `file:../foo/bar`. The latter is
considered canonical.
-* Attempting to install a specifer that has a windows drive letter will
+* Attempting to install a specifier that has a windows drive letter will
produce an error on non-Windows systems.
* A valid `file:` specifier points is:
* a valid package file. That is, a `.tar`, `.tar.gz` or `.tgz` containing
@@ -55,16 +55,13 @@ note for the `npm-shrinkwrap.json` as it means the specifier there will
be different then the original `package.json` (where it was relative to that
`package.json`).
-# No, for `file:` type specifiers, we SHOULD shrinkwrap. Other symlinks we
-# should not. Other symlinks w/o the link spec should be an error.
-
When shrinkwrapping file specifiers, the contents of the destination
package's `node_modules` WILL NOT be included in the shrinkwrap. If you want to lock
down the destination package's `node_modules` you should create a shrinkwrap for it
separately.
This is necessary to support the mono repo use case where many projects file
-to the same package. If each project included its own npm-shrinkwrap.json
+to the same package. If each project included its own `npm-shrinkwrap.json`
then they would each have their own distinct set of transitive dependencies
and they'd step on each other any time you ran an install in one or the other.
@@ -75,7 +72,7 @@ shrinkwrapped packages.
#### File type specifiers pointing at tarballs
-File-type specifiers pointing at a `.tgz` or `.tar.gz or `.tar` file will
+File-type specifiers pointing at a `.tgz` or `.tar.gz` or `.tar` file will
install it as a package file in the same way we would a remote tarball. The
checksum of the package file should be recorded so that we can check for updates.
@@ -134,7 +131,7 @@ example-package@1.0.0 /path/to/example-package
+-- a -> file:../a
```
-Of note here: No version is included as the relavent detail is WHERE the
+Of note here: No version is included as the relevant detail is WHERE the
package came from, not what version happened to be in that path.
### Outdated
diff --git a/deps/npm/doc/spec/package-lock.md b/deps/npm/doc/spec/package-lock.md
index e1cc6941aee3..9da5d8c03b45 100644
--- a/deps/npm/doc/spec/package-lock.md
+++ b/deps/npm/doc/spec/package-lock.md
@@ -269,7 +269,7 @@ nothing requires it any more.
## Additional fields / Adding new fields
Installers should ignore any field they aren't aware of. It's not an error
-to have additional properities in the package-lock or lock file.
+to have additional properties in the package-lock or lock file.
Installers that want to add new fields should either have one added via RFC
in the npm issue tracker and an accompanying documentation PR, or should prefix
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html
index af5ea2e6833b..e51860982c8b 100644
--- a/deps/npm/html/doc/README.html
+++ b/deps/npm/html/doc/README.html
@@ -10,7 +10,7 @@
a JavaScript package manager
-

+

SYNOPSIS
This is just enough info to get you up and running.
Much more info will be available via npm help once it's installed.
@@ -18,14 +18,12 @@
IMPORTANT
You need node v6 or higher to run this program.
To install an old and unsupported version of npm that works on node v5
and prior, clone the git repo and dig through the old tags and branches.
-
npm is configured to use npm, Inc.'s public package registry at
-https://registry.npmjs.org by default.
+
npm is configured to use npm, Inc.'s public registry at
+https://registry.npmjs.org by default. Use of the npm public registry
+is subject to terms of use available at https://www.npmjs.com/policies/terms.
You can configure npm to use any compatible registry you
like, and even run your own registry. Check out the doc on
registries.
-
Use of someone else's registry may be governed by terms of use. The
-terms of use for the default public registry are available at
-https://www.npmjs.com.
Super Easy Install
npm is bundled with node.
Windows Computers
@@ -59,7 +57,7 @@
Windows Install or Upgrade
upgrade tool,
download a new version of Node,
or follow the Windows upgrade instructions in the
-
npm Troubleshooting Guide.
+
Installing/upgrading npm post.
If that's not fancy enough for you, then you can fetch the code with
git, and mess with it directly.
Installing on Cygwin
@@ -120,5 +118,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html
index 3a06cf4cea40..400f553575d7 100644
--- a/deps/npm/html/doc/cli/npm-access.html
+++ b/deps/npm/html/doc/cli/npm-access.html
@@ -85,5 +85,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html
index 448b0849be5f..f7fd77ec7aa2 100644
--- a/deps/npm/html/doc/cli/npm-adduser.html
+++ b/deps/npm/html/doc/cli/npm-adduser.html
@@ -78,5 +78,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-audit.html b/deps/npm/html/doc/cli/npm-audit.html
index e8da37b2b18e..4209a09146aa 100644
--- a/deps/npm/html/doc/cli/npm-audit.html
+++ b/deps/npm/html/doc/cli/npm-audit.html
@@ -81,4 +81,4 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html
index 5f06b80fb019..8a332b6fc778 100644
--- a/deps/npm/html/doc/cli/npm-bin.html
+++ b/deps/npm/html/doc/cli/npm-bin.html
@@ -34,5 +34,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html
index 723d28de2a06..da9aa642c42c 100644
--- a/deps/npm/html/doc/cli/npm-bugs.html
+++ b/deps/npm/html/doc/cli/npm-bugs.html
@@ -54,5 +54,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html
index 6b69efcf1a27..07112d069c44 100644
--- a/deps/npm/html/doc/cli/npm-build.html
+++ b/deps/npm/html/doc/cli/npm-build.html
@@ -38,5 +38,5 @@
DESCRIPTION
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html
index 02977001c601..9c5145e05f26 100644
--- a/deps/npm/html/doc/cli/npm-bundle.html
+++ b/deps/npm/html/doc/cli/npm-bundle.html
@@ -31,5 +31,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html
index bc76fc61aca1..4b40521edc7a 100644
--- a/deps/npm/html/doc/cli/npm-cache.html
+++ b/deps/npm/html/doc/cli/npm-cache.html
@@ -88,5 +88,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-ci.html b/deps/npm/html/doc/cli/npm-ci.html
index de65c01cb9c2..3d3bc579e1f7 100644
--- a/deps/npm/html/doc/cli/npm-ci.html
+++ b/deps/npm/html/doc/cli/npm-ci.html
@@ -57,4 +57,4 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html
index badfceefb633..7421c363f031 100644
--- a/deps/npm/html/doc/cli/npm-completion.html
+++ b/deps/npm/html/doc/cli/npm-completion.html
@@ -41,5 +41,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-config.html b/deps/npm/html/doc/cli/npm-config.html
index 7141ac0da2f6..c5dd0eff4f17 100644
--- a/deps/npm/html/doc/cli/npm-config.html
+++ b/deps/npm/html/doc/cli/npm-config.html
@@ -62,5 +62,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-dedupe.html b/deps/npm/html/doc/cli/npm-dedupe.html
index b31aeb5d804c..377cf0fe7d70 100644
--- a/deps/npm/html/doc/cli/npm-dedupe.html
+++ b/deps/npm/html/doc/cli/npm-dedupe.html
@@ -58,5 +58,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-deprecate.html b/deps/npm/html/doc/cli/npm-deprecate.html
index 311915d164d2..6c91f2a7e686 100644
--- a/deps/npm/html/doc/cli/npm-deprecate.html
+++ b/deps/npm/html/doc/cli/npm-deprecate.html
@@ -36,5 +36,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-dist-tag.html b/deps/npm/html/doc/cli/npm-dist-tag.html
index b35d13d372f1..ef658d5a234c 100644
--- a/deps/npm/html/doc/cli/npm-dist-tag.html
+++ b/deps/npm/html/doc/cli/npm-dist-tag.html
@@ -85,5 +85,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html
index 1bd87813604f..4fbfc3e1a111 100644
--- a/deps/npm/html/doc/cli/npm-docs.html
+++ b/deps/npm/html/doc/cli/npm-docs.html
@@ -55,5 +55,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-doctor.html b/deps/npm/html/doc/cli/npm-doctor.html
index b9c7013d4166..062ed24cd49c 100644
--- a/deps/npm/html/doc/cli/npm-doctor.html
+++ b/deps/npm/html/doc/cli/npm-doctor.html
@@ -102,4 +102,4 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-edit.html b/deps/npm/html/doc/cli/npm-edit.html
index 7cb880067cc3..7b809aefca39 100644
--- a/deps/npm/html/doc/cli/npm-edit.html
+++ b/deps/npm/html/doc/cli/npm-edit.html
@@ -48,5 +48,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-explore.html b/deps/npm/html/doc/cli/npm-explore.html
index f23ba068590b..8a1a92c59354 100644
--- a/deps/npm/html/doc/cli/npm-explore.html
+++ b/deps/npm/html/doc/cli/npm-explore.html
@@ -47,5 +47,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-help-search.html b/deps/npm/html/doc/cli/npm-help-search.html
index 67068704cc1a..cfea82075b8f 100644
--- a/deps/npm/html/doc/cli/npm-help-search.html
+++ b/deps/npm/html/doc/cli/npm-help-search.html
@@ -44,5 +44,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-help.html b/deps/npm/html/doc/cli/npm-help.html
index 642cd3cc2ca9..0535f69bfba3 100644
--- a/deps/npm/html/doc/cli/npm-help.html
+++ b/deps/npm/html/doc/cli/npm-help.html
@@ -49,5 +49,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-hook.html b/deps/npm/html/doc/cli/npm-hook.html
index fbf86ab30017..283aeab5d074 100644
--- a/deps/npm/html/doc/cli/npm-hook.html
+++ b/deps/npm/html/doc/cli/npm-hook.html
@@ -23,7 +23,7 @@
SYNOPSIS
$ npm hook ls lodash
Update an existing hook's url:
$ npm hook update id-deadbeef https://my-new-website.here/
Remove a hook:
$ npm hook rm id-deadbeef
DESCRIPTION
-
Allows you to manage npm
+Allows you to manage npm
hooks,
including adding, removing, listing, and updating.
Hooks allow you to configure URL endpoints that will be notified whenever a
@@ -38,7 +38,7 @@
SYNOPSIS
request came from your own configured hook.
SEE ALSO
@@ -52,4 +52,4 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-init.html b/deps/npm/html/doc/cli/npm-init.html
index 475f98b7cefc..373fcad6b96f 100644
--- a/deps/npm/html/doc/cli/npm-init.html
+++ b/deps/npm/html/doc/cli/npm-init.html
@@ -61,5 +61,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-install-ci-test.html b/deps/npm/html/doc/cli/npm-install-ci-test.html
index c18e8da1f3c4..c7aecb2c9265 100644
--- a/deps/npm/html/doc/cli/npm-install-ci-test.html
+++ b/deps/npm/html/doc/cli/npm-install-ci-test.html
@@ -32,4 +32,4 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-install-test.html b/deps/npm/html/doc/cli/npm-install-test.html
index 23ca987f90ee..cbc70324cc38 100644
--- a/deps/npm/html/doc/cli/npm-install-test.html
+++ b/deps/npm/html/doc/cli/npm-install-test.html
@@ -41,5 +41,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html
index 39ee8ce902c5..979e317612ea 100644
--- a/deps/npm/html/doc/cli/npm-install.html
+++ b/deps/npm/html/doc/cli/npm-install.html
@@ -70,9 +70,11 @@ SYNOPSIS
using npm link.
Tarball requirements:
-- The filename must use
.tar, .tar.gz, or .tgz as
-the extension.
-- The package contents should reside in a subfolder inside the tarball (usually it is called
package/). npm strips one directory layer when installing the package (an equivalent of tar x --strip-components=1 is run).
+The filename must use .tar, .tar.gz, or .tgz as
+the extension.
+
+The package contents should reside in a subfolder inside the tarball (usually it is called package/). npm strips one directory layer when installing the package (an equivalent of tar x --strip-components=1 is run).
+
The package must contain a package.json file with name and version properties.
Example:
npm install ./package.tgz
@@ -170,12 +172,18 @@ SYNOPSIS
The following git environment variables are recognized by npm and will be
added to the environment when running git:
-GIT_ASKPASS
-GIT_EXEC_PATH
-GIT_PROXY_COMMAND
-GIT_SSH
-GIT_SSH_COMMAND
-GIT_SSL_CAINFO
+GIT_ASKPASS
+
+GIT_EXEC_PATH
+
+GIT_PROXY_COMMAND
+
+GIT_SSH
+
+GIT_SSH_COMMAND
+
+GIT_SSL_CAINFO
+
GIT_SSL_NO_VERIFY
See the git man page for details.
Examples:
@@ -362,5 +370,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html
index f8e409541a81..79083759c8cf 100644
--- a/deps/npm/html/doc/cli/npm-link.html
+++ b/deps/npm/html/doc/cli/npm-link.html
@@ -71,5 +71,5 @@ SYNOPSIS
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-logout.html b/deps/npm/html/doc/cli/npm-logout.html
index a709374d6f5c..b8c3247dd384 100644
--- a/deps/npm/html/doc/cli/npm-logout.html
+++ b/deps/npm/html/doc/cli/npm-logout.html
@@ -49,5 +49,5 @@ scope
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html
index d2391791d1f9..a4fadf88671a 100644
--- a/deps/npm/html/doc/cli/npm-ls.html
+++ b/deps/npm/html/doc/cli/npm-ls.html
@@ -20,7 +20,7 @@ SYNOPSIS
limit the results to only the paths to the packages named. Note that
nested packages will also show the paths to the specified packages.
For example, running npm ls promzard in npm's source tree will show:
-npm@6.2.0 /path/to/npm
+npm@6.4.1 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
It will print out extraneous, missing, and invalid packages.
If a project specifies git urls for dependencies these are shown
@@ -108,5 +108,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html
index f2ae7faa3460..dc847796e84c 100644
--- a/deps/npm/html/doc/cli/npm-outdated.html
+++ b/deps/npm/html/doc/cli/npm-outdated.html
@@ -114,5 +114,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html
index 4e5485c6fa9e..f439c815afa6 100644
--- a/deps/npm/html/doc/cli/npm-owner.html
+++ b/deps/npm/html/doc/cli/npm-owner.html
@@ -53,5 +53,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html
index c3d49981dae3..5727914b61ca 100644
--- a/deps/npm/html/doc/cli/npm-pack.html
+++ b/deps/npm/html/doc/cli/npm-pack.html
@@ -11,7 +11,7 @@
Create a tarball from a package
SYNOPSIS
-npm pack [[<@scope>/]<pkg>...]
DESCRIPTION
+npm pack [[<@scope>/]<pkg>...] [--dry-run]
DESCRIPTION
For anything that's installable (that is, a package folder, tarball,
tarball url, name@tag, name@version, name, or scoped name), this
command will fetch it to the cache, and then copy the tarball to the
@@ -20,6 +20,8 @@
SYNOPSIS
If the same package is specified multiple times, then the file will be
overwritten the second time.
If no arguments are supplied, then npm packs the current package folder.
+The --dry-run argument will do everything that pack usually does without
+actually packing anything. Reports on what would have gone into the tarball.
SEE ALSO
- npm-cache(1)
@@ -40,5 +42,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html
index 4687d1125525..1177eef2474e 100644
--- a/deps/npm/html/doc/cli/npm-ping.html
+++ b/deps/npm/html/doc/cli/npm-ping.html
@@ -33,5 +33,5 @@ SYNOPSIS
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html
index 0aaf04586be4..65dbf19286d2 100644
--- a/deps/npm/html/doc/cli/npm-prefix.html
+++ b/deps/npm/html/doc/cli/npm-prefix.html
@@ -37,5 +37,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-profile.html b/deps/npm/html/doc/cli/npm-profile.html
index 18f07a1fd8b8..3360e3009a2f 100644
--- a/deps/npm/html/doc/cli/npm-profile.html
+++ b/deps/npm/html/doc/cli/npm-profile.html
@@ -88,4 +88,4 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html
index 418ee8805040..9b1922e03a7b 100644
--- a/deps/npm/html/doc/cli/npm-prune.html
+++ b/deps/npm/html/doc/cli/npm-prune.html
@@ -47,5 +47,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html
index 79f751541026..b6819bc0aa0b 100644
--- a/deps/npm/html/doc/cli/npm-publish.html
+++ b/deps/npm/html/doc/cli/npm-publish.html
@@ -11,7 +11,7 @@
Publish a package
SYNOPSIS
-
npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--otp otpcode]
+npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--otp otpcode] [--dry-run]
Publishes '.' if no argument supplied
Sets tag 'latest' if no --tag specified
DESCRIPTION
@@ -49,6 +49,10 @@ SYNOPSIS
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.
+[--dry-run]
+Does everything publish would do except actually publishing to the registry.
+Reports the details of what would have been published.
+
Fails if the package name and version combination already exists in
the specified registry.
@@ -58,9 +62,8 @@ SYNOPSIS
As of npm@5, both a sha1sum and an integrity field with a sha512sum of the
tarball will be submitted to the registry during publication. Subsequent
installs will use the strongest supported algorithm to verify downloads.
-For a "dry run" that does everything except actually publishing to the
-registry, see npm-pack(1), which figures out the files to be included and
-packs them into a tarball to be uploaded to the registry.
+Similar to --dry-run see npm-pack(1), which figures out the files to be
+included and packs them into a tarball to be uploaded to the registry.
SEE ALSO
- npm-registry(7)
@@ -84,5 +87,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html
index 537b3e53dea8..3d574beea0cd 100644
--- a/deps/npm/html/doc/cli/npm-rebuild.html
+++ b/deps/npm/html/doc/cli/npm-rebuild.html
@@ -34,5 +34,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html
index c7a061020d0b..84f4221ee5d3 100644
--- a/deps/npm/html/doc/cli/npm-repo.html
+++ b/deps/npm/html/doc/cli/npm-repo.html
@@ -40,5 +40,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html
index 8a3f8cb3690e..5c25e1581617 100644
--- a/deps/npm/html/doc/cli/npm-restart.html
+++ b/deps/npm/html/doc/cli/npm-restart.html
@@ -52,5 +52,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html
index 3f6821e18e0c..1388f1a3f73f 100644
--- a/deps/npm/html/doc/cli/npm-root.html
+++ b/deps/npm/html/doc/cli/npm-root.html
@@ -34,5 +34,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-run-script.html b/deps/npm/html/doc/cli/npm-run-script.html
index 6dc9539150a0..a4da59791a98 100644
--- a/deps/npm/html/doc/cli/npm-run-script.html
+++ b/deps/npm/html/doc/cli/npm-run-script.html
@@ -19,9 +19,9 @@ SYNOPSIS
used by the test, start, restart, and stop commands, but can be called
directly, as well. When the scripts in the package are printed out, they're
separated into lifecycle (test, start, restart) and directly-run scripts.
-As of npm@2.0.0, you can
+
As of npm@2.0.0, you can
use custom arguments when executing scripts. The special option -- is used by
-getopt to delimit the end of the options. npm will pass
+getopt to delimit the end of the options. npm will pass
all the arguments after the -- directly to your script:
npm run test -- --grep="pattern"
The arguments will only be passed to the script specified after npm run
and not to any pre or post script.
@@ -79,5 +79,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html
index 1015bb9e9633..0a1bf7627b61 100644
--- a/deps/npm/html/doc/cli/npm-search.html
+++ b/deps/npm/html/doc/cli/npm-search.html
@@ -108,5 +108,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html
index 9784d1da249c..2f05e0adab5c 100644
--- a/deps/npm/html/doc/cli/npm-shrinkwrap.html
+++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html
@@ -40,5 +40,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html
index 36325e393165..8410bdd2c27e 100644
--- a/deps/npm/html/doc/cli/npm-star.html
+++ b/deps/npm/html/doc/cli/npm-star.html
@@ -35,5 +35,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html
index c2cdcaf081d5..68b7e7cc3bbd 100644
--- a/deps/npm/html/doc/cli/npm-stars.html
+++ b/deps/npm/html/doc/cli/npm-stars.html
@@ -35,5 +35,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html
index 4d61a463af35..d404e0b4012e 100644
--- a/deps/npm/html/doc/cli/npm-start.html
+++ b/deps/npm/html/doc/cli/npm-start.html
@@ -15,7 +15,7 @@ SYNOPSIS
This runs an arbitrary command specified in the package's "start" property of
its "scripts" object. If no "start" property is specified on the
"scripts" object, it will run node server.js.
-As of npm@2.0.0, you can
+
As of npm@2.0.0, you can
use custom arguments when executing scripts. Refer to npm-run-script(1) for
more details.
SEE ALSO
@@ -38,5 +38,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html
index 8f53a98b5630..aabfdb3c2264 100644
--- a/deps/npm/html/doc/cli/npm-stop.html
+++ b/deps/npm/html/doc/cli/npm-stop.html
@@ -33,5 +33,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html
index f4fb339a881e..1e92c1f8be97 100644
--- a/deps/npm/html/doc/cli/npm-team.html
+++ b/deps/npm/html/doc/cli/npm-team.html
@@ -69,5 +69,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html
index b55953438846..272a7694af4a 100644
--- a/deps/npm/html/doc/cli/npm-test.html
+++ b/deps/npm/html/doc/cli/npm-test.html
@@ -35,5 +35,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-token.html b/deps/npm/html/doc/cli/npm-token.html
index 3c48209cee8b..810bd4c93c3f 100644
--- a/deps/npm/html/doc/cli/npm-token.html
+++ b/deps/npm/html/doc/cli/npm-token.html
@@ -70,4 +70,4 @@ SYNOPSIS
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html
index a935b7b05c3e..9f9656ec233d 100644
--- a/deps/npm/html/doc/cli/npm-uninstall.html
+++ b/deps/npm/html/doc/cli/npm-uninstall.html
@@ -60,5 +60,5 @@ SYNOPSIS
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html
index 6b68e3528b85..0554893fc274 100644
--- a/deps/npm/html/doc/cli/npm-unpublish.html
+++ b/deps/npm/html/doc/cli/npm-unpublish.html
@@ -23,13 +23,14 @@ DESCRIPTION
If no version is specified, or if all versions are removed then
the root package entry is removed from the registry entirely.
Even if a package version is unpublished, that specific name and
-version combination can never be reused. In order to publish the
-package again, a new version number must be used.
+version combination can never be reused. In order to publish the
+package again, a new version number must be used. Additionally,
+new versions of packages with every version unpublished may not
+be republished until 24 hours have passed.
With the default registry (registry.npmjs.org), unpublish is
-only allowed with versions published in the last 72 hours. Similarly,
-new versions of unpublished packages may not be republished until 72 hours
-have passed. If you are trying to unpublish a version published longer
-ago than that, contact support@npmjs.com.
+only allowed with versions published in the last 72 hours. If you
+are trying to unpublish a version published longer ago than that,
+contact support@npmjs.com.
The scope is optional and follows the usual rules for npm-scope(7).
SEE ALSO
@@ -51,5 +52,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html
index 29ed3024167b..d4152688b6a7 100644
--- a/deps/npm/html/doc/cli/npm-update.html
+++ b/deps/npm/html/doc/cli/npm-update.html
@@ -57,8 +57,8 @@ Tilde Dependencies
However, if app's package.json contains:
"dependencies": {
"dep1": "~1.1.1"
-}
In this case, running npm update will install `dep1@1.1.2. Even though thelatesttag points to1.2.2, this version does not satisfy~1.1.1, which is equivalent
-to>=1.1.1 <1.2.0. So the highest-sorting version that satisfies~1.1.1is used,
+}
In this case, running npm update will install `dep1@1.1.2. Even though thelatesttag points to1.2.2, this version does not satisfy1.1.1, which is equivalent
+to>=1.1.1 <1.2.0. So the highest-sorting version that satisfies1.1.1is used,
which is1.1.2`.
Caret Dependencies below 1.0.0
Suppose app has a caret dependency on a version below 1.0.0, for example:
@@ -98,5 +98,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html
index 2432c356106b..41a133c1b67f 100644
--- a/deps/npm/html/doc/cli/npm-version.html
+++ b/deps/npm/html/doc/cli/npm-version.html
@@ -11,7 +11,7 @@
Bump a package version
SYNOPSIS
-npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git]
+npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=<prerelease-id>] | from-git]
'npm [-v | --version]' to print npm version
'npm view <pkg> version' to view a package's published version
@@ -116,5 +116,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html
index 58c7fc1d8a39..415082b82c35 100644
--- a/deps/npm/html/doc/cli/npm-view.html
+++ b/deps/npm/html/doc/cli/npm-view.html
@@ -75,5 +75,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html
index 4a2c5ea50855..7f82454bf79e 100644
--- a/deps/npm/html/doc/cli/npm-whoami.html
+++ b/deps/npm/html/doc/cli/npm-whoami.html
@@ -32,5 +32,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html
index c4bb944deb66..c2c0acda3da7 100644
--- a/deps/npm/html/doc/cli/npm.html
+++ b/deps/npm/html/doc/cli/npm.html
@@ -12,7 +12,7 @@
javascript package manager
SYNOPSIS
npm <command> [args]
VERSION
-6.2.0
+6.4.1
DESCRIPTION
npm is the package manager for the Node JavaScript platform. It puts
modules in place so that node can find them, and manages dependency
@@ -21,6 +21,13 @@
DESCRIPTION
Most commonly, it is used to publish, discover, install, and develop node
programs.
Run npm help to get a list of available commands.
+IMPORTANT
+npm is configured to use npm, Inc.'s public registry at
+https://registry.npmjs.org by default. Use of the npm public registry is
+subject to terms of use available at https://www.npmjs.com/policies/terms.
+You can configure npm to use any compatible registry you like, and even run
+your own registry. Use of someone else's registry may be governed by their
+terms of use.
INTRODUCTION
You probably got npm because you want to install stuff.
Use npm install blerg to install the latest version of "blerg". Check out
@@ -122,8 +129,8 @@
BUGS
AUTHOR
Isaac Z. Schlueter ::
isaacs ::
-@izs ::
-i@izs.me
+@izs ::
+i@izs.me
SEE ALSO
- npm-help(1)
@@ -147,5 +154,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html
index 4a9942d7abb3..95285eead07e 100644
--- a/deps/npm/html/doc/files/npm-folders.html
+++ b/deps/npm/html/doc/files/npm-folders.html
@@ -179,5 +179,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/npm-global.html b/deps/npm/html/doc/files/npm-global.html
index 4a9942d7abb3..95285eead07e 100644
--- a/deps/npm/html/doc/files/npm-global.html
+++ b/deps/npm/html/doc/files/npm-global.html
@@ -179,5 +179,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html
index 0edcca4702e5..5d9a0f79b6c0 100644
--- a/deps/npm/html/doc/files/npm-json.html
+++ b/deps/npm/html/doc/files/npm-json.html
@@ -81,7 +81,7 @@ license
{ "license" : "BSD-3-Clause" }
You can check the full list of SPDX license IDs.
Ideally you should pick one that is
OSI approved.
-If your package is licensed under multiple common licenses, use an SPDX license
+If your package is licensed under multiple common licenses, use an SPDX license
expression syntax version 2.0 string, like this:
{ "license" : "(ISC OR GPL-3.0)" }
If you are using a license that hasn't been assigned an SPDX identifier, or if
you are using a custom license, use a string value like this one:
@@ -256,15 +256,15 @@ repository
want to contribute. If the git repo is on GitHub, then the npm docs
command will be able to find you.
Do it like this:
-"repository" :
- { "type" : "git"
- , "url" : "https://github.com/npm/cli.git"
- }
+"repository": {
+ "type" : "git",
+ "url" : "https://github.com/npm/cli.git"
+}
-"repository" :
- { "type" : "svn"
- , "url" : "https://v8.googlecode.com/svn/trunk/"
- }
The URL should be a publicly available (perhaps read-only) url that can be handed
+"repository": {
+ "type" : "svn",
+ "url" : "https://v8.googlecode.com/svn/trunk/"
+}
The URL should be a publicly available (perhaps read-only) url that can be handed
directly to a VCS program without any modification. It should not be a url to an
html project page that you put in your browser. It's for computers.
For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
@@ -434,7 +434,7 @@
peerDependencies
Trying to install another plugin with a conflicting requirement will cause an
error. For this reason, make sure your plugin requirement is as broad as
possible, and not to lock it down to specific patch versions.
-Assuming the host complies with semver, only changes in
+
Assuming the host complies with semver, only changes in
the host package's major version will break your plugin. Thus, if you've worked
with every 1.x version of the host package, use "^1.0" or "1.x" to express
this. If you depend on features introduced in 1.5.2, use ">= 1.5.2 < 2".
@@ -574,5 +574,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/npm-package-locks.html b/deps/npm/html/doc/files/npm-package-locks.html
index 50ac0d4db804..425d274eb75a 100644
--- a/deps/npm/html/doc/files/npm-package-locks.html
+++ b/deps/npm/html/doc/files/npm-package-locks.html
@@ -151,4 +151,4 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/npm-shrinkwrap.json.html b/deps/npm/html/doc/files/npm-shrinkwrap.json.html
index 66cd483cb46c..0d01fdf56b99 100644
--- a/deps/npm/html/doc/files/npm-shrinkwrap.json.html
+++ b/deps/npm/html/doc/files/npm-shrinkwrap.json.html
@@ -42,4 +42,4 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/npmrc.html b/deps/npm/html/doc/files/npmrc.html
index bdb87a2019a2..eb834506345b 100644
--- a/deps/npm/html/doc/files/npmrc.html
+++ b/deps/npm/html/doc/files/npmrc.html
@@ -82,5 +82,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/package-lock.json.html b/deps/npm/html/doc/files/package-lock.json.html
index 82ccc40dc075..5732969d259f 100644
--- a/deps/npm/html/doc/files/package-lock.json.html
+++ b/deps/npm/html/doc/files/package-lock.json.html
@@ -130,4 +130,4 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/files/package.json.html b/deps/npm/html/doc/files/package.json.html
index 0edcca4702e5..5d9a0f79b6c0 100644
--- a/deps/npm/html/doc/files/package.json.html
+++ b/deps/npm/html/doc/files/package.json.html
@@ -81,7 +81,7 @@ license
{ "license" : "BSD-3-Clause" }
You can check the full list of SPDX license IDs.
Ideally you should pick one that is
OSI approved.
-If your package is licensed under multiple common licenses, use an SPDX license
+If your package is licensed under multiple common licenses, use an SPDX license
expression syntax version 2.0 string, like this:
{ "license" : "(ISC OR GPL-3.0)" }
If you are using a license that hasn't been assigned an SPDX identifier, or if
you are using a custom license, use a string value like this one:
@@ -256,15 +256,15 @@ repository
want to contribute. If the git repo is on GitHub, then the npm docs
command will be able to find you.
Do it like this:
-"repository" :
- { "type" : "git"
- , "url" : "https://github.com/npm/cli.git"
- }
+"repository": {
+ "type" : "git",
+ "url" : "https://github.com/npm/cli.git"
+}
-"repository" :
- { "type" : "svn"
- , "url" : "https://v8.googlecode.com/svn/trunk/"
- }
The URL should be a publicly available (perhaps read-only) url that can be handed
+"repository": {
+ "type" : "svn",
+ "url" : "https://v8.googlecode.com/svn/trunk/"
+}
The URL should be a publicly available (perhaps read-only) url that can be handed
directly to a VCS program without any modification. It should not be a url to an
html project page that you put in your browser. It's for computers.
For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
@@ -434,7 +434,7 @@
peerDependencies
Trying to install another plugin with a conflicting requirement will cause an
error. For this reason, make sure your plugin requirement is as broad as
possible, and not to lock it down to specific patch versions.
-Assuming the host complies with semver, only changes in
+
Assuming the host complies with semver, only changes in
the host package's major version will break your plugin. Thus, if you've worked
with every 1.x version of the host package, use "^1.0" or "1.x" to express
this. If you depend on features introduced in 1.5.2, use ">= 1.5.2 < 2".
@@ -574,5 +574,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/index.html b/deps/npm/html/doc/index.html
index 638ec9a08d70..5fef0c4f9435 100644
--- a/deps/npm/html/doc/index.html
+++ b/deps/npm/html/doc/index.html
@@ -180,5 +180,5 @@
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html
index e8133c1794ad..5f7c24e0648f 100644
--- a/deps/npm/html/doc/misc/npm-coding-style.html
+++ b/deps/npm/html/doc/misc/npm-coding-style.html
@@ -145,5 +145,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html
index fcfbb71f3c86..e27f5fd311b1 100644
--- a/deps/npm/html/doc/misc/npm-config.html
+++ b/deps/npm/html/doc/misc/npm-config.html
@@ -137,6 +137,13 @@ audit
When "true" submit audit reports alongside npm install runs to the default
registry and all registries configured for scopes. See the documentation
for npm-audit(1) for details on what is submitted.
+audit-level
+
+- Default:
"low"
+- Type:
'low', 'moderate', 'high', 'critical'
+
+The minimum level of vulnerability for npm audit to exit with
+a non-zero exit code.
auth-type
- Default:
'legacy'
@@ -272,8 +279,8 @@ dry-run
Indicates that you don't want npm to make any changes and that it should
only report what it would have done. This can be passed into any of the
commands that modify your local installation, eg, install, update,
-dedupe, uninstall. This is NOT currently honored by network related
-commands, eg dist-tags, owner, publish, etc.
+dedupe, uninstall. This is NOT currently honored by some network related
+commands, eg dist-tags, owner, etc.
editor
- Default:
EDITOR environment variable if set, or "vi" on Posix,
@@ -579,7 +586,7 @@ node-version
- Type: semver or false
The node version to use when checking a package's engines map.
-no-proxy
+noproxy
- Default: null
- Type: String or Array
@@ -675,6 +682,13 @@ prefix
The location to install global items. If set on the command line, then
it forces non-global commands to run in the specified folder.
+preid
+
+- Default: ""
+- Type: String
+
+The "prerelease identifier" to use as a prefix for the "prerelease" part of a
+semver. Like the rc in 1.2.0-rc.8.
production
- Default: false
@@ -1050,5 +1064,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html
index 961bf22c4155..5b484ff56417 100644
--- a/deps/npm/html/doc/misc/npm-developers.html
+++ b/deps/npm/html/doc/misc/npm-developers.html
@@ -198,5 +198,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html
index dccfe0394b0d..1c01e4870b13 100644
--- a/deps/npm/html/doc/misc/npm-disputes.html
+++ b/deps/npm/html/doc/misc/npm-disputes.html
@@ -20,7 +20,7 @@ Handling Module
TL;DR
- Get the author email with
npm owner ls <pkgname>
-- Email the author, CC support@npmjs.com
+- Email the author, CC support@npmjs.com
- After a few weeks, if there's no resolution, we'll sort it out.
Don't squat on package names. Publish code or move out of the way.
@@ -29,22 +29,25 @@ DESCRIPTION
some other user wants to use that name. Here are some common ways that happens
(each of these is based on actual events.)
-- Alice writes a JavaScript module
foo, which is not node-specific. Alice
+ Alice writes a JavaScript module foo, which is not node-specific. Alice
doesn't use node at all. Yusuf wants to use foo in node, so he wraps it in
an npm module. Some time later, Alice starts using node, and wants to take
-over management of her program.
-- Yusuf writes an npm module
foo, and publishes it. Perhaps much later, Alice
+over management of her program.
+
+Yusuf writes an npm module foo, and publishes it. Perhaps much later, Alice
finds a bug in foo, and fixes it. She sends a pull request to Yusuf, but
Yusuf doesn't have the time to deal with it, because he has a new job and a
new baby and is focused on his new Erlang project, and kind of not involved
with node any more. Alice would like to publish a new foo, but can't,
-because the name is taken.
-- Yusuf writes a 10-line flow-control library, and calls it
foo, and
+because the name is taken.
+
+Yusuf writes a 10-line flow-control library, and calls it foo, and
publishes it to the npm registry. Being a simple little thing, it never
really has to be updated. Alice works for Foo Inc, the makers of the
critically acclaimed and widely-marketed foo JavaScript toolkit framework.
They publish it to npm as foojs, but people are routinely confused when
-npm install foo is some different thing.
+npm install foo is some different thing.
+
Yusuf writes a parser for the widely-known foo file format, because he
needs it for work. Then, he gets a new job, and never updates the prototype.
Later on, Alice writes a much more complete foo parser, but can't publish,
@@ -53,15 +56,17 @@
DESCRIPTION
npm owner ls foo. This will tell Alice the email address of the owner
(Yusuf).
-- Alice emails Yusuf, explaining the situation as respectfully as possible,
+
Alice emails Yusuf, explaining the situation as respectfully as possible,
and what she would like to do with the module name. She adds the npm support
-staff support@npmjs.com to the CC list of the email. Mention in the email
+staff support@npmjs.com to the CC list of the email. Mention in the email
that Yusuf can run npm owner add alice foo to add Alice as an owner of the
-foo package.
-- After a reasonable amount of time, if Yusuf has not responded, or if Yusuf
+foo package.
+
+After a reasonable amount of time, if Yusuf has not responded, or if Yusuf
and Alice can't come to any sort of resolution, email support
-support@npmjs.com and we'll sort it out. ("Reasonable" is usually at least
-4 weeks.)
+support@npmjs.com and we'll sort it out. ("Reasonable" is usually at least
+4 weeks.)
+
REASONING
In almost every case so far, the parties involved have been able to reach an
@@ -96,14 +101,14 @@
EXCEPTIONS
Code of Conduct such as hateful
language, pornographic content, or harassment.
-If you see bad behavior like this, please report it to abuse@npmjs.com right
+
If you see bad behavior like this, please report it to abuse@npmjs.com right
away. You are never expected to resolve abusive behavior on your own. We are
here to help.
TRADEMARKS
If you think another npm publisher is infringing your trademark, such as by
-using a confusingly similar package name, email abuse@npmjs.com with a link to
-the package or user account on https://npmjs.com. Attach a
-copy of your trademark registration certificate.
+using a confusingly similar package name, email abuse@npmjs.com with a link to
+the package or user account on https://www.npmjs.com/.
+Attach a copy of your trademark registration certificate.
If we see that the package's publisher is intentionally misleading others by
misusing your registered mark without permission, we will transfer the package
name to you. Otherwise, we will contact the package publisher and ask them to
@@ -134,5 +139,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html
index 7c67f1b99ad6..943435719795 100644
--- a/deps/npm/html/doc/misc/npm-index.html
+++ b/deps/npm/html/doc/misc/npm-index.html
@@ -180,5 +180,5 @@
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html
index e2ed0d240ceb..b8529bb6675e 100644
--- a/deps/npm/html/doc/misc/npm-orgs.html
+++ b/deps/npm/html/doc/misc/npm-orgs.html
@@ -77,5 +77,5 @@ Team Admins create teams
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html
index 1a5626646d7f..3c2e8c0a910f 100644
--- a/deps/npm/html/doc/misc/npm-registry.html
+++ b/deps/npm/html/doc/misc/npm-registry.html
@@ -14,11 +14,17 @@ DESCRIPTION
To resolve packages by name and version, npm talks to a registry website
that implements the CommonJS Package Registry specification for reading
package info.
-Additionally, npm's package registry implementation supports several
+
npm is configured to use npm, Inc.'s public registry at
+https://registry.npmjs.org by default. Use of the npm public registry is
+subject to terms of use available at https://www.npmjs.com/policies/terms.
+You can configure npm to use any compatible registry you like, and even run
+your own registry. Use of someone else's registry may be governed by their
+terms of use.
+npm's package registry implementation supports several
write APIs as well, to allow for publishing packages and managing user
account information.
-The official public npm registry is at https://registry.npmjs.org/. It
-is powered by a CouchDB database, of which there is a public mirror at
+
The npm public registry is powered by a CouchDB database,
+of which there is a public mirror at
https://skimdb.npmjs.com/registry. The code for the couchapp is
available at https://github.com/npm/npm-registry-couchapp.
The registry URL used is determined by the scope of the package (see
@@ -69,7 +75,7 @@
Do I
No, but it's way easier. Basically, yes, you do, or you have to
effectively implement the entire CouchDB API anyway.
Is there a website or something to see package docs and such?
-Yes, head over to https://npmjs.com/
+Yes, head over to https://www.npmjs.com/
SEE ALSO
- npm-config(1)
@@ -90,5 +96,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html
index fe4a1abc254b..c8215a590d05 100644
--- a/deps/npm/html/doc/misc/npm-scope.html
+++ b/deps/npm/html/doc/misc/npm-scope.html
@@ -93,5 +93,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html
index d76bba3b61a0..7b333bcf8b2e 100644
--- a/deps/npm/html/doc/misc/npm-scripts.html
+++ b/deps/npm/html/doc/misc/npm-scripts.html
@@ -132,7 +132,9 @@ package.json vars
for instance, if you had {"name":"foo", "version":"1.2.5"} in your
package.json file, then your package scripts would have the
npm_package_name environment variable set to "foo", and the
-npm_package_version set to "1.2.5"
+npm_package_version set to "1.2.5". You can access these variables
+in your code with process.env.npm_package_name and
+process.env.npm_package_version, and so on for other fields.
configuration
Configuration parameters are put in the environment with the
npm_config_ prefix. For instance, you can view the effective root
@@ -232,5 +234,5 @@
SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html
index 3abcf7adb124..989094f9b470 100644
--- a/deps/npm/html/doc/misc/removing-npm.html
+++ b/deps/npm/html/doc/misc/removing-npm.html
@@ -52,5 +52,5 @@ SEE ALSO
| | |
| | | |
-
+
diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html
index 028d50aadeda..24a2d8b28b85 100644
--- a/deps/npm/html/doc/misc/semver.html
+++ b/deps/npm/html/doc/misc/semver.html
@@ -350,5 +350,5 @@ Coercion
| | |
| | | |
-
+
diff --git a/deps/npm/html/index.html b/deps/npm/html/index.html
index bb8681c85c9f..32dd01a34f8e 100644
--- a/deps/npm/html/index.html
+++ b/deps/npm/html/index.html
@@ -56,7 +56,7 @@
npm
-npm is a package manager for node. You can use it to install
+
npm is a package manager for node. You can use it to install
and publish your node programs. It manages dependencies and does other cool stuff.
Easy Zero Line Install
@@ -69,7 +69,7 @@ Easy Zero Line Install
Fancy Install
- - Get the code.
+
- Get the code.
- Do what the README
says to do.
@@ -86,7 +86,7 @@ Other Cool Stuff
- README
- Help Documentation
- Search for Packages
-
- Bugs
+
- Bugs