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.77
1 files changed, 1 insertions, 6 deletions
diff --git a/deps/npm/man/man7/npm-scripts.7 b/deps/npm/man/man7/npm-scripts.7
index c58a1ef954..e93ad1e650 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" "June 2017" "" ""
+.TH "NPM\-SCRIPTS" "7" "July 2017" "" ""
.SH "NAME"
\fBnpm-scripts\fR \- How npm handles the "scripts" field
.SH DESCRIPTION
@@ -89,11 +89,6 @@ allow users to avoid the confusing behavior of existing npm versions and only
run on \fBnpm publish\fP (for instance, running the tests one last time to ensure
they're in good shape)\.
.P
-\fBIMPORTANT:\fR As of \fBnpm@5\fP, \fBprepublish\fP will \fIonly\fR be run for \fBnpm
-publish\fP\|\. This will make its behavior identical to \fBprepublishOnly\fP, so
-\fBnpm@6\fP or later may drop support for the use of \fBprepublishOnly\fP, and then
-maybe we can all forget this embarrassing thing ever happened\.
-.P
See https://github\.com/npm/npm/issues/10074 for a much lengthier
justification, with further reading, for this change\.
.SS USE CASES