Skip to content
This repository has been archived by the owner. It is now read-only.
Permalink
Browse files

Upgrade npm to 1.1.18

  • Loading branch information
isaacs committed Apr 27, 2012
1 parent db844b1 commit f6ff0d60b7a9046c687a1cc5a96e217a27751d15
Showing with 762 additions and 541 deletions.
  1. +1 −0 deps/npm/AUTHORS
  2. +20 −0 deps/npm/doc/cli/config.md
  3. +77 −48 deps/npm/doc/cli/install.md
  4. +1 −1 deps/npm/html/api/bin.html
  5. +1 −1 deps/npm/html/api/bugs.html
  6. +1 −1 deps/npm/html/api/commands.html
  7. +1 −1 deps/npm/html/api/config.html
  8. +1 −1 deps/npm/html/api/deprecate.html
  9. +1 −1 deps/npm/html/api/docs.html
  10. +1 −1 deps/npm/html/api/edit.html
  11. +1 −1 deps/npm/html/api/explore.html
  12. +1 −1 deps/npm/html/api/help-search.html
  13. +1 −1 deps/npm/html/api/init.html
  14. +1 −1 deps/npm/html/api/install.html
  15. +1 −1 deps/npm/html/api/link.html
  16. +1 −1 deps/npm/html/api/load.html
  17. +1 −1 deps/npm/html/api/ls.html
  18. +2 −2 deps/npm/html/api/npm.html
  19. +1 −1 deps/npm/html/api/outdated.html
  20. +1 −1 deps/npm/html/api/owner.html
  21. +1 −1 deps/npm/html/api/pack.html
  22. +1 −1 deps/npm/html/api/prefix.html
  23. +1 −1 deps/npm/html/api/prune.html
  24. +1 −1 deps/npm/html/api/publish.html
  25. +1 −1 deps/npm/html/api/rebuild.html
  26. +1 −1 deps/npm/html/api/restart.html
  27. +1 −1 deps/npm/html/api/root.html
  28. +1 −1 deps/npm/html/api/run-script.html
  29. +1 −1 deps/npm/html/api/search.html
  30. +1 −1 deps/npm/html/api/shrinkwrap.html
  31. +1 −1 deps/npm/html/api/start.html
  32. +1 −1 deps/npm/html/api/stop.html
  33. +1 −1 deps/npm/html/api/submodule.html
  34. +1 −1 deps/npm/html/api/tag.html
  35. +1 −1 deps/npm/html/api/test.html
  36. +1 −1 deps/npm/html/api/uninstall.html
  37. +1 −1 deps/npm/html/api/unpublish.html
  38. +1 −1 deps/npm/html/api/update.html
  39. +1 −1 deps/npm/html/api/version.html
  40. +1 −1 deps/npm/html/api/view.html
  41. +1 −1 deps/npm/html/api/whoami.html
  42. +1 −1 deps/npm/html/doc/README.html
  43. +1 −1 deps/npm/html/doc/adduser.html
  44. +1 −1 deps/npm/html/doc/bin.html
  45. +1 −1 deps/npm/html/doc/bugs.html
  46. +1 −1 deps/npm/html/doc/build.html
  47. +1 −1 deps/npm/html/doc/bundle.html
  48. +1 −1 deps/npm/html/doc/cache.html
  49. +1 −1 deps/npm/html/doc/changelog.html
  50. +1 −1 deps/npm/html/doc/coding-style.html
  51. +1 −1 deps/npm/html/doc/completion.html
  52. +18 −2 deps/npm/html/doc/config.html
  53. +1 −1 deps/npm/html/doc/deprecate.html
  54. +1 −1 deps/npm/html/doc/developers.html
  55. +1 −1 deps/npm/html/doc/disputes.html
  56. +1 −1 deps/npm/html/doc/docs.html
  57. +1 −1 deps/npm/html/doc/edit.html
  58. +1 −1 deps/npm/html/doc/explore.html
  59. +1 −1 deps/npm/html/doc/faq.html
  60. +1 −1 deps/npm/html/doc/folders.html
  61. +1 −1 deps/npm/html/doc/help-search.html
  62. +1 −1 deps/npm/html/doc/help.html
  63. +1 −1 deps/npm/html/doc/index.html
  64. +1 −1 deps/npm/html/doc/init.html
  65. +20 −23 deps/npm/html/doc/install.html
  66. +1 −1 deps/npm/html/doc/json.html
  67. +1 −1 deps/npm/html/doc/link.html
  68. +1 −1 deps/npm/html/doc/list.html
  69. +2 −2 deps/npm/html/doc/npm.html
  70. +1 −1 deps/npm/html/doc/outdated.html
  71. +1 −1 deps/npm/html/doc/owner.html
  72. +1 −1 deps/npm/html/doc/pack.html
  73. +1 −1 deps/npm/html/doc/prefix.html
  74. +1 −1 deps/npm/html/doc/prune.html
  75. +1 −1 deps/npm/html/doc/publish.html
  76. +1 −1 deps/npm/html/doc/rebuild.html
  77. +1 −1 deps/npm/html/doc/registry.html
  78. +1 −1 deps/npm/html/doc/removing-npm.html
  79. +1 −1 deps/npm/html/doc/restart.html
  80. +1 −1 deps/npm/html/doc/root.html
  81. +1 −1 deps/npm/html/doc/run-script.html
  82. +1 −1 deps/npm/html/doc/scripts.html
  83. +1 −1 deps/npm/html/doc/search.html
  84. +1 −1 deps/npm/html/doc/semver.html
  85. +1 −1 deps/npm/html/doc/shrinkwrap.html
  86. +1 −1 deps/npm/html/doc/star.html
  87. +1 −1 deps/npm/html/doc/start.html
  88. +1 −1 deps/npm/html/doc/stop.html
  89. +1 −1 deps/npm/html/doc/submodule.html
  90. +1 −1 deps/npm/html/doc/tag.html
  91. +1 −1 deps/npm/html/doc/test.html
  92. +1 −1 deps/npm/html/doc/uninstall.html
  93. +1 −1 deps/npm/html/doc/unpublish.html
  94. +1 −1 deps/npm/html/doc/update.html
  95. +1 −1 deps/npm/html/doc/version.html
  96. +1 −1 deps/npm/html/doc/view.html
  97. +1 −1 deps/npm/html/doc/whoami.html
  98. +12 −3 deps/npm/html/index.html
  99. +14 −6 deps/npm/lib/install.js
  100. +18 −1 deps/npm/lib/npm.js
  101. +6 −0 deps/npm/lib/utils/config-defs.js
  102. +3 −0 deps/npm/lib/utils/read-installed.js
  103. +38 −0 deps/npm/man/man1/config.1
  104. +58 −32 deps/npm/man/man1/install.1
  105. +1 −1 deps/npm/man/man1/npm.1
  106. +1 −1 deps/npm/man/man3/npm.3
  107. +14 −2 deps/npm/node_modules/fstream-npm/fstream-npm.js
  108. +2 −2 deps/npm/node_modules/fstream-npm/node_modules/fstream-ignore/package.json
  109. +5 −5 deps/npm/node_modules/fstream-npm/package.json
  110. +24 −0 deps/npm/node_modules/node-gyp/LICENSE
  111. +67 −35 deps/npm/node_modules/node-gyp/bin/node-gyp.js
  112. +1 −0 deps/npm/node_modules/node-gyp/legacy/common.gypi
  113. +67 −35 deps/npm/node_modules/node-gyp/lib/build.js
  114. +3 −24 deps/npm/node_modules/node-gyp/lib/clean.js
  115. +74 −45 deps/npm/node_modules/node-gyp/lib/configure.js
  116. +61 −43 deps/npm/node_modules/node-gyp/lib/install.js
  117. +3 −6 deps/npm/node_modules/node-gyp/lib/list.js
  118. +44 −4 deps/npm/node_modules/node-gyp/lib/node-gyp.js
  119. +2 −5 deps/npm/node_modules/node-gyp/lib/remove.js
  120. +0 −61 deps/npm/node_modules/node-gyp/lib/util/asyncEmit.js
  121. +0 −48 deps/npm/node_modules/node-gyp/lib/util/hook.js
  122. +2 −2 deps/npm/node_modules/node-gyp/node_modules/ansi/package.json
  123. +2 −2 deps/npm/node_modules/node-gyp/node_modules/glob/package.json
  124. +7 −7 deps/npm/node_modules/node-gyp/package.json
  125. +3 −4 deps/npm/package.json
