From 9946519fba73687d34dccd5813808252a1973f3c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kat=20March=C3=A1n?= Date: Sun, 18 Dec 2016 20:22:09 -0800 Subject: deps: upgrade npm to 4.0.5 PR-URL: https://github.com/nodejs/node/pull/10330 Reviewed-By: Myles Borins --- deps/npm/html/doc/README.html | 12 +- deps/npm/html/doc/cli/npm-access.html | 2 +- deps/npm/html/doc/cli/npm-adduser.html | 5 +- deps/npm/html/doc/cli/npm-bin.html | 2 +- deps/npm/html/doc/cli/npm-bugs.html | 2 +- deps/npm/html/doc/cli/npm-build.html | 2 +- deps/npm/html/doc/cli/npm-bundle.html | 2 +- deps/npm/html/doc/cli/npm-cache.html | 2 +- deps/npm/html/doc/cli/npm-completion.html | 2 +- deps/npm/html/doc/cli/npm-config.html | 2 +- deps/npm/html/doc/cli/npm-dedupe.html | 2 +- deps/npm/html/doc/cli/npm-deprecate.html | 2 +- deps/npm/html/doc/cli/npm-dist-tag.html | 3 +- deps/npm/html/doc/cli/npm-docs.html | 2 +- deps/npm/html/doc/cli/npm-edit.html | 2 +- deps/npm/html/doc/cli/npm-explore.html | 2 +- deps/npm/html/doc/cli/npm-help-search.html | 2 +- deps/npm/html/doc/cli/npm-help.html | 2 +- deps/npm/html/doc/cli/npm-init.html | 2 +- deps/npm/html/doc/cli/npm-install-test.html | 2 +- deps/npm/html/doc/cli/npm-install.html | 7 +- deps/npm/html/doc/cli/npm-link.html | 2 +- deps/npm/html/doc/cli/npm-logout.html | 4 +- deps/npm/html/doc/cli/npm-ls.html | 4 +- deps/npm/html/doc/cli/npm-outdated.html | 2 +- deps/npm/html/doc/cli/npm-owner.html | 2 +- deps/npm/html/doc/cli/npm-pack.html | 2 +- deps/npm/html/doc/cli/npm-ping.html | 2 +- deps/npm/html/doc/cli/npm-prefix.html | 2 +- deps/npm/html/doc/cli/npm-prune.html | 2 +- deps/npm/html/doc/cli/npm-publish.html | 4 +- deps/npm/html/doc/cli/npm-rebuild.html | 2 +- deps/npm/html/doc/cli/npm-repo.html | 2 +- deps/npm/html/doc/cli/npm-restart.html | 2 +- deps/npm/html/doc/cli/npm-root.html | 2 +- deps/npm/html/doc/cli/npm-run-script.html | 9 +- deps/npm/html/doc/cli/npm-search.html | 72 ++++++++++-- deps/npm/html/doc/cli/npm-shrinkwrap.html | 18 +-- deps/npm/html/doc/cli/npm-star.html | 2 +- deps/npm/html/doc/cli/npm-stars.html | 2 +- deps/npm/html/doc/cli/npm-start.html | 2 +- deps/npm/html/doc/cli/npm-stop.html | 2 +- deps/npm/html/doc/cli/npm-tag.html | 67 ----------- deps/npm/html/doc/cli/npm-team.html | 2 +- deps/npm/html/doc/cli/npm-test.html | 4 +- deps/npm/html/doc/cli/npm-uninstall.html | 2 +- deps/npm/html/doc/cli/npm-unpublish.html | 2 +- deps/npm/html/doc/cli/npm-update.html | 2 +- deps/npm/html/doc/cli/npm-version.html | 9 +- deps/npm/html/doc/cli/npm-view.html | 2 +- deps/npm/html/doc/cli/npm-whoami.html | 2 +- deps/npm/html/doc/cli/npm.html | 6 +- deps/npm/html/doc/files/npm-folders.html | 2 +- deps/npm/html/doc/files/npm-global.html | 2 +- deps/npm/html/doc/files/npm-json.html | 14 +-- deps/npm/html/doc/files/npmrc.html | 8 +- deps/npm/html/doc/files/package.json.html | 14 +-- deps/npm/html/doc/index.html | 4 +- deps/npm/html/doc/misc/npm-coding-style.html | 2 +- deps/npm/html/doc/misc/npm-config.html | 60 +++++----- deps/npm/html/doc/misc/npm-developers.html | 2 +- deps/npm/html/doc/misc/npm-disputes.html | 168 +++++++++++++++------------ deps/npm/html/doc/misc/npm-index.html | 4 +- deps/npm/html/doc/misc/npm-orgs.html | 2 +- deps/npm/html/doc/misc/npm-registry.html | 22 +++- deps/npm/html/doc/misc/npm-scope.html | 2 +- deps/npm/html/doc/misc/npm-scripts.html | 30 ++++- deps/npm/html/doc/misc/removing-npm.html | 2 +- deps/npm/html/doc/misc/semver.html | 2 +- 69 files changed, 353 insertions(+), 287 deletions(-) delete mode 100644 deps/npm/html/doc/cli/npm-tag.html (limited to 'deps/npm/html') diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index 4aa3cc5e47..0d97ebb015 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -10,7 +10,7 @@

npm

a JavaScript package manager

-

Build Status

+

Build Status

SYNOPSIS

This is just enough info to get you up and running.

Much more info available via npm help once it's installed.

@@ -27,11 +27,11 @@ registries.

terms of use for the default public registry are available at https://www.npmjs.com.

Super Easy Install

-

npm is bundled with node.

+

npm is bundled with node.

Windows Computers

-

Get the MSI. npm is in it.

+

Get the MSI. npm is in it.

Apple Macintosh Computers

-

Get the pkg. npm is in it.

+

Get the pkg. npm is in it.

Other Sorts of Unices

Run make install. npm will be installed with node.

