From 43dd49c9782848c25e5b03448c8a0f923f13c158 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kat=20March=C3=A1n?= Date: Tue, 29 Jan 2019 14:43:00 -0800 Subject: deps: upgrade npm to 6.7.0 PR-URL: https://github.com/nodejs/node/pull/25804 Reviewed-By: Myles Borins --- deps/npm/html/doc/misc/npm-coding-style.html | 6 +- deps/npm/html/doc/misc/npm-config.html | 4 +- deps/npm/html/doc/misc/npm-developers.html | 4 +- deps/npm/html/doc/misc/npm-disputes.html | 14 +-- deps/npm/html/doc/misc/npm-index.html | 154 ++++++++++++++------------- deps/npm/html/doc/misc/npm-orgs.html | 2 +- deps/npm/html/doc/misc/npm-registry.html | 14 +-- deps/npm/html/doc/misc/npm-scope.html | 2 +- deps/npm/html/doc/misc/npm-scripts.html | 6 +- deps/npm/html/doc/misc/removing-npm.html | 2 +- deps/npm/html/doc/misc/semver.html | 37 ++++--- 11 files changed, 129 insertions(+), 116 deletions(-) (limited to 'deps/npm/html/doc/misc') diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index 6005929dc42..3e4632d6789 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -89,7 +89,7 @@ Also use a single space wherever it makes things more readable.

lines. Don't use more spaces than are helpful.

Functions

Use named functions. They make stack traces a lot easier to read.

-

Callbacks, Sync/async Style

+

Callbacks, Sync/async Style

Use the asynchronous/non-blocking versions of things as much as possible. It might make more sense for npm to use the synchronous fs APIs, but this way, the fs and http and child process stuff all uses the same callback-passing @@ -110,7 +110,7 @@ report what's happening so that it's easier to track down where a fault occurs.

Use appropriate log levels. See npm-config(7) and search for "loglevel".

-

Case, naming, etc.

+

Case, naming, etc.

Use lowerCamelCase for multiword identifiers when they refer to objects, functions, methods, properties, or anything not specified in this section.

Use UpperCamelCase for class names (things that you'd pass to "new").

@@ -145,5 +145,5 @@ set to anything."

       - + diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index 91af998a047..d09706648f6 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -259,7 +259,7 @@ disabled when the environment variable NO_COLOR is set to any value since that gives more useful information. To show the outdated status of all packages and dependents, use a large integer value, e.g., npm outdated --depth 9999

-

description

+

description

The npm registry does not try to correlate the information in these headers with any authenticated accounts that may be used in the same requests.

-

Can I run my own private registry?

+

Can I run my own private registry?

Yes!

The easiest way is to replicate the couch database, and use the same (or similar) design doc to implement the APIs.

@@ -61,20 +61,20 @@ to read any published packages, in addition to your private ones, and by default will only publish internally.

If you then want to publish a package for the whole world to see, you can simply override the --registry option for that publish command.

-

I don't want my package published in the official registry. It's private.

+

I don't want my package published in the official registry. It's private.

Set "private": true in your package.json to prevent it from being published at all, or "publishConfig":{"registry":"http://my-internal-registry.local"} to force it to be published only to your internal registry.

See package.json(5) for more info on what goes in the package.json file.

-

Will you replicate from my registry into the public one?

+

Will you replicate from my registry into the public one?

No. If you want things to be public, then publish them into the public registry using npm. What little security there is would be for nought otherwise.

-

Do I have to use couchdb to build a registry that npm can talk to?

+

Do I have to use couchdb to build a registry that npm can talk to?

No, but it's way easier. Basically, yes, you do, or you have to effectively implement the entire CouchDB API anyway.

-

Is there a website or something to see package docs and such?

+

Is there a website or something to see package docs and such?

Yes, head over to https://www.npmjs.com/

SEE ALSO