diff options
Diffstat (limited to 'deps/npm/html/partial/doc/cli/npm-link.html')
| -rw-r--r-- | deps/npm/html/partial/doc/cli/npm-link.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/deps/npm/html/partial/doc/cli/npm-link.html b/deps/npm/html/partial/doc/cli/npm-link.html index c4b01c2a65..1a33cf2c3e 100644 --- a/deps/npm/html/partial/doc/cli/npm-link.html +++ b/deps/npm/html/partial/doc/cli/npm-link.html @@ -24,14 +24,14 @@ npm link # creates global link cd ~/projects/node-bloggy # go into some other package directory. npm link redis # link-install the package </code></pre><p>Now, any changes to ~/projects/node-redis will be reflected in -~/projects/node-bloggy/node_modules/redis/</p> +~/projects/node-bloggy/node_modules/node-redis/</p> <p>You may also shortcut the two steps in one. For example, to do the above use-case in a shorter way:</p> <pre><code>cd ~/projects/node-bloggy # go into the dir of your main project npm link ../node-redis # link the dir of your dependency </code></pre><p>The second line is the equivalent of doing:</p> <pre><code>(cd ../node-redis; npm link) -npm link redis +npm link node-redis </code></pre><p>That is, it first creates a global link, and then links the global installation target into your project's <code>node_modules</code> folder.</p> <p>If your linked package is scoped (see <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>) your link command must |