@@ -63,3 +63,4 @@ Adam Blackburn <regality@gmail.com>
Kris Windham <kriswindham@gmail.com>
Jens Grunert <jens.grunert@gmail.com>
Joost-Wim Boekesteijn <joost-wim@boekesteijn.nl>
Dalmais Maxence <github@maxired.fr>
@@ -115,6 +115,8 @@ The following shorthands are parsed on the command-line:
* `-l`: `--long`
* `-desc`: `--description`
* `-S`: `--save`
* `-D`: `--save-dev`
* `-O`: `--save-optional`
* `-y`: `--yes`
* `-n`: `--yes false`
* `ll` and `la` commands: `ls --long`
@@ -584,6 +586,24 @@ Save installed packages to a package.json file as dependencies.

Only works if there is already a package.json file present.

### save-dev

* Default: false
* Type: Boolean

Save installed packages to a package.json file as devDependencies.

Only works if there is already a package.json file present.

### save-optional

* Default: false
* Type: Boolean

Save installed packages to a package.json file as optionalDependencies.

Only works if there is already a package.json file present.

### searchopts

* Default: ""
@@ -7,10 +7,11 @@ npm-install(1) -- Install a package
npm install <tarball file>
npm install <tarball url>
npm install <folder>
npm install <name>
npm install <name> [--save|--save-dev|--save-optional]
npm install <name>@<tag>
npm install <name>@<version>
npm install <name>@<version range>
npm install <name>@<version range>