If you want a more fancy pants install (a different version, customized @@ -106,7 +106,7 @@ you should read this

Be sure to include all of the output from the npm command that didn't work as expected. The npm-debug.log file is also helpful to provide.

-

You can also look for isaacs in #node.js on irc://irc.freenode.net. He +

You can also look for isaacs in #node.js on irc://irc.freenode.net. She will no doubt tell you to put the output in a gist or email.

SEE ALSO

    @@ -126,5 +126,5 @@ will no doubt tell you to put the output in a gist or email.

           - + diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html index fdc0cb756e..80a1da3423 100644 --- a/deps/npm/html/doc/cli/npm-access.html +++ b/deps/npm/html/doc/cli/npm-access.html @@ -84,5 +84,5 @@ with an HTTP 402 status code (logically enough), unless you use        - + diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html index 9ade2746aa..9f6ccada72 100644 --- a/deps/npm/html/doc/cli/npm-adduser.html +++ b/deps/npm/html/doc/cli/npm-adduser.html @@ -30,7 +30,8 @@ your existing record.

    registry

    Default: https://registry.npmjs.org/

    The base URL of the npm package registry. If scope is also specified, -this registry will only be used for packages with that scope. See npm-scope(7).

    +this registry will only be used for packages with that scope. scope defaults +to the scope of the project directory you're currently in, if any. See npm-scope(7).

    scope

    Default: none

    If specified, the user and login credentials given will be associated @@ -72,5 +73,5 @@ over any global configuration.

           - + diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html index 8d408216a9..57a372baff 100644 --- a/deps/npm/html/doc/cli/npm-bin.html +++ b/deps/npm/html/doc/cli/npm-bin.html @@ -35,5 +35,5 @@        - + diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html index d5b9edea56..607d245c27 100644 --- a/deps/npm/html/doc/cli/npm-bugs.html +++ b/deps/npm/html/doc/cli/npm-bugs.html @@ -55,5 +55,5 @@ a package.json in the current folder and use the name        - + diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html index 73c796c233..5f89aca15c 100644 --- a/deps/npm/html/doc/cli/npm-build.html +++ b/deps/npm/html/doc/cli/npm-build.html @@ -40,5 +40,5 @@ directly, run:

           - + diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html index 1f256d222d..41a4229c99 100644 --- a/deps/npm/html/doc/cli/npm-bundle.html +++ b/deps/npm/html/doc/cli/npm-bundle.html @@ -31,5 +31,5 @@ install packages into the local space.

           - + diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html index 883f07ffb5..1b6b34adb9 100644 --- a/deps/npm/html/doc/cli/npm-cache.html +++ b/deps/npm/html/doc/cli/npm-cache.html @@ -81,5 +81,5 @@ they do not make an HTTP request to the registry.

           - + diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html index 1be550a7dd..2f5cad2d33 100644 --- a/deps/npm/html/doc/cli/npm-completion.html +++ b/deps/npm/html/doc/cli/npm-completion.html @@ -43,5 +43,5 @@ completions based on the arguments.

           - + diff --git a/deps/npm/html/doc/cli/npm-config.html b/deps/npm/html/doc/cli/npm-config.html index 8940698b4a..9036bf84d5 100644 --- a/deps/npm/html/doc/cli/npm-config.html +++ b/deps/npm/html/doc/cli/npm-config.html @@ -67,5 +67,5 @@ global config.

           - + diff --git a/deps/npm/html/doc/cli/npm-dedupe.html b/deps/npm/html/doc/cli/npm-dedupe.html index 40cbd9f23a..e822dd5e65 100644 --- a/deps/npm/html/doc/cli/npm-dedupe.html +++ b/deps/npm/html/doc/cli/npm-dedupe.html @@ -61,5 +61,5 @@ result in new modules being installed.

           - + diff --git a/deps/npm/html/doc/cli/npm-deprecate.html b/deps/npm/html/doc/cli/npm-deprecate.html index a8476c51b1..8402c36fca 100644 --- a/deps/npm/html/doc/cli/npm-deprecate.html +++ b/deps/npm/html/doc/cli/npm-deprecate.html @@ -38,5 +38,5 @@ something like this:

           - + diff --git a/deps/npm/html/doc/cli/npm-dist-tag.html b/deps/npm/html/doc/cli/npm-dist-tag.html index 3b66f87f78..b1b5c038bf 100644 --- a/deps/npm/html/doc/cli/npm-dist-tag.html +++ b/deps/npm/html/doc/cli/npm-dist-tag.html @@ -66,7 +66,6 @@ example, v1.4 cannot be used as a tag, because it is interpreted by begin with a number or the letter v.

    SEE ALSO

      -
    • npm-tag(1)
    • npm-publish(1)
    • npm-install(1)
    • npm-dedupe(1)
      • @@ -87,5 +86,5 @@ begin with a number or the letter v.

             - + diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html index 265c35be15..a713ca1f3a 100644 --- a/deps/npm/html/doc/cli/npm-docs.html +++ b/deps/npm/html/doc/cli/npm-docs.html @@ -56,5 +56,5 @@ the current folder and use the name property.

             - + diff --git a/deps/npm/html/doc/cli/npm-edit.html b/deps/npm/html/doc/cli/npm-edit.html index 60e0a3b516..db4eba4111 100644 --- a/deps/npm/html/doc/cli/npm-edit.html +++ b/deps/npm/html/doc/cli/npm-edit.html @@ -49,5 +49,5 @@ or "notepad" on Windows.        - + diff --git a/deps/npm/html/doc/cli/npm-explore.html b/deps/npm/html/doc/cli/npm-explore.html index 29d5829b5d..2fb651064c 100644 --- a/deps/npm/html/doc/cli/npm-explore.html +++ b/deps/npm/html/doc/cli/npm-explore.html @@ -49,5 +49,5 @@ Windows        - + diff --git a/deps/npm/html/doc/cli/npm-help-search.html b/deps/npm/html/doc/cli/npm-help-search.html index 107687584d..7a7980a97d 100644 --- a/deps/npm/html/doc/cli/npm-help-search.html +++ b/deps/npm/html/doc/cli/npm-help-search.html @@ -45,5 +45,5 @@ where the terms were found in the documentation.

             - + diff --git a/deps/npm/html/doc/cli/npm-help.html b/deps/npm/html/doc/cli/npm-help.html index feb154a521..7249903ccc 100644 --- a/deps/npm/html/doc/cli/npm-help.html +++ b/deps/npm/html/doc/cli/npm-help.html @@ -50,5 +50,5 @@ matches are equivalent to specifying a topic name.

             - + diff --git a/deps/npm/html/doc/cli/npm-init.html b/deps/npm/html/doc/cli/npm-init.html index 5474d8392a..b4cec6b416 100644 --- a/deps/npm/html/doc/cli/npm-init.html +++ b/deps/npm/html/doc/cli/npm-init.html @@ -48,5 +48,5 @@ defaults and not prompt you for any options.

             - + diff --git a/deps/npm/html/doc/cli/npm-install-test.html b/deps/npm/html/doc/cli/npm-install-test.html index 428e0c7739..d283317a71 100644 --- a/deps/npm/html/doc/cli/npm-install-test.html +++ b/deps/npm/html/doc/cli/npm-install-test.html @@ -42,5 +42,5 @@ takes exactly the same arguments as npm install.

             - + diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html index 8c4575f949..c647781dcf 100644 --- a/deps/npm/html/doc/cli/npm-install.html +++ b/deps/npm/html/doc/cli/npm-install.html @@ -269,6 +269,9 @@ privately for itself.

      See npm-folders(5) for a more detailed description of the specific folder structures that npm creates.

      Limitations of npm's Install Algorithm

      +

      npm will refuse to install any package with an identical name to the +current package. This can be overridden with the --force flag, but in +most cases can simply be addressed by changing the local package name.

      There are some very rare and pathological edge-cases where a cycle can cause npm to try to install a never-ending tree of packages. Here is the simplest case:

      @@ -296,7 +299,7 @@ affects a real use-case, it will be investigated.

    • npm-config(7)
    • npmrc(5)
    • npm-registry(7)
      • -
    • npm-tag(1)
      • +
    • npm-dist-tag(1)
    • npm-uninstall(1)
    • npm-shrinkwrap(1)
    • package.json(5)
      • @@ -313,5 +316,5 @@ affects a real use-case, it will be investigated.

             - + diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html index d7aed7df34..f10b790bc2 100644 --- a/deps/npm/html/doc/cli/npm-link.html +++ b/deps/npm/html/doc/cli/npm-link.html @@ -74,5 +74,5 @@ include that scope, e.g.

             - + diff --git a/deps/npm/html/doc/cli/npm-logout.html b/deps/npm/html/doc/cli/npm-logout.html index a6d86e64b5..6543b57851 100644 --- a/deps/npm/html/doc/cli/npm-logout.html +++ b/deps/npm/html/doc/cli/npm-logout.html @@ -27,7 +27,7 @@ connected to that scope, if set.

      The base URL of the npm package registry. If scope is also specified, it takes precedence.

      scope

      -

      Default: none

      +

      Default: The scope of your current project, if any, otherwise none.

      If specified, you will be logged out of the specified scope. See npm-scope(7).

      npm logout --scope=@myco

      SEE ALSO

      @@ -51,5 +51,5 @@ it takes precedence.

             - + diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html index e3e3e60343..1b5d61bd38 100644 --- a/deps/npm/html/doc/cli/npm-ls.html +++ b/deps/npm/html/doc/cli/npm-ls.html @@ -21,7 +21,7 @@ installed, as well as their dependencies, in a tree-structure.

      limit the results to only the paths to the packages named. Note that nested packages will also show the paths to the specified packages. For example, running npm ls promzard in npm's source tree will show:

      -
      npm@3.10.10 /path/to/npm
+
      npm@4.0.5 /path/to/npm
 └─┬ init-package-json@0.0.4
   └── promzard@0.1.5
 
      It will print out extraneous, missing, and invalid packages.
      
@@ -104,5 +104,5 @@ project.
      
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html
index 5c06e18fb3..04a0da5155 100644
--- a/deps/npm/html/doc/cli/npm-outdated.html
+++ b/deps/npm/html/doc/cli/npm-outdated.html
@@ -116,5 +116,5 @@ project.
      
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html
index 9ec584f4ec..9f6d4db959 100644
--- a/deps/npm/html/doc/cli/npm-owner.html
+++ b/deps/npm/html/doc/cli/npm-owner.html
@@ -51,5 +51,5 @@ that is not implemented at this time.
      
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html
index 74682f5281..92cea26747 100644
--- a/deps/npm/html/doc/cli/npm-pack.html
+++ b/deps/npm/html/doc/cli/npm-pack.html
@@ -41,5 +41,5 @@ overwritten the second time.
      
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html
index b48db8ab63..f094762e62 100644
--- a/deps/npm/html/doc/cli/npm-ping.html
+++ b/deps/npm/html/doc/cli/npm-ping.html
@@ -32,5 +32,5 @@
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html
index 171c7ca263..906de75ff8 100644
--- a/deps/npm/html/doc/cli/npm-prefix.html
+++ b/deps/npm/html/doc/cli/npm-prefix.html
@@ -38,5 +38,5 @@ to contain a package.json file unless -g is also specified.
      
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html
index 5000f2c75c..9e40f28103 100644
--- a/deps/npm/html/doc/cli/npm-prune.html
+++ b/deps/npm/html/doc/cli/npm-prune.html
@@ -40,5 +40,5 @@ negate NODE_ENV being set to production.
      
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html
index c3272d3cdb..a6959ce0a4 100644
--- a/deps/npm/html/doc/cli/npm-publish.html
+++ b/deps/npm/html/doc/cli/npm-publish.html
@@ -61,7 +61,7 @@ packs them into a tarball to be uploaded to the registry.
      
 
    • npm-adduser(1)
      • 
 
    • npm-owner(1)
      • 
 
    • npm-deprecate(1)
      • 
-
    • npm-tag(1)
      • 
+
    • npm-dist-tag(1)
      • 
 
    • npm-pack(1)
      •
    @@ -76,5 +76,5 @@ packs them into a tarball to be uploaded to the registry.

           - + diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html index c975efca6b..b2d0670189 100644 --- a/deps/npm/html/doc/cli/npm-rebuild.html +++ b/deps/npm/html/doc/cli/npm-rebuild.html @@ -35,5 +35,5 @@ the new binary.

           - + diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html index 30b18957ca..83af687516 100644 --- a/deps/npm/html/doc/cli/npm-repo.html +++ b/deps/npm/html/doc/cli/npm-repo.html @@ -41,5 +41,5 @@ a package.json in the current folder and use the name        - + diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html index ceb270c6d8..6d4c455659 100644 --- a/deps/npm/html/doc/cli/npm-restart.html +++ b/deps/npm/html/doc/cli/npm-restart.html @@ -53,5 +53,5 @@ behavior will be accompanied by an increase in major version number

           - + diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html index 44c63f0c18..343790ab57 100644 --- a/deps/npm/html/doc/cli/npm-root.html +++ b/deps/npm/html/doc/cli/npm-root.html @@ -35,5 +35,5 @@        - + diff --git a/deps/npm/html/doc/cli/npm-run-script.html b/deps/npm/html/doc/cli/npm-run-script.html index 27fcfc9345..d68504647a 100644 --- a/deps/npm/html/doc/cli/npm-run-script.html +++ b/deps/npm/html/doc/cli/npm-run-script.html @@ -39,8 +39,11 @@ you should write:

    "scripts": {"test": "tap test/\*.js"}

    instead of "scripts": {"test": "node_modules/.bin/tap test/\*.js"} to run your tests.

    npm run sets the NODE environment variable to the node executable with -which npm is executed. Also, the directory within which it resides is added to the -PATH, if the node executable is not in the PATH.

    +which npm is executed. Also, if the --scripts-prepend-node-path is passed, +the directory within which node resides is added to the +PATH. If --scripts-prepend-node-path=auto is passed (which has been the +default in npm v3), this is only performed when that node executable is +not found in the PATH.

    If you try to run a script without having a node_modules directory and it fails, you will be given a warning to run npm install, just in case you've forgotten.

    SEE ALSO

    @@ -63,5 +66,5 @@ you will be given a warning to run npm install, just in case you        - + diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html index ed10e4c422..015d4a3ddb 100644 --- a/deps/npm/html/doc/cli/npm-search.html +++ b/deps/npm/html/doc/cli/npm-search.html @@ -11,15 +11,47 @@

    npm-search

    Search for packages

    SYNOPSIS

    -
    npm search [-l|--long] [search terms ...]
+
    npm search [-l|--long] [--json] [--parseable] [--no-description] [search terms ...]
 
 aliases: s, se, find
 
    DESCRIPTION
    
-
    Search the registry for packages matching the search terms.
    
-
    If a term starts with /, then it's interpreted as a regular expression.
-A trailing / will be ignored in this case.  (Note that many regular
-expression characters must be escaped or quoted in most shells.)
    
+
    Search the registry for packages matching the search terms. npm search
+performs a linear, incremental, lexically-ordered search through package
+metadata for all files in the registry. If color is enabled, it will further
+highlight the matches in the results.
    
+
    Additionally, using the --searchopts and --searchexclude options paired with
+more search terms will respectively include and exclude further patterns. The
+main difference between --searchopts and the standard search terms is that the
+former does not highlight results in the output and can be used for more
+fine-grained filtering. Additionally, both of these can be added to .npmrc for
+default search filtering behavior.
    
+
    Search also allows targeting of maintainers in search results, by prefixing
+their npm username with =.
    
+
    If a term starts with /, then it's interpreted as a regular expression and
+supports standard JavaScript RegExp syntax. A trailing / will be ignored in
+this case. (Note that many regular expression characters must be escaped or
+quoted in most shells.)
    
+
    A Note on caching
    
 
    CONFIGURATION
    
+
    description
    
+
      
+
    • Default: true
      • 
+
    • Type: Boolean
      • 
+
    
+
    Used as --no-description, disables search matching in package descriptions and
+suppresses display of that field in results.
    
+
    json
    
+
      
+
    • Default: false
      • 
+
    • Type: Boolean
      • 
+
    
+
    Output search results as a JSON array.
    
+
    parseable
    
+
      
+
    • Default: false
      • 
+
    • Type: Boolean
      • 
+
    
+
    Output search results as lines with tab-separated columns.
    
 
    long
    
 
      
 
    • Default: false
      • 
@@ -29,14 +61,34 @@ expression characters must be escaped or quoted in most shells.)
      
 lines. When disabled (default) search results are truncated to fit
 neatly on a single line. Modules with extremely long names will
 fall on multiple lines.
      
