diff options
Diffstat (limited to 'deps/npm/html/doc/cli/npm-link.html')
| -rw-r--r-- | deps/npm/html/doc/cli/npm-link.html | 51 |
1 files changed, 21 insertions, 30 deletions
diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html index d47465a51c..ab9d36e59e 100644 --- a/deps/npm/html/doc/cli/npm-link.html +++ b/deps/npm/html/doc/cli/npm-link.html @@ -10,60 +10,51 @@ <div id="wrapper"> <h1><a href="../cli/npm-link.html">npm-link</a></h1> <p>Symlink a package folder</p> - -<h2 id="SYNOPSIS">SYNOPSIS</h2> - +<h2 id="synopsis">SYNOPSIS</h2> <pre><code>npm link (in package folder) npm link <pkgname> -npm ln (with any of the previous argument usage)</code></pre> - -<h2 id="DESCRIPTION">DESCRIPTION</h2> - +npm ln (with any of the previous argument usage) +</code></pre><h2 id="description">DESCRIPTION</h2> <p>Package linking is a two-step process.</p> - <p>First, <code>npm link</code> in a package folder will create a globally-installed symbolic link from <code>prefix/package-name</code> to the current folder.</p> - <p>Next, in some other location, <code>npm link package-name</code> will create a symlink from the local <code>node_modules</code> folder to the global symlink.</p> - <p>Note that <code>package-name</code> is taken from <code>package.json</code>, not from directory name.</p> - <p>When creating tarballs for <code>npm publish</code>, the linked packages are "snapshotted" to their current state by resolving the symbolic links.</p> - <p>This is handy for installing your own stuff, so that you can work on it and test it iteratively without having to continually rebuild.</p> - <p>For example:</p> - <pre><code>cd ~/projects/node-redis # go into the package directory 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 +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> - <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> - +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</code></pre> - -<p>That is, it first creates a global link, and then links the global +npm link 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> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="../misc/npm-developers.html">npm-developers(7)</a></li> +<li><a href="../misc/npm-faq.html">npm-faq(7)</a></li> +<li><a href="../files/package.json.html">package.json(5)</a></li> +<li><a href="../cli/npm-install.html">npm-install(1)</a></li> +<li><a href="../files/npm-folders.html">npm-folders(5)</a></li> +<li><a href="../cli/npm-config.html">npm-config(1)</a></li> +<li><a href="../misc/npm-config.html">npm-config(7)</a></li> +<li><a href="../files/npmrc.html">npmrc(5)</a></li> +</ul> -<h2 id="SEE-ALSO">SEE ALSO</h2> - -<ul><li><a href="../misc/npm-developers.html">npm-developers(7)</a></li><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li></ul> </div> <table border=0 cellspacing=0 cellpadding=0 id=npmlogo> @@ -75,5 +66,5 @@ installation target into your project's <code>node_modules</code> folder.</p <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-link — npm@1.4.9</p> +<p id="footer">npm-link — npm@1.4.10</p> |