## DESCRIPTION

@@ -35,88 +36,116 @@ after packing it up into a tarball (b).


* `npm install` (in package directory, no arguments):
Install the dependencies in the local node_modules folder.

In global mode (ie, with `-g` or `--global` appended to the command),
it installs the current package context (ie, the current working
directory) as a global package.
Install the dependencies in the local node_modules folder.

In global mode (ie, with `-g` or `--global` appended to the command),
it installs the current package context (ie, the current working
directory) as a global package.


* `npm install <folder>`:
Install a package that is sitting in a folder on the filesystem.

Install a package that is sitting in a folder on the filesystem.

* `npm install <tarball file>`:
Install a package that is sitting on the filesystem. Note: if you just want
to link a dev directory into your npm root, you can do this more easily by
using `npm link`.

Example:
Install a package that is sitting on the filesystem. Note: if you just want
to link a dev directory into your npm root, you can do this more easily by
using `npm link`.

Example:

npm install ./package.tgz
npm install ./package.tgz

* `npm install <tarball url>`:
Fetch the tarball url, and then install it. In order to distinguish between
this and other options, the argument must start with "http://" or "https://"

Example:
Fetch the tarball url, and then install it. In order to distinguish between
this and other options, the argument must start with "http://" or "https://"

Example:

npm install https://github.com/indexzero/forever/tarball/v0.5.6

* `npm install <name> [--save|--save-dev|--save-optional]`:

Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See
`npm-config(1)`.)

npm install https://github.com/indexzero/forever/tarball/v0.5.6
In most cases, this will install the latest version
of the module published on npm.

* `npm install <name>`:
Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See
`npm-config(1)`)
Example:

Example:
npm install sax

