summaryrefslogtreecommitdiff
path: root/deps/npm/docs/output/using-npm/scripts.html
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/docs/output/using-npm/scripts.html')
-rw-r--r--deps/npm/docs/output/using-npm/scripts.html5
1 files changed, 5 insertions, 0 deletions
diff --git a/deps/npm/docs/output/using-npm/scripts.html b/deps/npm/docs/output/using-npm/scripts.html
index 19082719ef..a1b691f376 100644
--- a/deps/npm/docs/output/using-npm/scripts.html
+++ b/deps/npm/docs/output/using-npm/scripts.html
@@ -447,6 +447,11 @@ for anything else. You should almost never have to explicitly set a
preinstall or install script. If you are doing this, please consider if
there is another option. The only valid use of <code>install</code> or <code>preinstall</code>
scripts is for compilation which must be done on the target architecture.</li>
+<li>Scripts are run from the root of the package folder, regardless of what the
+current working directory is when <code>npm</code> is invoked. If you want your
+script to use different behavior based on what subdirectory you're in, you
+can use the <code>INIT_CWD</code> environment variable, which holds the full path you
+were in when you ran <code>npm run</code>.</li>
</ul>
<h3 id="see-also">See Also</h3>
<ul>