@@ -60,18 +60,18 @@ on Unix-like systems it is the `/bin/sh` command, on Windows it is the `cmd.exe`
6060The actual shell referred to by ` /bin/sh ` also depends on the system.
6161You can customize the shell with the ` script-shell ` configuration.
6262
63- Scripts are run from the root of the module , regardless of what the current
64- working directory is when ` npm run ` is called. If you want your script to
65- use different behavior based on what subdirectory you're in, you can use the
66- ` INIT_CWD ` environment variable, which holds the full path you were in when
67- you ran ` npm run ` .
68-
69- ` npm run ` sets the ` NODE ` environment variable to the ` node ` executable with
70- which ` npm ` is executed. Also, if the ` --scripts-prepend-node-path ` is passed,
71- the directory within which ` node ` resides is added to the
72- ` PATH ` . If ` --scripts-prepend-node-path=auto ` is passed (which has been the
73- default in ` npm ` v3), this is only performed when that ` node ` executable is
74- not found in the ` PATH ` .
63+ Scripts are run from the root of the package folder , regardless of what the
64+ current working directory is when ` npm run ` is called. If you want your
65+ script to use different behavior based on what subdirectory you're in, you
66+ can use the ` INIT_CWD ` environment variable, which holds the full path you
67+ were in when you ran ` npm run ` .
68+
69+ ` npm run ` sets the ` NODE ` environment variable to the ` node ` executable
70+ with which ` npm ` is executed. Also, if the ` --scripts-prepend-node-path ` is
71+ passed, the directory within which ` node ` resides is added to the ` PATH ` .
72+ If ` --scripts-prepend-node-path=auto ` is passed (which has been the default
73+ in ` npm ` v3), this is only performed when that ` node ` executable is not
74+ found in the ` PATH ` .
7575
7676If you try to run a script without having a ` node_modules ` directory and it fails,
7777you will be given a warning to run ` npm install ` , just in case you've forgotten.
0 commit comments