+
      searchopts
      
+
        
+
      • Default: ""
        • 
+
      • Type: String
        • 
+
      
+
      Space-separated options that are always passed to search.
      
+
      searchexclude
      
+
        
+
      • Default: ""
        • 
+
      • Type: String
        • 
+
      
+
      Space-separated options that limit the results from search.
      
+
      searchstaleness
      
+
        
+
      • Default: 900 (15 minutes)
        • 
+
      • Type: Number
        • 
+
      
+
      The age of the cache, in seconds, before another registry request is made.
      
 
      registry
      
 
-
      Search the specified registry for modules. If you have configured npm to point to a different default registry,
-such as your internal private module repository, npm search will default to that registry when searching.
-Pass a different registry url such as the default above in order to override this setting.
      
+
      Search the specified registry for modules. If you have configured npm to point
+to a different default registry, such as your internal private module
+repository, npm search will default to that registry when searching. Pass a
+different registry url such as the default above in order to override this
+setting.
      
 
      SEE ALSO
      
 
        
 
      • npm-registry(7)
        • 
@@ -57,5 +109,5 @@ Pass a different registry url such as the default above in order to override thi
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html
index bfe3410125..0f80895acf 100644
--- a/deps/npm/html/doc/cli/npm-shrinkwrap.html
+++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html
@@ -139,12 +139,16 @@ already installed, since that would result in a shrinkwrap that
 wouldn't actually work. Similarly, the command will fail if there are
 extraneous packages (not referenced by package.json), since that would
 indicate that package.json is not correct.
        
