aboutsummaryrefslogtreecommitdiff
path: root/deps/npm/doc/misc
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/doc/misc')
-rw-r--r--deps/npm/doc/misc/npm-config.md22
-rw-r--r--deps/npm/doc/misc/npm-disputes.md4
-rw-r--r--deps/npm/doc/misc/npm-registry.md16
-rw-r--r--deps/npm/doc/misc/npm-scripts.md4
4 files changed, 36 insertions, 10 deletions
diff --git a/deps/npm/doc/misc/npm-config.md b/deps/npm/doc/misc/npm-config.md
index 45aaf9be9d..8f04a76010 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 2d8885ecfe..8c9f0489f9 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 <abuse@npmjs.com> 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 ee8ecc1479..ffbf0214bb 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
+<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>.
@@ -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 <https://npmjs.com/>
+Yes, head over to <https://www.npmjs.com/>
## SEE ALSO
diff --git a/deps/npm/doc/misc/npm-scripts.md b/deps/npm/doc/misc/npm-scripts.md
index 259bf28a6b..9ceb7f2c43 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