deps: upgrade npm to 8.0.0

PR-URL: https://github.com/nodejs/node/pull/40369
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Danielle Adams <adamzdanielle@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
This commit is contained in:
npm team 2021-10-07 20:21:11 +00:00 committed by Myles Borins
parent 58739edf99
commit dbc91de011
No known key found for this signature in database
GPG Key ID: 933B01F40B5CA946
748 changed files with 4600 additions and 97651 deletions

View File

@ -138,7 +138,8 @@ Package descriptors have the following fields:
the case of packages fetched from the registry, this will be a url to a
tarball. In the case of git dependencies, this will be the full git url
with commit sha. In the case of link dependencies, this will be the
location of the link target.
location of the link target. `registry.npmjs.org` is a magic value meaning
"the currently configured registry".
* integrity: A `sha512` or `sha1` [Standard Subresource
Integrity](https://w3c.github.io/webappsec/specs/subresourceintegrity/)
@ -201,7 +202,8 @@ Dependency objects have the following fields:
* resolved: For registry sources this is path of the tarball relative to
the registry URL. If the tarball URL isn't on the same server as the
registry URL then this is a complete URL.
registry URL then this is a complete URL. `registry.npmjs.org` is a magic
value meaning "the currently configured registry".
* bundled: If true, this is the bundled dependency and will be installed
by the parent module. When installing, this module will be extracted

View File

@ -30,6 +30,13 @@ The registry URL used is determined by the scope of the package (see
supplied by the `registry` config parameter. See [`npm config`](/commands/npm-config),
[`npmrc`](/configuring-npm/npmrc), and [`config`](/using-npm/config) for more on managing npm's configuration.
When the default registry is used in a package-lock or shrinkwrap is has the
special meaning of "the currently configured registry". If you create a lock
file while using the default registry you can switch to another registry and
npm will install packages from the new registry, but if you create a lock
file while using a custom registry packages will be installed from that
registry even after you change to another registry.
### Does npm send any information about me back to the registry?
Yes.

View File

@ -98,7 +98,8 @@ desired, with `npm access` or on the npmjs.com website.
Scopes can be associated with a separate registry. This allows you to
seamlessly use a mix of packages from the primary npm registry and one or more
private registries, such as npm Enterprise.
private registries, such as [GitHub Packages](https://github.com/features/packages) or the open source [Verdaccio](https://verdaccio.org)
project.
You can associate a scope with a registry at login, e.g.

View File

@ -176,6 +176,22 @@ npm run test --workspaces
Will run the `test` script in both `./packages/a` and `./packages/b`.
Commands will be run in each workspace in the order they appear in your `package.json`
```
{
"workspaces": [ "packages/a", "packages/b" ]
}
```
Order of run is different with:
```
{
"workspaces": [ "packages/b", "packages/a" ]
}
```
### Ignoring missing scripts
It is not required for all of the workspaces to implement scripts run with the `npm run` command.

View File

@ -159,7 +159,7 @@ tree at all, use <a href="../commands/npm-explain.html"><code>npm explain</code>
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 npms source tree will show:</p>
<pre lang="bash"><code>npm@7.24.0 /path/to/npm
<pre lang="bash"><code>npm@8.0.0 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
</code></pre>

View File

@ -148,7 +148,7 @@ npm command-line interface
<pre lang="bash"><code>npm &lt;command&gt; [args]
</code></pre>
<h3 id="version">Version</h3>
<p>7.24.0</p>
<p>8.0.0</p>
<h3 id="description">Description</h3>
<p>npm is the package manager for the Node JavaScript platform. It puts
modules in place so that node can find them, and manages dependency

View File

@ -262,7 +262,8 @@ packages are listed with their relative paths from the root project folder.</p>
the case of packages fetched from the registry, this will be a url to a
tarball. In the case of git dependencies, this will be the full git url
with commit sha. In the case of link dependencies, this will be the
location of the link target.</p>
location of the link target. <code>registry.npmjs.org</code> is a magic value meaning
“the currently configured registry”.</p>
</li>
<li>
<p>integrity: A <code>sha512</code> or <code>sha1</code> <a href="https://w3c.github.io/webappsec/specs/subresourceintegrity/">Standard Subresource
@ -334,7 +335,8 @@ dependencies, this is the commit sha.</p>
<li>
<p>resolved: For registry sources this is path of the tarball relative to
the registry URL. If the tarball URL isnt on the same server as the
registry URL then this is a complete URL.</p>
registry URL then this is a complete URL. <code>registry.npmjs.org</code> is a magic
value meaning “the currently configured registry”.</p>
</li>
<li>
<p>bundled: If true, this is the bundled dependency and will be installed

View File

@ -163,6 +163,12 @@ of which there is a public mirror at <a href="https://skimdb.npmjs.com/registry"
<a href="../using-npm/scope.html"><code>scope</code></a>. If no scope is specified, the default registry is used, which is
supplied by the <code>registry</code> config parameter. See <a href="../commands/npm-config.html"><code>npm config</code></a>,
<a href="../configuring-npm/npmrc.html"><code>npmrc</code></a>, and <a href="../using-npm/config.html"><code>config</code></a> for more on managing npms configuration.</p>
<p>When the default registry is used in a package-lock or shrinkwrap is has the
special meaning of “the currently configured registry”. If you create a lock
file while using the default registry you can switch to another registry and
npm will install packages from the new registry, but if you create a lock
file while using a custom registry packages will be installed from that
registry even after you change to another registry.</p>
<h3 id="does-npm-send-any-information-about-me-back-to-the-registry">Does npm send any information about me back to the registry?</h3>
<p>Yes.</p>
<p>When making requests of the registry npm adds two headers with information

View File

@ -206,7 +206,8 @@ desired, with <code>npm access</code> or on the npmjs.com website.</p>
<h3 id="associating-a-scope-with-a-registry">Associating a scope with a registry</h3>
<p>Scopes can be associated with a separate registry. This allows you to
seamlessly use a mix of packages from the primary npm registry and one or more
private registries, such as npm Enterprise.</p>
private registries, such as <a href="https://github.com/features/packages">GitHub Packages</a> or the open source <a href="https://verdaccio.org">Verdaccio</a>
project.</p>
<p>You can associate a scope with a registry at login, e.g.</p>
<pre lang="bash"><code>npm login --registry=http://reg.example.com --scope=@myco
</code></pre>

View File

@ -264,6 +264,16 @@ configured workspaces. e.g:</p>
<pre><code>npm run test --workspaces
</code></pre>
<p>Will run the <code>test</code> script in both <code>./packages/a</code> and <code>./packages/b</code>.</p>
<p>Commands will be run in each workspace in the order they appear in your <code>package.json</code></p>
<pre><code>{
"workspaces": [ "packages/a", "packages/b" ]
}
</code></pre>
<p>Order of run is different with:</p>
<pre><code>{
"workspaces": [ "packages/b", "packages/a" ]
}
</code></pre>
<h3 id="ignoring-missing-scripts">Ignoring missing scripts</h3>
<p>It is not required for all of the workspaces to implement scripts run with the <code>npm run</code> command.</p>
<p>By running the command with the <code>--if-present</code> flag, npm will ignore workspaces missing target script.</p>

View File

@ -8,6 +8,7 @@ const semver = require('semver')
const BaseCommand = require('./base-command.js')
const npa = require('npm-package-arg')
const jsonParse = require('json-parse-even-better-errors')
const localeCompare = require('@isaacs/string-locale-compare')('en')
const searchCachePackage = async (path, spec, cacheKeys) => {
const parsed = npa(spec)
@ -212,10 +213,10 @@ class Cache extends BaseCommand {
for (const key of keySet)
results.add(key)
}
[...results].sort((a, b) => a.localeCompare(b, 'en')).forEach(key => this.npm.output(key))
[...results].sort(localeCompare).forEach(key => this.npm.output(key))
return
}
cacheKeys.sort((a, b) => a.localeCompare(b, 'en')).forEach(key => this.npm.output(key))
cacheKeys.sort(localeCompare).forEach(key => this.npm.output(key))
}
}

View File

@ -10,6 +10,7 @@ const writeFile = promisify(fs.writeFile)
const { spawn } = require('child_process')
const { EOL } = require('os')
const ini = require('ini')
const localeCompare = require('@isaacs/string-locale-compare')('en')
// take an array of `[key, value, k2=v2, k3, v3, ...]` and turn into
// { key: value, k2: v2, k3: v3 }
@ -209,7 +210,7 @@ class Config extends BaseCommand {
; Configs like \`//<hostname>/:_authToken\` are auth that is restricted
; to the registry host specified.
${data.split('\n').sort((a, b) => a.localeCompare(b, 'en')).join('\n').trim()}
${data.split('\n').sort(localeCompare).join('\n').trim()}
;;;;
; all available options shown below with default values
@ -238,7 +239,7 @@ ${defData}
if (where === 'default' && !long)
continue
const keys = Object.keys(data).sort((a, b) => a.localeCompare(b, 'en'))
const keys = Object.keys(data).sort(localeCompare)
if (!keys.length)
continue

View File

@ -49,7 +49,7 @@ class Deprecate extends BaseCommand {
}
async deprecate ([pkg, msg]) {
// msg == null becase '' is a valid value, it indicates undeprecate
// msg == null because '' is a valid value, it indicates undeprecate
if (!pkg || msg == null)
throw this.usageError()

View File

@ -3,6 +3,7 @@ const path = require('path')
const openUrl = require('./utils/open-url.js')
const { promisify } = require('util')
const glob = promisify(require('glob'))
const localeCompare = require('@isaacs/string-locale-compare')('en')
const BaseCommand = require('./base-command.js')
@ -82,7 +83,7 @@ class Help extends BaseCommand {
if (aManNumber !== bManNumber)
return aManNumber - bManNumber
return a.localeCompare(b, 'en')
return localeCompare(a, b)
})
const man = mans[0]

4
deps/npm/lib/ls.js vendored
View File

@ -22,6 +22,7 @@ const _problems = Symbol('problems')
const _required = Symbol('required')
const _type = Symbol('type')
const ArboristWorkspaceCmd = require('./workspaces/arborist-cmd.js')
const localeCompare = require('@isaacs/string-locale-compare')('en')
class LS extends ArboristWorkspaceCmd {
/* istanbul ignore next - see test/lib/load-all-commands.js */
@ -503,8 +504,7 @@ const augmentNodesWithMetadata = ({
return node
}
const sortAlphabetically = (a, b) =>
a.pkgid.localeCompare(b.pkgid, 'en')
const sortAlphabetically = ({ pkgid: a }, { pkgid: b }) => localeCompare(a, b)
const humanOutput = ({ color, result, seenItems, unicode }) => {
// we need to traverse the entire tree in order to determine which items

3
deps/npm/lib/npm.js vendored
View File

@ -355,6 +355,3 @@ const npm = module.exports = new class extends EventEmitter {
this.log.showProgress()
}
}()
if (require.main === module)
require('./cli.js')(process)

View File

@ -6,6 +6,7 @@ const color = require('chalk')
const styles = require('ansistyles')
const npa = require('npm-package-arg')
const pickManifest = require('npm-pick-manifest')
const localeCompare = require('@isaacs/string-locale-compare')('en')
const Arborist = require('@npmcli/arborist')
@ -85,7 +86,10 @@ class Outdated extends ArboristWorkspaceCmd {
}))
// sorts list alphabetically
const outdated = this.list.sort((a, b) => a.name.localeCompare(b.name, 'en'))
const outdated = this.list.sort((a, b) => localeCompare(a.name, b.name))
if (outdated.length > 0)
process.exitCode = 1
// return if no outdated packages
if (outdated.length === 0 && !this.npm.config.get('json'))

View File

@ -1,5 +1,6 @@
const { resolve } = require('path')
const Arborist = require('@npmcli/arborist')
const localeCompare = require('@isaacs/string-locale-compare')('en')
const installedDeep = async (npm) => {
const {
@ -15,8 +16,7 @@ const installedDeep = async (npm) => {
return i
})
.filter(i => (i.depth - 1) <= depth)
.sort((a, b) => a.depth - b.depth)
.sort((a, b) => a.depth === b.depth ? a.name.localeCompare(b.name, 'en') : 0)
.sort((a, b) => (a.depth - b.depth) || localeCompare(a.name, b.name))
const res = new Set()
const gArb = new Arborist({ global: true, path: resolve(npm.globalDir, '..') })

View File

@ -1,4 +1,5 @@
const definitions = require('./definitions.js')
const localeCompare = require('@isaacs/string-locale-compare')('en')
const describeAll = () => {
// sort not-deprecated ones to the top
/* istanbul ignore next - typically already sorted in the definitions file,
@ -7,7 +8,7 @@ const describeAll = () => {
const sort = ([keya, {deprecated: depa}], [keyb, {deprecated: depb}]) => {
return depa && !depb ? 1
: !depa && depb ? -1
: keya.localeCompare(keyb, 'en')
: localeCompare(keya, keyb)
}
return Object.entries(definitions).sort(sort)
.map(([key, def]) => def.describe())

View File

@ -1,5 +1,6 @@
const { dirname } = require('path')
const { cmdList } = require('./cmd-list')
const localeCompare = require('@isaacs/string-locale-compare')('en')
module.exports = (npm) => {
const usesBrowser = npm.config.get('viewer') === 'browser'
@ -62,7 +63,7 @@ const usages = (npm) => {
maxLen = Math.max(maxLen, c.length)
return set
}, [])
.sort((a, b) => a[0].localeCompare(b[0], 'en'))
.sort(([a], [b]) => localeCompare(a, b))
.map(([c, usage]) => `\n ${c}${' '.repeat(maxLen - c.length + 1)}${
(usage.split('\n').join('\n' + ' '.repeat(maxLen + 5)))}`)
.join('\n')

View File

@ -4,6 +4,7 @@ const { URL } = require('url')
// attempt to open URL in web-browser, print address otherwise:
const open = async (npm, url, errMsg) => {
url = encodeURI(url)
const browser = npm.config.get('browser')
function printAlternateMsg () {

View File

@ -3,6 +3,10 @@ const ssri = require('ssri')
const npmlog = require('npmlog')
const formatBytes = require('./format-bytes.js')
const columnify = require('columnify')
const localeCompare = require('@isaacs/string-locale-compare')('en', {
sensitivity: 'case',
numeric: true,
})
const logTar = (tarball, opts = {}) => {
const { unicode = false, log = npmlog } = opts
@ -75,12 +79,7 @@ const getContents = async (manifest, tarball) => {
algorithms: ['sha1', 'sha512'],
})
const comparator = (a, b) => {
return a.path.localeCompare(b.path, 'en', {
sensitivity: 'case',
numeric: true,
})
}
const comparator = ({ path: a }, { path: b }) => localeCompare(a, b)
const isUpper = (str) => {
const ch = str.charAt(0)

View File

@ -1,4 +1,4 @@
.TH "NPM\-ACCESS" "1" "September 2021" "" ""
.TH "NPM\-ACCESS" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-access\fR \- Set access level on published packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-ADDUSER" "1" "September 2021" "" ""
.TH "NPM\-ADDUSER" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-adduser\fR \- Add a registry user account
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-AUDIT" "1" "September 2021" "" ""
.TH "NPM\-AUDIT" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-audit\fR \- Run a security audit
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-BIN" "1" "September 2021" "" ""
.TH "NPM\-BIN" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-bin\fR \- Display npm bin folder
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-BUGS" "1" "September 2021" "" ""
.TH "NPM\-BUGS" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-bugs\fR \- Report bugs for a package in a web browser
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-CACHE" "1" "September 2021" "" ""
.TH "NPM\-CACHE" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-cache\fR \- Manipulates packages cache
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-CI" "1" "September 2021" "" ""
.TH "NPM\-CI" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-ci\fR \- Install a project with a clean slate
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-COMPLETION" "1" "September 2021" "" ""
.TH "NPM\-COMPLETION" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-completion\fR \- Tab Completion for npm
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-CONFIG" "1" "September 2021" "" ""
.TH "NPM\-CONFIG" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-config\fR \- Manage the npm configuration files
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-DEDUPE" "1" "September 2021" "" ""
.TH "NPM\-DEDUPE" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-dedupe\fR \- Reduce duplication in the package tree
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-DEPRECATE" "1" "September 2021" "" ""
.TH "NPM\-DEPRECATE" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-deprecate\fR \- Deprecate a version of a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-DIFF" "1" "September 2021" "" ""
.TH "NPM\-DIFF" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-diff\fR \- The registry diff command
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-DIST\-TAG" "1" "September 2021" "" ""
.TH "NPM\-DIST\-TAG" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-dist-tag\fR \- Modify package distribution tags
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-DOCS" "1" "September 2021" "" ""
.TH "NPM\-DOCS" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-docs\fR \- Open documentation for a package in a web browser
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-DOCTOR" "1" "September 2021" "" ""
.TH "NPM\-DOCTOR" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-doctor\fR \- Check your npm environment
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-EDIT" "1" "September 2021" "" ""
.TH "NPM\-EDIT" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-edit\fR \- Edit an installed package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-EXEC" "1" "September 2021" "" ""
.TH "NPM\-EXEC" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-exec\fR \- Run a command from a local or remote npm package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-EXPLAIN" "1" "September 2021" "" ""
.TH "NPM\-EXPLAIN" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-explain\fR \- Explain installed packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-EXPLORE" "1" "September 2021" "" ""
.TH "NPM\-EXPLORE" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-explore\fR \- Browse an installed package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-FIND\-DUPES" "1" "September 2021" "" ""
.TH "NPM\-FIND\-DUPES" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-find-dupes\fR \- Find duplication in the package tree
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-FUND" "1" "September 2021" "" ""
.TH "NPM\-FUND" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-fund\fR \- Retrieve funding information
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-HELP\-SEARCH" "1" "September 2021" "" ""
.TH "NPM\-HELP\-SEARCH" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-help-search\fR \- Search npm help documentation
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-HELP" "1" "September 2021" "" ""
.TH "NPM\-HELP" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-help\fR \- Get help on npm
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-HOOK" "1" "September 2021" "" ""
.TH "NPM\-HOOK" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-hook\fR \- Manage registry hooks
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-INIT" "1" "September 2021" "" ""
.TH "NPM\-INIT" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-init\fR \- Create a package\.json file
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-INSTALL\-CI\-TEST" "1" "September 2021" "" ""
.TH "NPM\-INSTALL\-CI\-TEST" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-install-ci-test\fR \- Install a project with a clean slate and run tests
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-INSTALL\-TEST" "1" "September 2021" "" ""
.TH "NPM\-INSTALL\-TEST" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-install-test\fR \- Install package(s) and run tests
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-INSTALL" "1" "September 2021" "" ""
.TH "NPM\-INSTALL" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-install\fR \- Install a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-LINK" "1" "September 2021" "" ""
.TH "NPM\-LINK" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-link\fR \- Symlink a package folder
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-LOGOUT" "1" "September 2021" "" ""
.TH "NPM\-LOGOUT" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-logout\fR \- Log out of the registry
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-LS" "1" "September 2021" "" ""
.TH "NPM\-LS" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-ls\fR \- List installed packages
.SS Synopsis
@ -26,7 +26,7 @@ example, running \fBnpm ls promzard\fP in npm's source tree will show:
.P
.RS 2
.nf
npm@7\.24\.0 /path/to/npm
npm@8\.0\.0 /path/to/npm
└─┬ init\-package\-json@0\.0\.4
└── promzard@0\.1\.5
.fi

View File

@ -1,4 +1,4 @@
.TH "NPM\-ORG" "1" "September 2021" "" ""
.TH "NPM\-ORG" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-org\fR \- Manage orgs
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-OUTDATED" "1" "September 2021" "" ""
.TH "NPM\-OUTDATED" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-outdated\fR \- Check for outdated packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-OWNER" "1" "September 2021" "" ""
.TH "NPM\-OWNER" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-owner\fR \- Manage package owners
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-PACK" "1" "September 2021" "" ""
.TH "NPM\-PACK" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-pack\fR \- Create a tarball from a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-PING" "1" "September 2021" "" ""
.TH "NPM\-PING" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-ping\fR \- Ping npm registry
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-PKG" "1" "September 2021" "" ""
.TH "NPM\-PKG" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-pkg\fR \- Manages your package\.json
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-PREFIX" "1" "September 2021" "" ""
.TH "NPM\-PREFIX" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-prefix\fR \- Display prefix
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-PROFILE" "1" "September 2021" "" ""
.TH "NPM\-PROFILE" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-profile\fR \- Change settings on your registry profile
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-PRUNE" "1" "September 2021" "" ""
.TH "NPM\-PRUNE" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-prune\fR \- Remove extraneous packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-PUBLISH" "1" "September 2021" "" ""
.TH "NPM\-PUBLISH" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-publish\fR \- Publish a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-REBUILD" "1" "September 2021" "" ""
.TH "NPM\-REBUILD" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-rebuild\fR \- Rebuild a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-REPO" "1" "September 2021" "" ""
.TH "NPM\-REPO" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-repo\fR \- Open package repository page in the browser
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-RESTART" "1" "September 2021" "" ""
.TH "NPM\-RESTART" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-restart\fR \- Restart a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-ROOT" "1" "September 2021" "" ""
.TH "NPM\-ROOT" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-root\fR \- Display npm root
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-RUN\-SCRIPT" "1" "September 2021" "" ""
.TH "NPM\-RUN\-SCRIPT" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-run-script\fR \- Run arbitrary package scripts
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-SEARCH" "1" "September 2021" "" ""
.TH "NPM\-SEARCH" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-search\fR \- Search for packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-SET\-SCRIPT" "1" "September 2021" "" ""
.TH "NPM\-SET\-SCRIPT" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-set-script\fR \- Set tasks in the scripts section of package\.json
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-SHRINKWRAP" "1" "September 2021" "" ""
.TH "NPM\-SHRINKWRAP" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-shrinkwrap\fR \- Lock down dependency versions for publication
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-STAR" "1" "September 2021" "" ""
.TH "NPM\-STAR" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-star\fR \- Mark your favorite packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-STARS" "1" "September 2021" "" ""
.TH "NPM\-STARS" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-stars\fR \- View packages marked as favorites
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-START" "1" "September 2021" "" ""
.TH "NPM\-START" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-start\fR \- Start a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-STOP" "1" "September 2021" "" ""
.TH "NPM\-STOP" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-stop\fR \- Stop a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-TEAM" "1" "September 2021" "" ""
.TH "NPM\-TEAM" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-team\fR \- Manage organization teams and team memberships
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-TEST" "1" "September 2021" "" ""
.TH "NPM\-TEST" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-test\fR \- Test a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-TOKEN" "1" "September 2021" "" ""
.TH "NPM\-TOKEN" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-token\fR \- Manage your authentication tokens
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-UNINSTALL" "1" "September 2021" "" ""
.TH "NPM\-UNINSTALL" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-uninstall\fR \- Remove a package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-UNPUBLISH" "1" "September 2021" "" ""
.TH "NPM\-UNPUBLISH" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-unpublish\fR \- Remove a package from the registry
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-UNSTAR" "1" "September 2021" "" ""
.TH "NPM\-UNSTAR" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-unstar\fR \- Remove an item from your favorite packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-UPDATE" "1" "September 2021" "" ""
.TH "NPM\-UPDATE" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-update\fR \- Update packages
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-VERSION" "1" "September 2021" "" ""
.TH "NPM\-VERSION" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-version\fR \- Bump a package version
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-VIEW" "1" "September 2021" "" ""
.TH "NPM\-VIEW" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-view\fR \- View registry info
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM\-WHOAMI" "1" "September 2021" "" ""
.TH "NPM\-WHOAMI" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm-whoami\fR \- Display npm username
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "NPM" "1" "September 2021" "" ""
.TH "NPM" "1" "October 2021" "" ""
.SH "NAME"
\fBnpm\fR \- javascript package manager
.SS Synopsis
@ -10,7 +10,7 @@ npm <command> [args]
.RE
.SS Version
.P
7\.24\.0
8\.0\.0
.SS Description
.P
npm is the package manager for the Node JavaScript platform\. It puts

View File

@ -1,4 +1,4 @@
.TH "NPX" "1" "September 2021" "" ""
.TH "NPX" "1" "October 2021" "" ""
.SH "NAME"
\fBnpx\fR \- Run a command from a local or remote npm package
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "FOLDERS" "5" "September 2021" "" ""
.TH "FOLDERS" "5" "October 2021" "" ""
.SH "NAME"
\fBfolders\fR \- Folder Structures Used by npm
.SS Description

View File

@ -1,4 +1,4 @@
.TH "INSTALL" "5" "September 2021" "" ""
.TH "INSTALL" "5" "October 2021" "" ""
.SH "NAME"
\fBinstall\fR \- Download and install node and npm
.SS Description

View File

@ -1,4 +1,4 @@
.TH "NPM\-SHRINKWRAP\.JSON" "5" "September 2021" "" ""
.TH "NPM\-SHRINKWRAP\.JSON" "5" "October 2021" "" ""
.SH "NAME"
\fBnpm-shrinkwrap.json\fR \- A publishable lockfile
.SS Description

View File

@ -1,4 +1,4 @@
.TH "NPMRC" "5" "September 2021" "" ""
.TH "NPMRC" "5" "October 2021" "" ""
.SH "NAME"
\fBnpmrc\fR \- The npm config files
.SS Description

View File

@ -1,4 +1,4 @@
.TH "PACKAGE\.JSON" "5" "September 2021" "" ""
.TH "PACKAGE\.JSON" "5" "October 2021" "" ""
.SH "NAME"
\fBpackage.json\fR \- Specifics of npm's package\.json handling
.SS Description

View File

@ -1,4 +1,4 @@
.TH "PACKAGE\-LOCK\.JSON" "5" "September 2021" "" ""
.TH "PACKAGE\-LOCK\.JSON" "5" "October 2021" "" ""
.SH "NAME"
\fBpackage-lock.json\fR \- A manifestation of the manifest
.SS Description
@ -142,7 +142,8 @@ resolved: The place where the package was actually resolved from\. In
the case of packages fetched from the registry, this will be a url to a
tarball\. In the case of git dependencies, this will be the full git url
with commit sha\. In the case of link dependencies, this will be the
location of the link target\.
location of the link target\. \fBregistry\.npmjs\.org\fP is a magic value meaning
"the currently configured registry"\.
.IP \(bu 2
integrity: A \fBsha512\fP or \fBsha1\fP Standard Subresource
Integrity \fIhttps://w3c\.github\.io/webappsec/specs/subresourceintegrity/\fR
@ -215,7 +216,8 @@ dependencies, this is the commit sha\.
.IP \(bu 2
resolved: For registry sources this is path of the tarball relative to
the registry URL\. If the tarball URL isn't on the same server as the
registry URL then this is a complete URL\.
registry URL then this is a complete URL\. \fBregistry\.npmjs\.org\fP is a magic
value meaning "the currently configured registry"\.
.IP \(bu 2
bundled: If true, this is the bundled dependency and will be installed
by the parent module\. When installing, this module will be extracted

View File

@ -1,4 +1,4 @@
.TH "CONFIG" "7" "September 2021" "" ""
.TH "CONFIG" "7" "October 2021" "" ""
.SH "NAME"
\fBconfig\fR \- More than you probably want to know about npm configuration
.SS Description

View File

@ -1,4 +1,4 @@
.TH "DEVELOPERS" "7" "September 2021" "" ""
.TH "DEVELOPERS" "7" "October 2021" "" ""
.SH "NAME"
\fBdevelopers\fR \- Developer Guide
.SS Description

View File

@ -1,4 +1,4 @@
.TH "ORGS" "7" "September 2021" "" ""
.TH "ORGS" "7" "October 2021" "" ""
.SH "NAME"
\fBorgs\fR \- Working with Teams & Orgs
.SS Description

View File

@ -1,4 +1,4 @@
.TH "REGISTRY" "7" "September 2021" "" ""
.TH "REGISTRY" "7" "October 2021" "" ""
.SH "NAME"
\fBregistry\fR \- The JavaScript Package Registry
.SS Description
@ -26,6 +26,13 @@ The registry URL used is determined by the scope of the package (see
npm help \fBscope\fP\|\. If no scope is specified, the default registry is used, which is
supplied by the \fBregistry\fP config parameter\. See npm help \fBconfig\fP,
npm help \fBnpmrc\fP, and npm help \fBconfig\fP for more on managing npm's configuration\.
.P
When the default registry is used in a package\-lock or shrinkwrap is has the
special meaning of "the currently configured registry"\. If you create a lock
file while using the default registry you can switch to another registry and
npm will install packages from the new registry, but if you create a lock
file while using a custom registry packages will be installed from that
registry even after you change to another registry\.
.SS Does npm send any information about me back to the registry?
.P
Yes\.

View File

@ -1,4 +1,4 @@
.TH "REMOVAL" "7" "September 2021" "" ""
.TH "REMOVAL" "7" "October 2021" "" ""
.SH "NAME"
\fBremoval\fR \- Cleaning the Slate
.SS Synopsis

View File

@ -1,4 +1,4 @@
.TH "SCOPE" "7" "September 2021" "" ""
.TH "SCOPE" "7" "October 2021" "" ""
.SH "NAME"
\fBscope\fR \- Scoped packages
.SS Description
@ -97,7 +97,8 @@ desired, with \fBnpm access\fP or on the npmjs\.com website\.
.P
Scopes can be associated with a separate registry\. This allows you to
seamlessly use a mix of packages from the primary npm registry and one or more
private registries, such as npm Enterprise\.
private registries, such as GitHub Packages \fIhttps://github\.com/features/packages\fR or the open source Verdaccio \fIhttps://verdaccio\.org\fR
project\.
.P
You can associate a scope with a registry at login, e\.g\.
.P

View File

@ -1,4 +1,4 @@
.TH "SCRIPTS" "7" "September 2021" "" ""
.TH "SCRIPTS" "7" "October 2021" "" ""
.SH "NAME"
\fBscripts\fR \- How npm handles the "scripts" field
.SS Description

Some files were not shown because too many files have changed in this diff Show More