-
        Since npm shrinkwrap is intended to lock down your dependencies for
-production use, devDependencies will not be included unless you
-explicitly set the --dev flag when you run npm shrinkwrap.  If
-installed devDependencies are excluded, then npm will print a
-warning.  If you want them to be installed with your module by
-default, please consider adding them to dependencies instead.
        
+
        Starting with npm v4.0.1, devDependencies are included when you run
+npm shrinkwrap and follow the usual rules as to when they're installed.
+As of npm v3.10.8, if you run npm install --only=production or
+npm install --production with a shrinkwrap including your development
+dependencies they won't be installed. Similarly, if the environment
+variable NODE_ENV is production then they won't be installed. If you
+need compatibility with versions of npm prior to v3.10.8 or otherwise
+don't want them in your shrinkwrap you can exclude development
+dependencies with:
+npm shrinkwrap --only=prod or npm shrinkwrap --production.
        
 
        If shrinkwrapped package A depends on shrinkwrapped package B, B's
 shrinkwrap will not be used as part of the installation of A. However,
 because A's shrinkwrap is constructed from a valid installation of B
@@ -176,5 +180,5 @@ contents rather than versions.
        
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html
index 01c593c461..2564d61dfc 100644
--- a/deps/npm/html/doc/cli/npm-star.html
+++ b/deps/npm/html/doc/cli/npm-star.html
@@ -36,5 +36,5 @@ a vaguely positive way to show that you care.
        
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html
index 4d470fd4ba..a4889bd84d 100644
--- a/deps/npm/html/doc/cli/npm-stars.html
+++ b/deps/npm/html/doc/cli/npm-stars.html
@@ -36,5 +36,5 @@ you will most certainly enjoy this command.
        
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html
index f193608014..65c229ec95 100644
--- a/deps/npm/html/doc/cli/npm-start.html
+++ b/deps/npm/html/doc/cli/npm-start.html
@@ -39,5 +39,5 @@ more details.
        
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html
index 082b2560c7..277b5a845e 100644
--- a/deps/npm/html/doc/cli/npm-stop.html
+++ b/deps/npm/html/doc/cli/npm-stop.html
@@ -34,5 +34,5 @@
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-tag.html b/deps/npm/html/doc/cli/npm-tag.html
deleted file mode 100644
index 2270e1e3f1..0000000000
--- a/deps/npm/html/doc/cli/npm-tag.html
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-  npm-tag
-  
-  
-  
-  
-
-  
-    
        
-
-
        npm-tag
         
        Tag a published version
        
-
        SYNOPSIS
        
-
        [DEPRECATED] npm tag <name>@<version> [<tag>]
-See `dist-tag`
-
        DESCRIPTION
        
-
        THIS COMMAND IS DEPRECATED. See npm-dist-tag(1) for details.
        