npm install sax
`npm install` takes 3 exclusive, optional flags which save or update
the package version in your main package.json:

**Note**: If there is a file or folder named `<name>` in the current
working directory, then it will try to install that, and only try to
fetch the package by name if it is not valid.
* `--save`: Package will appear in your `dependencies`.

* `--save-dev`: Package will appear in your `devDependencies`.

* `--save-optional`: Package will appear in your `optionalDependencies`.

Examples:

npm install sax --save
npm install node-tap --save-dev
npm install dtrace-provider --save-optional


**Note**: If there is a file or folder named `<name>` in the current
working directory, then it will try to install that, and only try to
fetch the package by name if it is not valid.

* `npm install <name>@<tag>`:
Install the version of the package that is referenced by the specified tag.
If the tag does not exist in the registry data for that package, then this
will fail.

Example:
Install the version of the package that is referenced by the specified tag.
If the tag does not exist in the registry data for that package, then this
will fail.

Example:

npm install sax@latest
npm install sax@latest

* `npm install <name>@<version>`:
Install the specified version of the package. This will fail if the version
has not been published to the registry.

Example:
Install the specified version of the package. This will fail if the version
has not been published to the registry.

npm install sax@0.1.1
Example:

npm install sax@0.1.1

* `npm install <name>@<version range>`:
Install a version of the package matching the specified version range. This
will follow the same rules for resolving dependencies described in `npm-json(1)`.

Note that most version ranges must be put in quotes so that your shell will
treat it as a single argument.
Install a version of the package matching the specified version range. This
will follow the same rules for resolving dependencies described in `npm-json(1)`.

Note that most version ranges must be put in quotes so that your shell will
treat it as a single argument.

Example:
Example:

npm install sax@">=0.1.0 <0.2.0"
npm install sax@">=0.1.0 <0.2.0"

* `npm install <git remote url>`:

Install a package by cloning a git remote url. The format of the git
url is:
Install a package by cloning a git remote url. The format of the git
url is:

<protocol>://[<user>@]<hostname><separator><path>[#<commit-ish>]
<protocol>://[<user>@]<hostname><separator><path>[#<commit-ish>]

`<protocol>` is one of `git`, `git+ssh`, `git+http`, or
`git+https`. If no `<commit-ish>` is specified, then `master` is
used.
`<protocol>` is one of `git`, `git+ssh`, `git+http`, or
`git+https`. If no `<commit-ish>` is specified, then `master` is
used.

Examples:
Examples:

git+ssh://git@github.com:isaacs/npm.git#v1.0.27
git+https://isaacs@github.com/isaacs/npm.git
git://github.com/isaacs/npm.git#v1.0.27
git+ssh://git@github.com:isaacs/npm.git#v1.0.27
git+https://isaacs@github.com/isaacs/npm.git
git://github.com/isaacs/npm.git#v1.0.27

You may combine multiple arguments, and even multiple types of arguments.
For example:
@@ -19,7 +19,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>This function should not be used programmatically. Instead, just refer
to the <code>npm.bin</code> member.</p>
</div>
<p id="footer">bin &mdash; npm@1.1.16</p>
<p id="footer">bin &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -25,7 +25,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>This command will launch a browser, so this command may not be the most
friendly for programmatic use.</p>
</div>
<p id="footer">bugs &mdash; npm@1.1.16</p>
<p id="footer">bugs &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -28,7 +28,7 @@ <h2 id="SEE-ALSO">SEE ALSO</h2>

<ul><li><a href="../doc/index.html">index(1)</a></li></ul>
</div>
<p id="footer">commands &mdash; npm@1.1.16</p>
<p id="footer">commands &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -33,7 +33,7 @@ <h2 id="SEE-ALSO">SEE ALSO</h2>

<ul><li><a href="../api/npm.html">npm(3)</a></li></ul>
</div>
<p id="footer">config &mdash; npm@1.1.16</p>
<p id="footer">config &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -30,7 +30,7 @@ <h2 id="SEE-ALSO">SEE ALSO</h2>

