/usr/share/doc/npm/cli/npm-dedupe.html is in npm 1.3.10~dfsg-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 | <!doctype html>
<html>
<title>npm-dedupe</title>
<meta http-equiv="content-type" value="text/html;utf-8">
<link rel="stylesheet" type="text/css" href="../../static/style.css">
<body>
<div id="wrapper">
<div class='mp'>
<h2 id="NAME">NAME</h2>
<p class="man-name">
<code>npm-dedupe</code> - <span class="man-whatis">Reduce duplication</span>
</p>
<h2 id="SYNOPSIS">SYNOPSIS</h2>
<pre><code>npm dedupe [package names...]
npm ddp [package names...]
</code></pre>
<h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>Searches the local package tree and attempts to simplify the overall
structure by moving dependencies further up the tree, where they can
be more effectively shared by multiple dependent packages.</p>
<p>For example, consider this dependency graph:</p>
<pre><code>a
+-- b <-- depends on c@1.0.x
| `-- c@1.0.3
`-- d <-- depends on c@~1.0.9
`-- c@1.0.10
</code></pre>
<p>In this case, <code><a href="../cli/npm-dedupe.html">npm-dedupe(1)</a></code> will transform the tree to:</p>
<pre><code>a
+-- b
+-- d
`-- c@1.0.10
</code></pre>
<p>Because of the hierarchical nature of node's module lookup, b and d
will both get their dependency met by the single c package at the root
level of the tree.</p>
<p>If a suitable version exists at the target location in the tree
already, then it will be left untouched, but the other duplicates will
be deleted.</p>
<p>If no suitable version can be found, then a warning is printed, and
nothing is done.</p>
<p>If any arguments are supplied, then they are filters, and only the
named packages will be touched.</p>
<p>Note that this operation transforms the dependency tree, and may
result in packages getting updated versions, perhaps from the npm
registry.</p>
<p>This feature is experimental, and may change in future versions.</p>
<h2 id="SEE-ALSO">SEE ALSO</h2>
<ul>
<li><span class="man-ref">npm-ls<span class="s">(1)</span></span></li>
<li><span class="man-ref">npm-update<span class="s">(1)</span></span></li>
<li><span class="man-ref">npm-install<span class="s">(1)</span></span></li>
</ul>
</div>
</div>
<p id="footer">npm-dedupe — npm@1.3.10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
var els = Array.prototype.slice.call(wrapper.getElementsByTagName("*"), 0)
.filter(function (el) {
return el.parentNode === wrapper
&& el.tagName.match(/H[1-6]/)
&& el.id
})
var l = 2
, toc = document.createElement("ul")
toc.innerHTML = els.map(function (el) {
var i = el.tagName.charAt(1)
, out = ""
while (i > l) {
out += "<ul>"
l ++
}
while (i < l) {
out += "</ul>"
l --
}
out += "<li><a href='#" + el.id + "'>" +
( el.innerText || el.text || el.innerHTML)
+ "</a>"
return out
}).join("\n")
toc.id = "toc"
document.body.appendChild(toc)
})()
</script>
|