-
        Tags the specified version of the package with the specified tag, or the
---tag config if not specified.
        
-
        A tag can be used when installing packages as a reference to a version instead
-of using a specific version number:
        
-
        npm install <name>@<tag>
-
        When installing dependencies, a preferred tagged version may be specified:
        
-
        npm install --tag <tag>
-
        This also applies to npm dedupe.
        
-
        Publishing a package always sets the "latest" tag to the published version.
        
-
        PURPOSE
        
-
        Tags can be used to provide an alias instead of version numbers.  For
-example, npm currently uses the tag "next" to identify the upcoming
-version, and the tag "latest" to identify the current version.
        
-
        A project might choose to have multiple streams of development, e.g.,
-"stable", "canary".
        
-
        CAVEATS
        
-
        Tags must share a namespace with version numbers, because they are
-specified in the same slot: npm install <pkg>@<version> vs npm
-install <pkg>@<tag>.
        
-
        Tags that can be interpreted as valid semver ranges will be
-rejected. For example, v1.4 cannot be used as a tag, because it is
-interpreted by semver as >=1.4.0 <1.5.0.  See
-https://github.com/npm/npm/issues/6082.
        
-
        The simplest way to avoid semver problems with tags is to use tags
-that do not begin with a number or the letter v.
        
-
        SEE ALSO
        
-
-
-
        
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html
index 02dffaae03..2fea57d08e 100644
--- a/deps/npm/html/doc/cli/npm-team.html
+++ b/deps/npm/html/doc/cli/npm-team.html
@@ -67,5 +67,5 @@ use the npm access command to grant or revoke the appropriate permi
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html
index c15a2fe233..041ce2130b 100644
--- a/deps/npm/html/doc/cli/npm-test.html
+++ b/deps/npm/html/doc/cli/npm-test.html
@@ -16,8 +16,6 @@
   aliases: t, tst

    DESCRIPTION

    This runs a package's "test" script, if one was provided.

    -

    To run tests as a condition of installation, set the npat config to -true.

    SEE ALSO

    • npm-run-script(1)
      • @@ -38,5 +36,5 @@ true.

             - + diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html index 1ed389ac26..b1d9de7809 100644 --- a/deps/npm/html/doc/cli/npm-uninstall.html +++ b/deps/npm/html/doc/cli/npm-uninstall.html @@ -60,5 +60,5 @@ npm uninstall dtrace-provider --save-optional        - + diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html index 4e085352ad..147e42221a 100644 --- a/deps/npm/html/doc/cli/npm-unpublish.html +++ b/deps/npm/html/doc/cli/npm-unpublish.html @@ -47,5 +47,5 @@ package again, a new version number must be used.

             - + diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html index 809475745e..c2b8b18d48 100644 --- a/deps/npm/html/doc/cli/npm-update.html +++ b/deps/npm/html/doc/cli/npm-update.html @@ -118,5 +118,5 @@ be downgraded.

             - + diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html index bc58045dc7..adbfb7ab7c 100644 --- a/deps/npm/html/doc/cli/npm-version.html +++ b/deps/npm/html/doc/cli/npm-version.html @@ -79,6 +79,13 @@ and tag up to the server, and deletes the build/temp directory.

    • Type: Boolean

    Commit and tag the version change.

    +

    sign-git-tag

    +
      +
    • Default: false
      • +
    • Type: Boolean
      • +
    +

    Pass the -s flag to git to sign the tag.

    +

    Note that you must have a default GPG key set up in your git config for this to work properly.

    SEE ALSO

    • npm-init(1)
      • @@ -100,5 +107,5 @@ and tag up to the server, and deletes the build/temp directory.

             - + diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html index 9b7651fcce..f1de2303d0 100644 --- a/deps/npm/html/doc/cli/npm-view.html +++ b/deps/npm/html/doc/cli/npm-view.html @@ -86,5 +86,5 @@ the field name.

             - + diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html index cc30465997..50ff32f00c 100644 --- a/deps/npm/html/doc/cli/npm-whoami.html +++ b/deps/npm/html/doc/cli/npm-whoami.html @@ -33,5 +33,5 @@        - + diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html index 08b24220f3..44685d4a29 100644 --- a/deps/npm/html/doc/cli/npm.html +++ b/deps/npm/html/doc/cli/npm.html @@ -13,7 +13,7 @@

      SYNOPSIS

      npm <command> [args]

      VERSION

      -

      3.10.10

      +

      4.0.5

      DESCRIPTION

      npm is the package manager for the Node JavaScript platform. It puts modules in place so that node can find them, and manages dependency @@ -126,7 +126,7 @@ will no doubt tell you to put the output in a gist or email.

      Isaac Z. Schlueter :: isaacs :: @izs :: -i@izs.me

      +i@izs.me

      SEE ALSO

      For example, these are all valid:

      @@ -357,8 +357,8 @@ included. For example:

      "name": "foo", "version": "0.0.0", "dependencies": { - "express": "visionmedia/express", - "mocha": "visionmedia/mocha#4727d357ea", + "express": "expressjs/express", + "mocha": "mochajs/mocha#4727d357ea", "module": "user/repo#feature\/branch" } } @@ -392,7 +392,7 @@ object.

      from the root of a package, and can be managed like any other npm configuration param. See npm-config(7) for more on the topic.

      For build steps that are not platform-specific, such as compiling -CoffeeScript or other languages to JavaScript, use the prepublish +CoffeeScript or other languages to JavaScript, use the prepare script to do this, and make the required package a devDependency.

      For example:

      { "name": "ethopia-waza",
@@ -402,11 +402,11 @@ script to do this, and make the required package a devDependency.
      
     "coffee-script": "~1.6.3"
   },
   "scripts": {
-    "prepublish": "coffee -o lib/ -c src/waza.coffee"
+    "prepare": "coffee -o lib/ -c src/waza.coffee"
   },
   "main": "lib/waza.js"
 }
-

      The prepublish script will be run before publishing, so that users +

      The prepare script will be run before publishing, so that users can consume the functionality without requiring them to compile it themselves. In dev mode (ie, locally running npm install), it'll run this script as well, so that you can test it easily.

      @@ -586,5 +586,5 @@ ignored.

             - + diff --git a/deps/npm/html/doc/files/npmrc.html b/deps/npm/html/doc/files/npmrc.html index 151b0c0079..8385a103a3 100644 --- a/deps/npm/html/doc/files/npmrc.html +++ b/deps/npm/html/doc/files/npmrc.html @@ -35,11 +35,7 @@ override the setting in the globalconfig file.

      example:

      key[] = "first value"
 key[] = "second value"
