summaryrefslogtreecommitdiff
path: root/deps/npm/html/doc/api/npm-link.html
diff options
context:
space:
mode:
authorisaacs <i@izs.me>2014-05-05 18:20:40 -0700
committerisaacs <i@izs.me>2014-05-05 18:20:40 -0700
commit120f7cf55fb977a145dca0ed840ea5a07730da05 (patch)
treed71ec93330b3e2514c144fa212579158bf5e3b3a /deps/npm/html/doc/api/npm-link.html
parent00890e43fb935c8bc5dc150f0f2c96bc465d8a4d (diff)
downloadnode-new-120f7cf55fb977a145dca0ed840ea5a07730da05.tar.gz
npm: upgrade to 1.4.10
* Don't set referer if already set * fetch: Send referer and npm-session headers * run-script: Support --parseable and --json * list runnable scripts (Evan Lucas) * Use marked instead of ronn for html docs
Diffstat (limited to 'deps/npm/html/doc/api/npm-link.html')
-rw-r--r--deps/npm/html/doc/api/npm-link.html24
1 files changed, 7 insertions, 17 deletions
diff --git a/deps/npm/html/doc/api/npm-link.html b/deps/npm/html/doc/api/npm-link.html
index 9be928229c..1f162e3b40 100644
--- a/deps/npm/html/doc/api/npm-link.html
+++ b/deps/npm/html/doc/api/npm-link.html
@@ -10,37 +10,27 @@
<div id="wrapper">
<h1><a href="../api/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.command.link(callback)
-npm.command.link(packages, callback)</code></pre>
-
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-
+npm.command.link(packages, callback)
+</code></pre><h2 id="description">DESCRIPTION</h2>
<p>Package linking is a two-step process.</p>
-
<p>Without parameters, link will create a globally-installed
symbolic link from <code>prefix/package-name</code> to the current folder.</p>
-
<p>With a parameters, link will create a symlink from the local <code>node_modules</code>
folder to the global symlink.</p>
-
<p>When creating tarballs for <code>npm publish</code>, the linked packages are
&quot;snapshotted&quot; 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>npm.commands.link(cb) # creates global link from the cwd
# (say redis package)
-npm.commands.link(&#39;redis&#39;, cb) # link-install the package</code></pre>
-
-<p>Now, any changes to the redis package will be reflected in
+npm.commands.link(&#39;redis&#39;, cb) # link-install the package
+</code></pre><p>Now, any changes to the redis package will be reflected in
the package in the current working directory</p>
+
</div>
<table border=0 cellspacing=0 cellpadding=0 id=npmlogo>
@@ -52,5 +42,5 @@ the package in the current working directory</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">npm-link &mdash; npm@1.4.9</p>
+<p id="footer">npm-link &mdash; npm@1.4.10</p>