summaryrefslogtreecommitdiff
path: root/deps/npm/doc/cli/npm-run-script.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/doc/cli/npm-run-script.md')
-rw-r--r--deps/npm/doc/cli/npm-run-script.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/deps/npm/doc/cli/npm-run-script.md b/deps/npm/doc/cli/npm-run-script.md
index c1ce342953..ee907d8c73 100644
--- a/deps/npm/doc/cli/npm-run-script.md
+++ b/deps/npm/doc/cli/npm-run-script.md
@@ -44,6 +44,12 @@ instead of
to run your tests.
+The actual shell your script is run within is platform dependent. By default,
+on Unix-like systems it is the `/bin/sh` command, on Windows it is the `cmd.exe`.
+The actual shell referred to by `/bin/sh` also depends on the system.
+As of [`npm@5.1.0`](https://github.com/npm/npm/releases/tag/v5.1.0) you can
+customize the shell with the `script-shell` configuration.
+
Scripts are run from the root of the module, regardless of what your current
working directory is when you call `npm run`. If you want your script to
use different behavior based on what subdirectory you're in, you can use the
@@ -69,3 +75,4 @@ You can use the `--silent` flag to prevent showing `npm ERR!` output on error.
* npm-start(1)
* npm-restart(1)
* npm-stop(1)
+* npm-config(7)