-

      NOTE: Because local (per-project or per-user) .npmrc files can contain -sensitive credentials, they must be readable and writable only by your user -account (i.e. must have a mode of 0600), otherwise they will be ignored by -npm!

      -

      Comments

      +

      Comments

      Lines in .npmrc files are interpreted as comments when they begin with a ; or # character. .npmrc files are parsed by npm/ini, which specifies this comment syntax.

      For example:

      # last modified: 01 Jan 2016
@@ -89,5 +85,5 @@ manner.
      
   
    
 
-
+
 
diff --git a/deps/npm/html/doc/files/package.json.html b/deps/npm/html/doc/files/package.json.html
index 3894c9ead6..392d8552f8 100644
--- a/deps/npm/html/doc/files/package.json.html
+++ b/deps/npm/html/doc/files/package.json.html
@@ -317,7 +317,7 @@ tarball or git URL.
      
 
    • range1 || range2 Passes if either range1 or range2 are satisfied.
      • 
 
    • git... See 'Git URLs as Dependencies' below
      • 
 
    • user/repo See 'GitHub URLs' below
      • 
-
    • tag A specific version tagged and published as tag  See npm-tag(1)
      • 
+
    • tag A specific version tagged and published as tag  See npm-dist-tag(1)
      • 
 
    • path/path/path See Local Paths below
      •

    For example, these are all valid:

    @@ -357,8 +357,8 @@ included. For example:

    "name": "foo", "version": "0.0.0", "dependencies": { - "express": "visionmedia/express", - "mocha": "visionmedia/mocha#4727d357ea", + "express": "expressjs/express", + "mocha": "mochajs/mocha#4727d357ea", "module": "user/repo#feature\/branch" } } @@ -392,7 +392,7 @@ object.

    from the root of a package, and can be managed like any other npm configuration param. See npm-config(7) for more on the topic.

    For build steps that are not platform-specific, such as compiling -CoffeeScript or other languages to JavaScript, use the prepublish +CoffeeScript or other languages to JavaScript, use the prepare script to do this, and make the required package a devDependency.

    For example:

    { "name": "ethopia-waza",
@@ -402,11 +402,11 @@ script to do this, and make the required package a devDependency.
    
     "coffee-script": "~1.6.3"
   },
   "scripts": {
-    "prepublish": "coffee -o lib/ -c src/waza.coffee"
+    "prepare": "coffee -o lib/ -c src/waza.coffee"
   },
   "main": "lib/waza.js"
 }
