summaryrefslogtreecommitdiff
path: root/deps/npm/doc/cli/npm-shrinkwrap.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/doc/cli/npm-shrinkwrap.md')
-rw-r--r--deps/npm/doc/cli/npm-shrinkwrap.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/deps/npm/doc/cli/npm-shrinkwrap.md b/deps/npm/doc/cli/npm-shrinkwrap.md
index c79418a248..6fc7d96f7c 100644
--- a/deps/npm/doc/cli/npm-shrinkwrap.md
+++ b/deps/npm/doc/cli/npm-shrinkwrap.md
@@ -109,6 +109,14 @@ resolution using "version" if one isn't.
2. The tree is walked and any missing dependencies are installed in the usual fashion.
+If `preshrinkwrap`, `shrinkwrap` or `postshrinkwrap` are in the `scripts` property of the
+`package.json`, they will be executed by running `npm shrinkwrap`.
+`preshrinkwrap` and `shrinkwrap` are executed before the shrinkwrap, `postshrinkwrap` is
+executed afterwards. For example to run some postprocessing on the generated file:
+
+ "scripts": { "postshrinkwrap": "node fix-shrinkwrap.js" }
+
+
### Using shrinkwrapped packages
Using a shrinkwrapped package is no different than using any other
@@ -174,5 +182,7 @@ contents rather than versions.
## SEE ALSO
* npm-install(1)
+* npm-run-script(1)
+* npm-scripts(7)
* package.json(5)
* npm-ls(1)