<ul><li><a href="../api/publish.html">publish(3)</a></li><li><a href="../api/unpublish.html">unpublish(3)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">deprecate &mdash; npm@1.1.16</p>
<p id="footer">deprecate &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -25,7 +25,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>This command will launch a browser, so this command may not be the most
friendly for programmatic use.</p>
</div>
<p id="footer">docs &mdash; npm@1.1.16</p>
<p id="footer">docs &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -30,7 +30,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>Since this command opens an editor in a new process, be careful about where
and how this is used.</p>
</div>
<p id="footer">edit &mdash; npm@1.1.16</p>
<p id="footer">edit &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -24,7 +24,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>

<p>The first element in the 'args' parameter must be a package name. After that is the optional command, which can be any number of strings. All of the strings will be combined into one, space-delimited command.</p>
</div>
<p id="footer">explore &mdash; npm@1.1.16</p>
<p id="footer">explore &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -32,7 +32,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>

<p>The silent parameter is not neccessary not used, but it may in the future.</p>
</div>
<p id="footer">help-search &mdash; npm@1.1.16</p>
<p id="footer">help-search &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -35,7 +35,7 @@ <h2 id="SEE-ALSO">SEE ALSO</h2>

<p><a href="../doc/json.html">json(1)</a></p>
</div>
<p id="footer">init &mdash; npm@1.1.16</p>
<p id="footer">init &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -25,7 +25,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>Finally, 'callback' is a function that will be called when all packages have been
installed or when an error has been encountered.</p>
</div>
<p id="footer">install &mdash; npm@1.1.16</p>
<p id="footer">install &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -39,7 +39,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>Now, any changes to the redis package will be reflected in
the package in the current working directory</p>
</div>
<p id="footer">link &mdash; npm@1.1.16</p>
<p id="footer">link &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -32,7 +32,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>

<p>For a list of all the available command-line configs, see <code>npm help config</code></p>
</div>
<p id="footer">load &mdash; npm@1.1.16</p>
<p id="footer">load &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -59,7 +59,7 @@ <h3 id="global">global</h3>
This means that if a submodule a same dependency as a parent module, then the
dependency will only be output once.</p>
</div>
<p id="footer">ls &mdash; npm@1.1.16</p>
<p id="footer">ls &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -24,7 +24,7 @@ <h2 id="SYNOPSIS">SYNOPSIS</h2>

<h2 id="VERSION">VERSION</h2>

<p>1.1.16</p>
<p>1.1.18</p>

<h2 id="DESCRIPTION">DESCRIPTION</h2>

@@ -91,7 +91,7 @@ <h2 id="ABBREVS">ABBREVS</h2>

<pre><code>var cmd = npm.deref("unp") // cmd === "unpublish"</code></pre>
</div>
<p id="footer">npm &mdash; npm@1.1.16</p>
<p id="footer">npm &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -19,7 +19,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>

<p>If the 'packages' parameter is left out, npm will check all packages.</p>
</div>
<p id="footer">outdated &mdash; npm@1.1.16</p>
<p id="footer">outdated &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -34,7 +34,7 @@ <h2 id="SEE-ALSO">SEE ALSO</h2>

<ul><li><a href="../api/publish.html">publish(3)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">owner &mdash; npm@1.1.16</p>
<p id="footer">owner &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -25,7 +25,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>

<p>If no arguments are supplied, then npm packs the current package folder.</p>
</div>
<p id="footer">pack &mdash; npm@1.1.16</p>
<p id="footer">pack &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
@@ -21,7 +21,7 @@ <h2 id="DESCRIPTION">DESCRIPTION</h2>

<p>This function is not useful programmatically</p>
</div>
<p id="footer">prefix &mdash; npm@1.1.16</p>
<p id="footer">prefix &mdash; npm@1.1.18</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

0 comments on commit f6ff0d6

Please sign in to comment.
You can’t perform that action at this time.