aboutsummaryrefslogtreecommitdiff
path: root/deps/npm/man/man7
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man7')
-rw-r--r--deps/npm/man/man7/npm-coding-style.72
-rw-r--r--deps/npm/man/man7/npm-config.730
-rw-r--r--deps/npm/man/man7/npm-developers.72
-rw-r--r--deps/npm/man/man7/npm-disputes.76
-rw-r--r--deps/npm/man/man7/npm-index.72
-rw-r--r--deps/npm/man/man7/npm-orgs.72
-rw-r--r--deps/npm/man/man7/npm-registry.718
-rw-r--r--deps/npm/man/man7/npm-scope.72
-rw-r--r--deps/npm/man/man7/npm-scripts.76
-rw-r--r--deps/npm/man/man7/removing-npm.72
-rw-r--r--deps/npm/man/man7/semver.72
11 files changed, 53 insertions, 21 deletions
diff --git a/deps/npm/man/man7/npm-coding-style.7 b/deps/npm/man/man7/npm-coding-style.7
index d1fcce79df..455c30d9d2 100644
--- a/deps/npm/man/man7/npm-coding-style.7
+++ b/deps/npm/man/man7/npm-coding-style.7
@@ -1,4 +1,4 @@
-.TH "NPM\-CODING\-STYLE" "7" "July 2018" "" ""
+.TH "NPM\-CODING\-STYLE" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-coding-style\fR \- npm's "funny" coding style
.SH DESCRIPTION
diff --git a/deps/npm/man/man7/npm-config.7 b/deps/npm/man/man7/npm-config.7
index f664d4d268..22847a0443 100644
--- a/deps/npm/man/man7/npm-config.7
+++ b/deps/npm/man/man7/npm-config.7
@@ -1,4 +1,4 @@
-.TH "NPM\-CONFIG" "7" "July 2018" "" ""
+.TH "NPM\-CONFIG" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-config\fR \- More than you probably want to know about npm configuration
.SH DESCRIPTION
@@ -223,6 +223,17 @@ Type: Boolean
When "true" submit audit reports alongside \fBnpm install\fP runs to the default
registry and all registries configured for scopes\. See the documentation
for npm help audit for details on what is submitted\.
+.SS audit\-level
+.RS 0
+.IP \(bu 2
+Default: \fB"low"\fP
+.IP \(bu 2
+Type: \fB\|'low'\fP, \fB\|'moderate'\fP, \fB\|'high'\fP, \fB\|'critical'\fP
+
+.RE
+.P
+The minimum level of vulnerability for \fBnpm audit\fP to exit with
+a non\-zero exit code\.
.SS auth\-type
.RS 0
.IP \(bu 2
@@ -457,8 +468,8 @@ Type: Boolean
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, \fBinstall\fP, \fBupdate\fP,
-\fBdedupe\fP, \fBuninstall\fP\|\. This is NOT currently honored by network related
-commands, eg \fBdist\-tags\fP, \fBowner\fP, \fBpublish\fP, etc\.
+\fBdedupe\fP, \fBuninstall\fP\|\. This is NOT currently honored by some network related
+commands, eg \fBdist\-tags\fP, \fBowner\fP, etc\.
.SS editor
.RS 0
.IP \(bu 2
@@ -946,7 +957,7 @@ Type: semver or false
.RE
.P
The node version to use when checking a package's \fBengines\fP map\.
-.SS no\-proxy
+.SS noproxy
.RS 0
.IP \(bu 2
Default: null
@@ -1096,6 +1107,17 @@ Type: path
.P
The location to install global items\. If set on the command line, then
it forces non\-global commands to run in the specified folder\.
+.SS preid
+.RS 0
+.IP \(bu 2
+Default: ""
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The "prerelease identifier" to use as a prefix for the "prerelease" part of a
+semver\. Like the \fBrc\fP in \fB1\.2\.0\-rc\.8\fP\|\.
.SS production
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man7/npm-developers.7 b/deps/npm/man/man7/npm-developers.7
index 144a9e387d..22ccbd70d2 100644
--- a/deps/npm/man/man7/npm-developers.7
+++ b/deps/npm/man/man7/npm-developers.7
@@ -1,4 +1,4 @@
-.TH "NPM\-DEVELOPERS" "7" "July 2018" "" ""
+.TH "NPM\-DEVELOPERS" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-developers\fR \- Developer Guide
.SH DESCRIPTION
diff --git a/deps/npm/man/man7/npm-disputes.7 b/deps/npm/man/man7/npm-disputes.7
index ed3350767a..23cd81e0b5 100644
--- a/deps/npm/man/man7/npm-disputes.7
+++ b/deps/npm/man/man7/npm-disputes.7
@@ -1,4 +1,4 @@
-.TH "NPM\-DISPUTES" "7" "July 2018" "" ""
+.TH "NPM\-DISPUTES" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-disputes\fR \- Handling Module Name Disputes
.P
@@ -120,8 +120,8 @@ here to help\.\fR
.P
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:// \fIhttps://npmjs\.com\fR\|\. Attach a
-copy of your trademark registration certificate\.
+the package or user account on https:// \fIhttps://www\.npmjs\.com/\fR\|\.
+Attach a copy of your trademark registration certificate\.
.P
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/man/man7/npm-index.7 b/deps/npm/man/man7/npm-index.7
index 94b3815015..209d6ae409 100644
--- a/deps/npm/man/man7/npm-index.7
+++ b/deps/npm/man/man7/npm-index.7
@@ -1,4 +1,4 @@
-.TH "NPM\-INDEX" "7" "July 2018" "" ""
+.TH "NPM\-INDEX" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-index\fR \- Index of all npm documentation
.SS npm help README
diff --git a/deps/npm/man/man7/npm-orgs.7 b/deps/npm/man/man7/npm-orgs.7
index c904887e6d..db86589161 100644
--- a/deps/npm/man/man7/npm-orgs.7
+++ b/deps/npm/man/man7/npm-orgs.7
@@ -1,4 +1,4 @@
-.TH "NPM\-ORGS" "7" "July 2018" "" ""
+.TH "NPM\-ORGS" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-orgs\fR \- Working with Teams & Orgs
.SH DESCRIPTION
diff --git a/deps/npm/man/man7/npm-registry.7 b/deps/npm/man/man7/npm-registry.7
index 8ed316303b..e2ca184223 100644
--- a/deps/npm/man/man7/npm-registry.7
+++ b/deps/npm/man/man7/npm-registry.7
@@ -1,4 +1,4 @@
-.TH "NPM\-REGISTRY" "7" "July 2018" "" ""
+.TH "NPM\-REGISTRY" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-registry\fR \- The JavaScript Package Registry
.SH DESCRIPTION
@@ -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\.
.P
-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\|\.
+.P
+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\.
+.P
+npm's package registry implementation supports several
write APIs as well, to allow for publishing packages and managing user
account information\.
.P
-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\|\.
.P
@@ -79,7 +87,7 @@ No, but it's way easier\. Basically, yes, you do, or you have to
effectively implement the entire CouchDB API anyway\.
.SH Is there a website or something to see package docs and such?
.P
-Yes, head over to https://npmjs\.com/
+Yes, head over to https://www\.npmjs\.com/
.SH SEE ALSO
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man7/npm-scope.7 b/deps/npm/man/man7/npm-scope.7
index 4e96ef9e0b..1a54139844 100644
--- a/deps/npm/man/man7/npm-scope.7
+++ b/deps/npm/man/man7/npm-scope.7
@@ -1,4 +1,4 @@
-.TH "NPM\-SCOPE" "7" "July 2018" "" ""
+.TH "NPM\-SCOPE" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-scope\fR \- Scoped packages
.SH DESCRIPTION
diff --git a/deps/npm/man/man7/npm-scripts.7 b/deps/npm/man/man7/npm-scripts.7
index f037b8dbad..3a7e80870a 100644
--- a/deps/npm/man/man7/npm-scripts.7
+++ b/deps/npm/man/man7/npm-scripts.7
@@ -1,4 +1,4 @@
-.TH "NPM\-SCRIPTS" "7" "July 2018" "" ""
+.TH "NPM\-SCRIPTS" "7" "August 2018" "" ""
.SH "NAME"
\fBnpm-scripts\fR \- How npm handles the "scripts" field
.SH DESCRIPTION
@@ -170,7 +170,9 @@ The package\.json fields are tacked onto the \fBnpm_package_\fP prefix\. So,
for instance, if you had \fB{"name":"foo", "version":"1\.2\.5"}\fP in your
package\.json file, then your package scripts would have the
\fBnpm_package_name\fP environment variable set to "foo", and the
-\fBnpm_package_version\fP set to "1\.2\.5"
+\fBnpm_package_version\fP set to "1\.2\.5"\. You can access these variables
+in your code with \fBprocess\.env\.npm_package_name\fP and
+\fBprocess\.env\.npm_package_version\fP, and so on for other fields\.
.SS configuration
.P
Configuration parameters are put in the environment with the
diff --git a/deps/npm/man/man7/removing-npm.7 b/deps/npm/man/man7/removing-npm.7
index 0500ae926f..99fa7b7998 100644
--- a/deps/npm/man/man7/removing-npm.7
+++ b/deps/npm/man/man7/removing-npm.7
@@ -1,4 +1,4 @@
-.TH "NPM\-REMOVAL" "1" "July 2018" "" ""
+.TH "NPM\-REMOVAL" "1" "August 2018" "" ""
.SH "NAME"
\fBnpm-removal\fR \- Cleaning the Slate
.SH SYNOPSIS
diff --git a/deps/npm/man/man7/semver.7 b/deps/npm/man/man7/semver.7
index 3451156073..abc92686aa 100644
--- a/deps/npm/man/man7/semver.7
+++ b/deps/npm/man/man7/semver.7
@@ -1,4 +1,4 @@
-.TH "SEMVER" "7" "July 2018" "" ""
+.TH "SEMVER" "7" "August 2018" "" ""
.SH "NAME"
\fBsemver\fR \- The semantic versioner for npm
.SH Install
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-14 09:38:32 +0000