summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-link.1
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man1/npm-link.1')
-rw-r--r--deps/npm/man/man1/npm-link.113
1 files changed, 7 insertions, 6 deletions
diff --git a/deps/npm/man/man1/npm-link.1 b/deps/npm/man/man1/npm-link.1
index 921b79e498..db43123a68 100644
--- a/deps/npm/man/man1/npm-link.1
+++ b/deps/npm/man/man1/npm-link.1
@@ -1,4 +1,4 @@
-.TH "NPM\-LINK" "1" "February 2016" "" ""
+.TH "NPM\-LINK" "1" "March 2016" "" ""
.SH "NAME"
\fBnpm-link\fR \- Symlink a package folder
.SH SYNOPSIS
@@ -15,12 +15,13 @@ alias: npm ln
.P
Package linking is a two\-step process\.
.P
-First, \fBnpm link\fP in a package folder will create a globally\-installed
-symbolic link from \fBprefix/package\-name\fP to the current folder (see
-npm help 7 \fBnpm\-config\fP for the value of \fBprefix\fP)\.
+First, \fBnpm link\fP in a package folder will create a symlink in the global folder
+\fB{prefix}/lib/node_modules/<package>\fP that links to the package where the \fBnpm
+link\fP command was executed\. (see npm help 7 \fBnpm\-config\fP for the value of \fBprefix\fP)\.
.P
Next, in some other location, \fBnpm link package\-name\fP will create a
-symlink from the local \fBnode_modules\fP folder to the global symlink\.
+symbolic link from globally\-installed \fBpackage\-name\fP to \fBnode_modules/\fP
+of the current folder\.
.P
Note that \fBpackage\-name\fP is taken from \fBpackage\.json\fP,
not from directory name\.
@@ -47,7 +48,7 @@ npm link redis # link\-install the package
.P
Now, any changes to ~/projects/node\-redis will be reflected in
~/projects/node\-bloggy/node_modules/node\-redis/\. Note that the link should
-be to the package name, not the directory name for that package\.
+be to the package name, not the directory name for that package\.
.P
You may also shortcut the two steps in one\. For example, to do the
above use\-case in a shorter way: