Skip to content

Commit

Permalink
deps: upgrade npm to 7.0.15
Browse files Browse the repository at this point in the history
PR-URL: #36293
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
  • Loading branch information
ruyadorno authored and danielleadams committed Dec 7, 2020
1 parent 58abdca commit 278862a
Show file tree
Hide file tree
Showing 35 changed files with 841 additions and 61 deletions.
3 changes: 3 additions & 0 deletions deps/npm/AUTHORS
Original file line number Diff line number Diff line change
Expand Up @@ -735,3 +735,6 @@ Vlad GURDIGA <gurdiga@gmail.com>
Sébastien Puech <s.puech@tricentis.com>
Jannis Hell <Primajin@users.noreply.github.com>
Hollow Man <hollowman@hollowman.ml>
kai zhu <kaizhu256@gmail.com>
Alex Woollam <alexjhwoollam@gmail.com>
Daniel Fischer <daniel@d-fischer.dev>
35 changes: 35 additions & 0 deletions deps/npm/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,38 @@
## 7.0.15 (2020-11-27)

### DEPENDENCIES

* [`00e6028ef`](https://github.com/npm/cli/commit/00e6028ef83bf76eaae10241fd7ba59e39768603)
`@npmcli/arborist@1.0.13`
* do not override user-defined shorthand values when saving `package.json`

### BUG FIXES

* [`9c3413fbc`](https://github.com/npm/cli/commit/9c3413fbcb37e79fc0b3d980e0b5810d7961277c)
[#2034](https://github.com/npm/cli/issues/2034)
[#2245](https://github.com/npm/cli/issues/2245)
`npm link <pkg>` should not save `package.json`
([@ruyadorno](https://github.com/ruyadorno))

### DOCUMENTATION

* [`1875347f9`](https://github.com/npm/cli/commit/1875347f9f4f2b50c28fe8857c5533eeebf42da2)
[#2196](https://github.com/npm/cli/issues/2196)
remove doc on obsolete `unsafe-perm` flag
([@kaizhu256](https://github.com/kaizhu256))
* [`f51e50603`](https://github.com/npm/cli/commit/f51e5060340c783a8a00dadd98e5786960caf43f)
[#2200](https://github.com/npm/cli/issues/2200)
`config.md` cleanup
([@alexwoollam](https://github.com/alexwoollam))
* [`997cbdb40`](https://github.com/npm/cli/commit/997cbdb400bcd22e457e8a06b69a7be697cfd66d)
[#2238](https://github.com/npm/cli/issues/2238)
Fix broken link to `package.json` documentation
([@d-fischer](https://github.com/d-fischer))
* [`9da972dc4`](https://github.com/npm/cli/commit/9da972dc44c21cf0e337f1c3fca44eb9df3e40d5)
[#2241](https://github.com/npm/cli/issues/2241)
`npm star` docs cleanup
([@ruyadorno](https://github.com/ruyadorno))

## 7.0.14 (2020-11-23)

### DEPENDENCIES
Expand Down
17 changes: 15 additions & 2 deletions deps/npm/docs/content/commands/npm-star.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,20 +8,33 @@ description: Mark your favorite packages

```bash
npm star [<pkg>...]
npm unstar [<pkg>...]
```

### Description

"Starring" a package means that you have some interest in it. It's
a vaguely positive way to show that you care.

It's a boolean thing. Starring repeatedly has no additional effect.

### More

There's also these extra commands to help you manage your favorite packages:

#### Unstar

You can also "unstar" a package using [`npm unstar`](/commands/npm-unstar)

"Unstarring" is the same thing, but in reverse.

It's a boolean thing. Starring repeatedly has no additional effect.
#### Listing stars

You can see all your starred packages using [`npm stars`](/commands/npm-stars)

### See Also

* [npm unstar](/commands/npm-unstar)
* [npm stars](/commands/npm-stars)
* [npm view](/commands/npm-view)
* [npm whoami](/commands/npm-whoami)
* [npm adduser](/commands/npm-adduser)
1 change: 1 addition & 0 deletions deps/npm/docs/content/commands/npm-stars.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ you will most certainly enjoy this command.
### See Also

* [npm star](/commands/npm-star)
* [npm unstar](/commands/npm-unstar)
* [npm view](/commands/npm-view)
* [npm whoami](/commands/npm-whoami)
* [npm adduser](/commands/npm-adduser)
36 changes: 36 additions & 0 deletions deps/npm/docs/content/commands/npm-unstar.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
title: npm-unstar
section: 1
description: Remove an item from your favorite packages
---

### Synopsis

```bash
npm unstar [<pkg>...]
```

### Description

"Unstarring" a package is the opposite of [`npm star`](/commands/npm-star),
it removes an item from your list of favorite packages.

### More

There's also these extra commands to help you manage your favorite packages:

#### Star

You can "star" a package using [`npm star`](/commands/npm-star)

#### Listing stars

You can see all your starred packages using [`npm stars`](/commands/npm-stars)

### See Also

* [npm star](/commands/npm-star)
* [npm stars](/commands/npm-stars)
* [npm view](/commands/npm-view)
* [npm whoami](/commands/npm-whoami)
* [npm adduser](/commands/npm-adduser)
4 changes: 2 additions & 2 deletions deps/npm/docs/content/using-npm/config.md
Original file line number Diff line number Diff line change
Expand Up @@ -432,7 +432,7 @@ Format `package-lock.json` or `npm-shrinkwrap.json` as a human readable file.
* Type: Boolean

When "true" displays the message at the end of each `npm install`
aknowledging the number of dependencies looking for funding.
acknowledging the number of dependencies looking for funding.
See [`npm fund`](/commands/npm-fund) for details.

#### fetch-retries
Expand Down Expand Up @@ -1096,7 +1096,7 @@ using legacy search endpoint.

If true, success/failure metrics will be reported to the registry stored in
`metrics-registry`. These requests contain the number of successful and
failing runs of the npm CLI and the time period overwhich those counts were
failing runs of the npm CLI and the time period over which those counts were
gathered. No identifying information is included in these requests.

#### shell
Expand Down
6 changes: 2 additions & 4 deletions deps/npm/docs/content/using-npm/scripts.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,10 +122,8 @@ npm will default some script values based on package contents.

### User

If npm was invoked with root privileges, then it will change the uid
to the user account or uid specified by the `user` config, which
defaults to `nobody`. Set the `unsafe-perm` flag to run scripts with
root privileges.
When npm is run as root, scripts are always run with the effective uid
and gid of the working directory owner.

### Environment

Expand Down
4 changes: 2 additions & 2 deletions deps/npm/docs/content/using-npm/workspaces.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,13 @@ order to add references to packages that should be symlinked into the current

We also refer to these packages being auto-symlinked during `npm install` as a
single **workspace**, meaning it's a nested package within the current local
file system that is explicitly defined in the [`package.json`](/using-npm/package-json)
file system that is explicitly defined in the [`package.json`](/configuring-npm/package-json#workspaces)
`workspaces` configuration.

### Installing workspaces

Workspaces are usually defined via the `workspaces` property of the
[`package.json`](/using-npm/package-json) file, e.g:
[`package.json`](/configuring-npm/package-json#workspaces) file, e.g:

```json
{
Expand Down
2 changes: 1 addition & 1 deletion deps/npm/docs/output/commands/npm-ls.html
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,7 @@ <h3 id="description">Description</h3>
limit the results to only the paths to the packages named. Note that
nested packages will <em>also</em> show the paths to the specified packages.
For example, running <code>npm ls promzard</code> in npm’s source tree will show:</p>
<pre lang="bash"><code> npm@7.0.14 /path/to/npm
<pre lang="bash"><code> npm@7.0.15 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
</code></pre>
Expand Down
13 changes: 10 additions & 3 deletions deps/npm/docs/output/commands/npm-star.html
Original file line number Diff line number Diff line change
Expand Up @@ -141,20 +141,27 @@ <h1 id="npm-star">npm-star</h1>

<section id="table_of_contents">
<h2 id="table-of-contents">Table of contents</h2>
<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#see-also">See Also</a></li></ul></div>
<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#more">More</a></li><ul><li><a href="#unstar">Unstar</a></li><li><a href="#listing-stars">Listing stars</a></li></ul><li><a href="#see-also">See Also</a></li></ul></div>
</section>

<div id="_content"><h3 id="synopsis">Synopsis</h3>
<pre lang="bash"><code>npm star [&lt;pkg&gt;...]
npm unstar [&lt;pkg&gt;...]
</code></pre>
<h3 id="description">Description</h3>
<p>“Starring” a package means that you have some interest in it. It’s
a vaguely positive way to show that you care.</p>
<p>It’s a boolean thing. Starring repeatedly has no additional effect.</p>
<h3 id="more">More</h3>
<p>There’s also these extra commands to help you manage your favorite packages:</p>
<h4 id="unstar">Unstar</h4>
<p>You can also “unstar” a package using <a href="../commands/npm-unstar.html"><code>npm unstar</code></a></p>
<p>“Unstarring” is the same thing, but in reverse.</p>
<p>It’s a boolean thing. Starring repeatedly has no additional effect.</p>
<h4 id="listing-stars">Listing stars</h4>
<p>You can see all your starred packages using <a href="../commands/npm-stars.html"><code>npm stars</code></a></p>
<h3 id="see-also">See Also</h3>
<ul>
<li><a href="../commands/npm-unstar.html">npm unstar</a></li>
<li><a href="../commands/npm-stars.html">npm stars</a></li>
<li><a href="../commands/npm-view.html">npm view</a></li>
<li><a href="../commands/npm-whoami.html">npm whoami</a></li>
<li><a href="../commands/npm-adduser.html">npm adduser</a></li>
Expand Down
1 change: 1 addition & 0 deletions deps/npm/docs/output/commands/npm-stars.html
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,7 @@ <h3 id="description">Description</h3>
<h3 id="see-also">See Also</h3>
<ul>
<li><a href="../commands/npm-star.html">npm star</a></li>
<li><a href="../commands/npm-unstar.html">npm unstar</a></li>
<li><a href="../commands/npm-view.html">npm view</a></li>
<li><a href="../commands/npm-whoami.html">npm whoami</a></li>
<li><a href="../commands/npm-adduser.html">npm adduser</a></li>
Expand Down
Loading

0 comments on commit 278862a

Please sign in to comment.