diff options
author | isaacs <i@izs.me> | 2011-01-06 02:38:40 +0300 |
---|---|---|
committer | isaacs <i@izs.me> | 2011-01-06 02:38:40 +0300 |
commit | 1f0849ff6e852882cbd55be5fa491a043ed8c541 (patch) | |
tree | c3613870622a821e2e0ca8a27b511920a89376e1 /man1 | |
parent | 39985c8f615441bea88db878cf99819d9619a1ad (diff) |
doc the npm_dependency_* environs
Diffstat (limited to 'man1')
-rw-r--r-- | man1/scripts.1 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/man1/scripts.1 b/man1/scripts.1 index bf2dd76f6..33b12a9ab 100644 --- a/man1/scripts.1 +++ b/man1/scripts.1 @@ -95,6 +95,11 @@ variable set to "foo", and the \fBnpm_package_version\fR set to "1\.2\.5" Configuration parameters are put in the environment with the \fBnpm_config_\fR prefix\. For instance, you can view the effective \fBroot\fR config by checking the \fBnpm_config_root\fR environment variable\. . +.SS "dependency path and versions" +All of the resolved dependencies are available in the environtment as \fBnpm_dependency_<name>=<version>\fR and \fBnpm_dependency_<name>_path=<dir>\fR\|\. So, if you need to refer to files +from dependency packages, or see which version is installed, you can +refer to those environment variables\. +. .SS "Special: package\.json "config" hash" The package\.json "config" keys are overwritten in the environment if there is a config param of \fB<name>[@<version>]:<key>\fR\|\. For example, if |