-

    The prepublish script will be run before publishing, so that users +

    The prepare script will be run before publishing, so that users can consume the functionality without requiring them to compile it themselves. In dev mode (ie, locally running npm install), it'll run this script as well, so that you can test it easily.

    @@ -586,5 +586,5 @@ ignored.

           - + diff --git a/deps/npm/html/doc/index.html b/deps/npm/html/doc/index.html index 394e371da4..83baa43e6e 100644 --- a/deps/npm/html/doc/index.html +++ b/deps/npm/html/doc/index.html @@ -98,8 +98,6 @@

    Start a package

    npm-stop(1)

    Stop a package

    -

    npm-tag(1)

    -

    Tag a published version

    npm-team(1)

    Manage organization teams and team memberships

    npm-test(1)

    @@ -162,5 +160,5 @@        - + diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index 93ab1a0e18..0873b5f82f 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -153,5 +153,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 75720461f7..c4dca1bc18 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -24,7 +24,10 @@ interpreted as a configuration parameter. For example, putting configuration parameter to bar. Any environment configurations that are not given a value will be given the value of true. Config values are case-insensitive, so NPM_CONFIG_FOO=bar will work the -same.

    +same. However, please note that inside npm-scripts +npm will set it's own environment variables and Node will prefer +those lowercase versions over any uppercase ones that you might set. +For details see this issue.

    npmrc Files

    The four relevant files are:

      @@ -236,8 +239,6 @@ e.g., npm outdated --depth 9999

    • Type: Boolean

    Install dev-dependencies along with packages.

    -

    Note that dev-dependencies are also installed if the npat flag is -set.

    dry-run

    • Default: false
      • @@ -431,9 +432,9 @@ version number, if not already set in package.json.

    • Type: Boolean

    Whether or not to output JSON data, rather than the normal output.

    -

    This feature is currently experimental, and the output data structures -for many commands is either not implemented in JSON yet, or subject to -change. Only the output from npm ls --json is currently valid.

    +

    This feature is currently experimental, and the output data structures for many +commands is either not implemented in JSON yet, or subject to change. Only the +output from npm ls --json and npm search --json are currently valid.

    key

    • Default: null
      • @@ -522,12 +523,6 @@ combination). Passed to the http Agent used to make th
    • Type: semver or false

    The node version to use when checking a package's engines map.

    -

    npat

    -
      -
    • Default: false
      • -
    • Type: Boolean
      • -
    -

    Run tests on installation.

    onload-script

    • Default: false
      • @@ -563,7 +558,7 @@ process is not aborted.

    • Type: Boolean

    Output parseable results from commands that write to -standard output.

    +standard output. For npm search, this will be tab-separated table format.

    prefix

    • Default: see npm-folders(5)
      • @@ -685,7 +680,7 @@ set to ^1.2.3 which allows minor upgrades for that package, but aft patch upgrades.

      scope

        -
      • Default: ""
        • +
      • Default: the scope of the current project, if any, or ""
      • Type: String

      Associate an operation with a scope for a scoped registry. Useful when logging @@ -693,27 +688,40 @@ in to a private registry for the first time: npm login --scope=@organization --registry=registry.organization.com, which will cause @organization to be mapped to the registry for future installation of packages specified according to the pattern @organization/package.

      -

      searchopts

      +

      scripts-prepend-node-path

      +
        +
      • Default: "warn-only"
        • +
      • Type: Boolean, "auto" or "warn-only"
        • +
      +

      If set to true, add the directory in which the current node executable +resides to the PATH environment variable when running scripts, +even if that means that npm will invoke a different node executable than +the one which it is running.

      +

      If set to false, never modify PATH with that.

      +

      If set to "warn-only", never modify PATH but print a warning if npm thinks +that you may want to run it with true, e.g. because the node executable +in the PATH is not the one npm was invoked with.

      +

      If set to auto, only add that directory to the PATH environment variable +if the node executable with which npm was invoked and the one that is found +first on the PATH are different.

      +

      searchexclude

      • Default: ""
      • Type: String
      -

      Space-separated options that are always passed to search.

      -

      searchexclude

      +

      Space-separated options that limit the results from search.

      +

      searchopts

      • Default: ""
      • Type: String
      -

      Space-separated options that limit the results from search.

      -

      searchsort

      +

      Space-separated options that are always passed to search.

      +

      searchstaleness

        -
      • Default: "name"
        • -
      • Type: String
        • -
      • Values: "name", "-name", "date", "-date", "description", -"-description", "keywords", "-keywords"
        • +
      • Default: 900 (15 minutes)
        • +
      • Type: Number
      -

      Indication of which field to sort search results by. Prefix with a - -character to indicate reverse sort.

      +

      The age of the cache, in seconds, before another registry request is made.

      shell

      • Default: SHELL environment variable, or "bash" on Posix, or "cmd" on @@ -864,5 +872,5 @@ exit successfully.

               - + diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index 2c64e124ce..3b04dffacf 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -194,5 +194,5 @@ from a fresh checkout.

               - + diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index 69a49b6e74..3db7ef27db 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -10,91 +10,113 @@

        npm-disputes

        Handling Module Name Disputes

        -

        SYNOPSIS

        +

        This document describes the steps that you should take to resolve module name +disputes with other npm publishers. It also describes special steps you should +take about names you think infringe your trademarks.

        +

        This document is a clarification of the acceptable behavior outlined in the +npm Code of Conduct, and nothing in +this document should be interpreted to contradict any aspect of the npm Code of +Conduct.

        +

        TL;DR

        1. Get the author email with npm owner ls <pkgname>
          2. -
        2. Email the author, CC support@npmjs.com
          3. +
        3. Email the author, CC support@npmjs.com
        4. After a few weeks, if there's no resolution, we'll sort it out.

        Don't squat on package names. Publish code or move out of the way.

        DESCRIPTION

        -

        There sometimes arise cases where a user publishes a module, and then -later, some other user wants to use that name. Here are some common -ways that happens (each of these is based on actual events.)

        +

        There sometimes arise cases where a user publishes a module, and then later, +some other user wants to use that name. Here are some common ways that happens +(each of these is based on actual events.)

          -
        1. Joe writes a JavaScript module foo, which is not node-specific. -Joe doesn't use node at all. Bob wants to use foo in node, so he -wraps it in an npm module. Some time later, Joe starts using node, -and wants to take over management of his program.
          2. -
        2. Bob writes an npm module foo, and publishes it. Perhaps much -later, Joe finds a bug in foo, and fixes it. He sends a pull -request to Bob, but Bob doesn't have the time to deal with it, -because he has a new job and a new baby and is focused on his new -erlang project, and kind of not involved with node any more. Joe -would like to publish a new foo, but can't, because the name is -taken.
          3. -
        3. Bob writes a 10-line flow-control library, and calls it foo, and -publishes it to the npm registry. Being a simple little thing, it -never really has to be updated. Joe works for Foo Inc, the makers -of the critically acclaimed and widely-marketed foo JavaScript -toolkit framework. They publish it to npm as foojs, but people are -routinely confused when npm install foo is some different thing.
          4. -
        4. Bob writes a parser for the widely-known foo file format, because -he needs it for work. Then, he gets a new job, and never updates the -prototype. Later on, Joe writes a much more complete foo parser, -but can't publish, because Bob's foo is in the way.
          5. -
        -

        The validity of Joe's claim in each situation can be debated. However, -Joe's appropriate course of action in each case is the same.

        -
          -
        1. npm owner ls foo. This will tell Joe the email address of the -owner (Bob).
          2. -
        2. Joe emails Bob, explaining the situation as respectfully as -possible, and what he would like to do with the module name. He -adds the npm support staff support@npmjs.com to the CC list of -the email. Mention in the email that Bob can run npm owner add -joe foo to add Joe as an owner of the foo package.
          3. -
        3. After a reasonable amount of time, if Bob has not responded, or if -Bob and Joe can't come to any sort of resolution, email support -support@npmjs.com and we'll sort it out. ("Reasonable" is -usually at least 4 weeks, but extra time is allowed around common -holidays.)
          4. +
        4. Alice writes a JavaScript module foo, which is not node-specific. Alice +doesn't use node at all. Yusuf wants to use foo in node, so he wraps it in +an npm module. Some time later, Alice starts using node, and wants to take +over management of her program.
          5. +
        5. Yusuf writes an npm module foo, and publishes it. Perhaps much later, Alice +finds a bug in foo, and fixes it. She sends a pull request to Yusuf, but +Yusuf doesn't have the time to deal with it, because he has a new job and a +new baby and is focused on his new Erlang project, and kind of not involved +with node any more. Alice would like to publish a new foo, but can't, +because the name is taken.
          6. +
        6. Yusuf writes a 10-line flow-control library, and calls it foo, and +publishes it to the npm registry. Being a simple little thing, it never +really has to be updated. Alice works for Foo Inc, the makers of the +critically acclaimed and widely-marketed foo JavaScript toolkit framework. +They publish it to npm as foojs, but people are routinely confused when +npm installfoo`` is some different thing.
          7. +

        7. Yusuf writes a parser for the widely-known foo file format, because he +needs it for work. Then, he gets a new job, and never updates the prototype. +Later on, Alice writes a much more complete foo parser, but can't publish, +because Yusuf's foo is in the way.

          +
          8. +

        8. npm owner ls foo. This will tell Alice the email address of the owner +(Yusuf).

          +
          9. +
        9. Alice emails Yusuf, explaining the situation as respectfully as possible, +and what she would like to do with the module name. She adds the npm support +staff support@npmjs.com to the CC list of the email. Mention in the email +that Yusuf can run npm owner add alice foo to add Alice as an owner of the +foo package.
          10. +
        10. After a reasonable amount of time, if Yusuf has not responded, or if Yusuf +and Alice can't come to any sort of resolution, email support +support@npmjs.com and we'll sort it out. ("Reasonable" is usually at least +4 weeks.)

        REASONING

        -

        In almost every case so far, the parties involved have been able to reach -an amicable resolution without any major intervention. Most people -really do want to be reasonable, and are probably not even aware that -they're in your way.

        -

        Module ecosystems are most vibrant and powerful when they are as -self-directed as possible. If an admin one day deletes something you -had worked on, then that is going to make most people quite upset, -regardless of the justification. When humans solve their problems by -talking to other humans with respect, everyone has the chance to end up -feeling good about the interaction.

        +

        In almost every case so far, the parties involved have been able to reach an +amicable resolution without any major intervention. Most people really do want +to be reasonable, and are probably not even aware that they're in your way.

        +

        Module ecosystems are most vibrant and powerful when they are as self-directed +as possible. If an admin one day deletes something you had worked on, then that +is going to make most people quite upset, regardless of the justification. When +humans solve their problems by talking to other humans with respect, everyone +has the chance to end up feeling good about the interaction.

        EXCEPTIONS

        -

        Some things are not allowed, and will be removed without discussion if -they are brought to the attention of the npm registry admins, including -but not limited to:

        +

        Some things are not allowed, and will be removed without discussion if they are +brought to the attention of the npm registry admins, including but not limited +to:

          -
        1. Malware (that is, a package designed to exploit or harm the machine on -which it is installed).
          2. -
        2. Violations of copyright or licenses (for example, cloning an -MIT-licensed program, and then removing or changing the copyright and -license statement).
          3. +
        3. Malware (that is, a package designed to exploit or harm the machine on which +it is installed).
          4. +
        4. Violations of copyright or licenses (for example, cloning an MIT-licensed +program, and then removing or changing the copyright and license statement).
        5. Illegal content.
          6. -
        6. "Squatting" on a package name that you plan to use, but aren't -actually using. Sorry, I don't care how great the name is, or how -perfect a fit it is for the thing that someday might happen. If -someone wants to use it today, and you're just taking up space with -an empty tarball, you're going to be evicted.
          7. -
        7. Putting empty packages in the registry. Packages must have SOME -functionality. It can be silly, but it can't be nothing. (See -also: squatting.)
          8. -
        8. Doing weird things with the registry, like using it as your own -personal application database or otherwise putting non-packagey -things into it.
          9. +
        9. "Squatting" on a package name that you plan to use, but aren't actually +using. Sorry, I don't care how great the name is, or how perfect a fit it is +for the thing that someday might happen. If someone wants to use it today, +and you're just taking up space with an empty tarball, you're going to be +evicted.
          10. +
        10. Putting empty packages in the registry. Packages must have SOME +functionality. It can be silly, but it can't be nothing. (See also: +squatting.)
          11. +
        11. Doing weird things with the registry, like using it as your own personal +application database or otherwise putting non-packagey things into it.
          12. +
        12. Other things forbidden by the npm +Code of Conduct such as hateful +language, pornographic content, or harassment.
        -

        If you see bad behavior like this, please report it right away.

        +

        If you see bad behavior like this, please report it to abuse@npmjs.com right +away. You are never expected to resolve abusive behavior on your own. We are +here to help.

        +

        TRADEMARKS

        +

        If you think another npm publisher is infringing your trademark, such as by +using a confusingly similar package name, email abuse@npmjs.com with a link to +the package or user account on https://npmjs.com. Attach a +copy of your trademark registration certificate.

        +

        If we see that the package's publisher is intentionally misleading others by +misusing your registered mark without permission, we will transfer the package +name to you. Otherwise, we will contact the package publisher and ask them to +clear up any confusion with changes to their package's README file or +metadata.

        +

        CHANGES

        +

        This is a living document and may be updated from time to time. Please refer to +the git history for this document +to view the changes.

        +

        LICENSE

        +

        Copyright (C) npm, Inc., All rights reserved

        +

        This document may be reused under a Creative Commons Attribution-ShareAlike +License.

        SEE ALSO

        • npm-registry(7)
          • @@ -112,5 +134,5 @@ things into it.        - + diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index 702e543023..4e590dabe7 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -98,8 +98,6 @@

          Start a package

          npm-stop(1)

          Stop a package

          -

          npm-tag(1)

          -

          Tag a published version

          npm-team(1)

          Manage organization teams and team memberships

          npm-test(1)

          @@ -162,5 +160,5 @@        - + diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index 7d5a7cba38..92aa4257e8 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -86,5 +86,5 @@        - + diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index b36cfa5bbe..a780c98a45 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -25,6 +25,26 @@ available at https://gith npm-scope(7)). If no scope is specified, the default registry is used, which is supplied by the registry config parameter. See npm-config(1), npmrc(5), and npm-config(7) for more on managing npm's configuration.

          +

          Does npm send any information about me back to the registry?

          +

          Yes.

          +

          When making requests of the registry npm adds two headers with information +about your environment:

          +
            +
          • Npm-Scope – If your project is scoped, this header will contain its +scope. In the future npm hopes to build registry features that use this +information to allow you to customize your experience for your +organization.
            • +
          • Npm-In-CI – Set to "true" if npm believes this install is running in a +continous integration environment, "false" otherwise. This is detected by +looking for the following environment variables: CI, TDDIUM, +JENKINS_URL, bamboo.buildKey. If you'd like to learn more you may find +the original PR +interesting. +This is used to gather better metrics on how npm is used by humans, versus +build farms.
            • +
          +

          The npm registry does not 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?

          Yes!

          The easiest way is to replicate the couch database, and use the same (or @@ -70,5 +90,5 @@ effectively implement the entire CouchDB API anyway.

                 - + diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index aed4efe7d1..7295c81fd8 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -94,5 +94,5 @@ that registry instead.

                 - + diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index 172a6cd748..c140ea2152 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -16,7 +16,13 @@ following scripts:

          • prepublish: Run BEFORE the package is published. (Also run on local npm -install without any arguments.)
            • +install without any arguments. See below.) +
          • prepare: +Run both BEFORE the package is published, and on local npm +install without any arguments. (See below.) This is run +AFTER prepublish, but BEFORE prepublishOnly.
            • +
          • prepublishOnly: +Run BEFORE the package is published. (See below.)
          • publish, postpublish: Run AFTER the package is published.
          • preinstall: @@ -50,7 +56,25 @@ run-script <stage>. Pre and post commands with ma names will be run for those as well (e.g. premyscript, myscript, postmyscript). Scripts from dependencies can be run with `npm explore

            -- npm run `.

            -

            COMMON USES

            +

            PREPUBLISH AND PREPARE

            +

            DEPRECATION NOTE

            +

            Since npm@1.1.71, the npm CLI has run the prepublish script for both npm +publish and npm install, because it's a convenient way to prepare a package +for use (some common use cases are described in the section below). It has +also turned out to be, in practice, very +confusing. As of npm@4.0.0, a new +event has been introduced, prepare, that preserves this existing behavior. A +new event, prepublishOnly has been added as a transitional strategy to +allow users to avoid the confusing behavior of existing npm versions and only +run on npm publish (for instance, running the tests one last time to ensure +they're in good shape).

            +

            IMPORTANT: As of npm@5, prepublish will only be run for npm +publish. This will make its behavior identical to prepublishOnly, so +npm@6 or later may drop support for the use of prepublishOnly, and then +maybe we can all forget this embarrassing thing ever happened.

            +

            See https://github.com/npm/npm/issues/10074 for a much lengthier +justification, with further reading, for this change.

            +

            USE CASES

            If you need to perform operations on your package before it is used, in a way that is not dependent on the operating system or architecture of the target system, use a prepublish script. This includes @@ -213,5 +237,5 @@ scripts is for compilation which must be done on the target architecture.

            •        - + diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 6b2f30a72b..63d0648844 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -57,5 +57,5 @@ modules. To track those down, you can do the following:

                   - + diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index 7e053f6228..2ae0288f99 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -325,5 +325,5 @@ range, use the satisfies(version, range) function.

                   - + -- cgit v1.2.1