aboutsummaryrefslogtreecommitdiff
path: root/deps/npm/man/man7/npm-scripts.7
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man7/npm-scripts.7')
-rw-r--r--deps/npm/man/man7/npm-scripts.76
1 files changed, 4 insertions, 2 deletions
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