summaryrefslogtreecommitdiff
path: root/deps/npm/html/doc/cli/npm-install.html
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/html/doc/cli/npm-install.html')
-rw-r--r--deps/npm/html/doc/cli/npm-install.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html
index 979e317612..06f4744283 100644
--- a/deps/npm/html/doc/cli/npm-install.html
+++ b/deps/npm/html/doc/cli/npm-install.html
@@ -163,7 +163,7 @@ fetch the package by name if it is not valid.</code></pre><ul>
be any valid semver range or exact version, and npm will look for any tags
or refs matching that range in the remote repository, much as it would for a
registry dependency. If neither <code>#&lt;commit-ish&gt;</code> or <code>#semver:&lt;semver&gt;</code> is
- specified, then <code>master</code> is used.</p>
+ specified, then the default branch of the repository is used.</p>
<p> If the repository makes use of submodules, those submodules will be cloned
as well.</p>
<p> If the package being installed contains a <code>prepare</code> script, its
@@ -370,5 +370,5 @@ affects a real use-case, it will be investigated.</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-install &mdash; npm@6.4.1</p>
+<p id="footer">npm-install &mdash; npm@6.5.0-next.0</p>