Browse Source

npm: Upgrade to 1.1.37

v0.8.7-release
isaacs 13 years ago
parent
commit
ae5a209b11
  1. 22
      deps/npm/.npmignore
  2. 5
      deps/npm/AUTHORS
  3. 5
      deps/npm/LICENSE
  4. 6
      deps/npm/README.md
  5. 13
      deps/npm/bin/npm
  6. 12
      deps/npm/bin/npm-cli.js
  7. 2
      deps/npm/bin/read-package-json.js
  8. 21
      deps/npm/doc/cli/coding-style.md
  9. 148
      deps/npm/doc/cli/config.md
  10. 1
      deps/npm/doc/cli/init.md
  11. 2
      deps/npm/doc/cli/install.md
  12. 19
      deps/npm/doc/cli/json.md
  13. 20
      deps/npm/doc/cli/list.md
  14. 2
      deps/npm/html/api/bin.html
  15. 2
      deps/npm/html/api/bugs.html
  16. 2
      deps/npm/html/api/commands.html
  17. 2
      deps/npm/html/api/config.html
  18. 2
      deps/npm/html/api/deprecate.html
  19. 2
      deps/npm/html/api/docs.html
  20. 2
      deps/npm/html/api/edit.html
  21. 2
      deps/npm/html/api/explore.html
  22. 2
      deps/npm/html/api/help-search.html
  23. 2
      deps/npm/html/api/init.html
  24. 2
      deps/npm/html/api/install.html
  25. 2
      deps/npm/html/api/link.html
  26. 2
      deps/npm/html/api/load.html
  27. 2
      deps/npm/html/api/ls.html
  28. 4
      deps/npm/html/api/npm.html
  29. 2
      deps/npm/html/api/outdated.html
  30. 2
      deps/npm/html/api/owner.html
  31. 2
      deps/npm/html/api/pack.html
  32. 2
      deps/npm/html/api/prefix.html
  33. 2
      deps/npm/html/api/prune.html
  34. 2
      deps/npm/html/api/publish.html
  35. 2
      deps/npm/html/api/rebuild.html
  36. 2
      deps/npm/html/api/restart.html
  37. 2
      deps/npm/html/api/root.html
  38. 2
      deps/npm/html/api/run-script.html
  39. 2
      deps/npm/html/api/search.html
  40. 2
      deps/npm/html/api/shrinkwrap.html
  41. 2
      deps/npm/html/api/start.html
  42. 2
      deps/npm/html/api/stop.html
  43. 2
      deps/npm/html/api/submodule.html
  44. 2
      deps/npm/html/api/tag.html
  45. 2
      deps/npm/html/api/test.html
  46. 2
      deps/npm/html/api/uninstall.html
  47. 2
      deps/npm/html/api/unpublish.html
  48. 2
      deps/npm/html/api/update.html
  49. 2
      deps/npm/html/api/version.html
  50. 2
      deps/npm/html/api/view.html
  51. 2
      deps/npm/html/api/whoami.html
  52. 10
      deps/npm/html/doc/README.html
  53. 2
      deps/npm/html/doc/adduser.html
  54. 2
      deps/npm/html/doc/bin.html
  55. 2
      deps/npm/html/doc/bugs.html
  56. 2
      deps/npm/html/doc/build.html
  57. 2
      deps/npm/html/doc/bundle.html
  58. 2
      deps/npm/html/doc/cache.html
  59. 2
      deps/npm/html/doc/changelog.html
  60. 23
      deps/npm/html/doc/coding-style.html
  61. 2
      deps/npm/html/doc/completion.html
  62. 135
      deps/npm/html/doc/config.html
  63. 2
      deps/npm/html/doc/deprecate.html
  64. 2
      deps/npm/html/doc/developers.html
  65. 2
      deps/npm/html/doc/disputes.html
  66. 2
      deps/npm/html/doc/docs.html
  67. 2
      deps/npm/html/doc/edit.html
  68. 2
      deps/npm/html/doc/explore.html
  69. 2
      deps/npm/html/doc/faq.html
  70. 2
      deps/npm/html/doc/folders.html
  71. 2
      deps/npm/html/doc/help-search.html
  72. 2
      deps/npm/html/doc/help.html
  73. 2
      deps/npm/html/doc/index.html
  74. 4
      deps/npm/html/doc/init.html
  75. 4
      deps/npm/html/doc/install.html
  76. 21
      deps/npm/html/doc/json.html
  77. 2
      deps/npm/html/doc/link.html
  78. 22
      deps/npm/html/doc/list.html
  79. 4
      deps/npm/html/doc/npm.html
  80. 2
      deps/npm/html/doc/outdated.html
  81. 2
      deps/npm/html/doc/owner.html
  82. 2
      deps/npm/html/doc/pack.html
  83. 2
      deps/npm/html/doc/prefix.html
  84. 2
      deps/npm/html/doc/prune.html
  85. 2
      deps/npm/html/doc/publish.html
  86. 2
      deps/npm/html/doc/rebuild.html
  87. 2
      deps/npm/html/doc/registry.html
  88. 2
      deps/npm/html/doc/removing-npm.html
  89. 2
      deps/npm/html/doc/restart.html
  90. 2
      deps/npm/html/doc/root.html
  91. 2
      deps/npm/html/doc/run-script.html
  92. 2
      deps/npm/html/doc/scripts.html
  93. 2
      deps/npm/html/doc/search.html
  94. 2
      deps/npm/html/doc/semver.html
  95. 2
      deps/npm/html/doc/shrinkwrap.html
  96. 2
      deps/npm/html/doc/star.html
  97. 2
      deps/npm/html/doc/start.html
  98. 2
      deps/npm/html/doc/stop.html
  99. 2
      deps/npm/html/doc/submodule.html
  100. 2
      deps/npm/html/doc/tag.html

22
deps/npm/.npmignore

@ -1,16 +1,16 @@
*.swp
test/bin
test/output.log
test/packages/*/node_modules
test/packages/npm-test-depends-on-spark/which-spark.log
test/packages/test-package/random-data.txt
test/root
node_modules/ronn
node_modules/.bin
npm-debug.log
./npmrc
.gitignore
release/
/test/bin
/test/output.log
/test/packages/*/node_modules
/test/packages/npm-test-depends-on-spark/which-spark.log
/test/packages/test-package/random-data.txt
/test/root
/node_modules/ronn
/node_modules/tap
/node_modules/.bin
/npmrc
/release/
# don't need these in the npm package.
html/*.png

5
deps/npm/AUTHORS

@ -66,3 +66,8 @@ Joost-Wim Boekesteijn <joost-wim@boekesteijn.nl>
Dalmais Maxence <github@maxired.fr>
Marcus Ekwall <marcus.ekwall@gmail.com>
Aaron Stacy <aaron.r.stacy@gmail.com>
Phillip Howell <phowell@cothm.org>
Domenic Denicola <domenic@domenicdenicola.com>
James Halliday <mail@substack.net>
Jeremy Cantrell <jmcantrell@gmail.com>
Ribettes <patlogan29@gmail.com>

5
deps/npm/LICENSE

@ -49,6 +49,11 @@ and are not covered by this license.
"npm Logo" created by Mathias Pettersson and Brian Hammond,
used with permission.
"Gubblebum Blocky" font
Copyright (c) 2007 by Tjarda Koster, http://jelloween.deviantart.com
included for use in the npm website and documentation,
used with permission.
This program uses "node-uuid", Copyright (c) 2010 Robert Kieffer,
according to the terms of the MIT license.

6
deps/npm/README.md

@ -89,21 +89,15 @@ To install the latest **unstable** development version from git:
git clone https://github.com/isaacs/npm.git
cd npm
git submodule update --init --recursive
sudo make install # (or: `node cli.js install -gf`)
If you're sitting in the code folder reading this document in your
terminal, then you've already got the code. Just do:
git submodule update --init --recursive
sudo make install
and npm will install itself.
Note that github tarballs **do not contain submodules**, so
those won't work. You'll have to also fetch the appropriate submodules
listed in the .gitmodules file.
## Permissions when Using npm to Install Other Stuff
**tl;dr**

13
deps/npm/bin/npm

@ -1,6 +1,13 @@
#!/bin/sh
if [ -x "`dirname "$0"`/node.exe" ]; then
"`dirname "$0"`/node.exe" "`dirname "$0"`/node_modules/npm/bin/npm-cli.js" "$@"
basedir=`dirname "$0"`
case `uname` in
*CYGWIN*) basedir=`cygpath -w "$basedir"`;;
esac
if [ -x "$basedir/node.exe" ]; then
"$basedir/node.exe" "$basedir/node_modules/npm/bin/npm-cli.js" "$@"
else
node "`dirname "$0"`/node_modules/npm/bin/npm-cli.js" "$@"
node "$basedir/node_modules/npm/bin/npm-cli.js" "$@"
fi

12
deps/npm/bin/npm-cli.js

@ -15,9 +15,9 @@ if (typeof WScript !== "undefined") {
process.title = "npm"
var log = require("../lib/utils/log.js")
log.waitForConfig()
log.info("ok", "it worked if it ends with")
var log = require("npmlog")
log.pause() // will be unpaused when config is loaded.
log.info("it worked if it ends with", "ok")
var fs = require("graceful-fs")
, path = require("path")
@ -36,7 +36,7 @@ if (path.basename(process.argv[1]).slice(-1) === "g") {
process.argv.splice(1, 1, "npm", "-g")
}
log.verbose(process.argv, "cli")
log.verbose("cli", process.argv)
var conf = nopt(types, shorthands)
npm.argv = conf.argv.remain
@ -56,8 +56,8 @@ if (conf.versions) {
return
}
log.info("npm@"+npm.version, "using")
log.info("node@"+process.version, "using")
log.info("using", "npm@%s", npm.version)
log.info("using", "node@%s", process.version)
// make sure that this version of node works with this version of npm.
var semver = require("semver")

2
deps/npm/bin/read-package-json.js

@ -6,7 +6,7 @@ if (argv.length < 3) {
var fs = require("fs")
, file = argv[2]
, readJson = require("../lib/utils/read-json")
, readJson = require("read-package-json")
readJson(file, function (er, data) {
if (er) throw er

21
deps/npm/doc/cli/coding-style.md

@ -129,29 +129,18 @@ Just send the error message back as the first argument to the callback.
Always create a new Error object with your message. Don't just return a
string message to the callback. Stack traces are handy.
Use the `require("./utils/log").er` function. It takes a callback and an
error message, and returns an object that will report the message in the
event of a failure. It's quite handy.
function myThing (args, cb) {
getData(args, function (er, data) {
if (er) return log.er(cb, "Couldn't get data")(er)
doSomethingElse(data, cb)
})
}
function justHasToWork (cb) {
doSomething(log.er(cb, "the doSomething failed."))
}
## Logging
Logging is done using the [npmlog](https://github.com/isaacs/npmlog)
utility.
Please clean up logs when they are no longer helpful. In particular,
logging the same object over and over again is not helpful. Logs should
report what's happening so that it's easier to track down where a fault
occurs.
Use appropriate log levels. The default log() function logs at the
"info" level. See `npm-config(1)` and search for "loglevel".
Use appropriate log levels. See `npm-config(1)` and search for
"loglevel".
## Case, naming, etc.

148
deps/npm/doc/cli/config.md

@ -117,6 +117,7 @@ The following shorthands are parsed on the command-line:
* `-S`: `--save`
* `-D`: `--save-dev`
* `-O`: `--save-optional`
* `-B`: `--save-bundle`
* `-y`: `--yes`
* `-n`: `--yes false`
* `ll` and `la` commands: `ls --long`
@ -167,32 +168,6 @@ then the user could change the behavior by doing:
Force npm to always require authentication when accessing the registry,
even for `GET` requests.
### bin-publish
* Default: false
* Type: Boolean
If set to true, then binary packages will be created on publish.
This is the way to opt into the "bindist" behavior described below.
### bindist
* Default: Unstable node versions, `null`, otherwise
`"<node version>-<platform>-<os release>"`
* Type: String or `null`
Experimental: on stable versions of node, binary distributions will be
created with this tag. If a user then installs that package, and their
`bindist` tag is found in the list of binary distributions, they will
get that prebuilt version.
Pre-build node packages have their preinstall, install, and postinstall
scripts stripped (since they are run prior to publishing), and do not
have their `build` directories automatically ignored.
It's yet to be seen if this is a good idea.
### browser
* Default: OS X: `"open"`, others: `"google-chrome"`
@ -220,6 +195,27 @@ See also the `strict-ssl` config.
The location of npm's cache directory. See `npm-cache(1)`
### cache-lock-stale
* Default: 60000 (1 minute)
* Type: Number
The number of ms before cache folder lockfiles are considered stale.
### cache-lock-retries
* Default: 10
* Type: Number
Number of times to retry to acquire a lock on cache folder lockfiles.
### cache-lock-wait
* Default: 10000 (10 seconds)
* Type: Number
Number of ms to wait for cache lock files to expire.
### cache-max
* Default: Infinity
@ -291,6 +287,15 @@ set.
The command to run for `npm edit` or `npm config edit`.
### engine-strict
* Default: false
* Type: Boolean
If set to true, then npm will stubbornly refuse to install (or even
consider installing) any package that claims to not be compatible with
the current Node.js version.
### force
* Default: false
@ -303,6 +308,38 @@ Makes various commands more forceful.
* skips cache when requesting from the registry.
* prevents checks against clobbering non-npm files.
### fetch-retries
* Default: 2
* Type: Number
The "retries" config for the `retry` module to use when fetching
packages from the registry.
### fetch-retry-factor
* Default: 10
* Type: Number
The "factor" config for the `retry` module to use when fetching
packages.
### fetch-retry-mintimeout
* Default: 10000 (10 seconds)
* Type: Number
The "minTimeout" config for the `retry` module to use when fetching
packages.
### fetch-retry-maxtimeout
* Default: 60000 (1 minute)
* Type: Number
The "maxTimeout" config for the `retry` module to use when fetching
packages.
### git
* Default: `"git"`
@ -375,6 +412,16 @@ Sets a User-Agent to the request header
A white-space separated list of glob patterns of files to always exclude
from packages when building tarballs.
### init-module
* Default: ~/.npm-init.js
* Type: path
A module that will be loaded by the `npm init` command. See the
documentation for the
[init-package-json](https://github.com/isaacs/init-package-json) module
for more information, or npm-init(1).
### init.version
* Default: "0.0.0"
@ -430,13 +477,6 @@ if one of the two conditions are met:
* the globally installed version is identical to the version that is
being installed locally.
### logfd
* Default: stderr file descriptor
* Type: Number or Stream
The location to write log output.
### loglevel
* Default: "http"
@ -449,13 +489,17 @@ What level of logs to report. On failure, *all* logs are written to
Any logs of a higher level than the setting are shown.
The default is "http", which shows http, warn, and error output.
### logprefix
### logstream
* Default: true on Posix, false on Windows
* Type: Boolean
* Default: process.stderr
* Type: Stream
This is the stream that is passed to the
[npmlog](https://github.com/isaacs/npmlog) module at run time.
Whether or not to prefix log messages with "npm" and the log level. See
also "color" and "loglevel".
It cannot be set from the command line, but if you are using npm
programmatically, you may wish to send logs to somewhere other than
stderr.
### long
@ -503,13 +547,6 @@ The url to report npat test results.
A node module to `require()` when npm loads. Useful for programmatic
usage.
### outfd
* Default: standard output file descriptor
* Type: Number or Stream
Where to write "normal" output. This has no effect on log output.
### parseable
* Default: false
@ -584,8 +621,23 @@ Remove failed installs.
Save installed packages to a package.json file as dependencies.
When used with the `npm rm` command, it removes it from the dependencies
hash.
Only works if there is already a package.json file present.
### save-bundle
* Default: false
* Type: Boolean
If a package would be saved at install time by the use of `--save`,
`--save-dev`, or `--save-optional`, then also put it in the
`bundleDependencies` list.
When used with the `npm rm` command, it removes it from the
bundledDependencies list.
### save-dev
* Default: false
@ -593,6 +645,9 @@ Only works if there is already a package.json file present.
Save installed packages to a package.json file as devDependencies.
When used with the `npm rm` command, it removes it from the devDependencies
hash.
Only works if there is already a package.json file present.
### save-optional
@ -602,6 +657,9 @@ Only works if there is already a package.json file present.
Save installed packages to a package.json file as optionalDependencies.
When used with the `npm rm` command, it removes it from the devDependencies
hash.
Only works if there is already a package.json file present.
### searchopts

1
deps/npm/doc/cli/init.md

@ -20,5 +20,6 @@ without a really good reason to do so.
## SEE ALSO
* <https://github.com/isaacs/init-package-json>
* npm-json(1)
* npm-version(1)

2
deps/npm/doc/cli/install.md

@ -160,7 +160,7 @@ local copy exists on disk.
npm install sax --force
The `--global` argument will cause npm to install the package globally
rather than locally. See `npm-global(1)`.
rather than locally. See `npm-folders(1)`.
The `--link` argument will cause npm to link global installs into the
local space in some cases.

19
deps/npm/doc/cli/json.md

@ -453,8 +453,7 @@ Entries in `optionalDependencies` will override entries of the same name in
## engines
You can specify the version of
node that your stuff works on:
You can specify the version of node that your stuff works on:
{ "engines" : { "node" : ">=0.1.27 <0.1.30" } }
@ -470,6 +469,22 @@ are capable of properly installing your program. For example:
{ "engines" : { "npm" : "~1.0.20" } }
Note that, unless the user has set the `engine-strict` config flag, this
field is advisory only.
## engineStrict
If you are sure that your module will *definitely not* run properly on
versions of Node/npm other than those specified in the `engines` hash,
then you can set `"engineStrict": true` in your package.json file.
This will override the user's `engine-strict` config setting.
Please do not do this unless you are really very very sure. If your
engines hash is something overly restrictive, you can quite easily and
inadvertently lock yourself into obscurity and prevent your users from
updating to new versions of Node. Consider this choice carefully. If
people abuse it, it will be removed in a future version of npm.
## os
You can specify which operating systems your

20
deps/npm/doc/cli/list.md

@ -3,20 +3,26 @@ npm-ls(1) -- List installed packages
## SYNOPSIS
npm list
npm ls
npm la
npm ll
npm list [<pkg> ...]
npm ls [<pkg> ...]
npm la [<pkg> ...]
npm ll [<pkg> ...]
## DESCRIPTION
This command will print to stdout all the versions of packages that are
installed, as well as their dependencies, in a tree-structure.
It does not take positional arguments, though you may set config flags
like with any other command, such as `-g` to list global packages.
Positional arguments are `name@version-range` identifiers, which will
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:
It will print out extraneous, missing, and invalid packages.
npm@@VERSION@ /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
It will show print out extraneous, missing, and invalid packages.
When run as `ll` or `la`, it shows extended information by default.

2
deps/npm/html/api/bin.html

@ -19,7 +19,7 @@
<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.24</p>
<p id="footer">bin &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/bugs.html

@ -25,7 +25,7 @@ optional version number.</p>
<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.24</p>
<p id="footer">bugs &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/commands.html

@ -28,7 +28,7 @@ usage, or <code>man 3 npm-&lt;command&gt;</code> for programmatic usage.</p>
<ul><li><a href="../doc/index.html">index(1)</a></li></ul>
</div>
<p id="footer">commands &mdash; npm@1.1.24</p>
<p id="footer">commands &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/config.html

@ -33,7 +33,7 @@ functions instead.</p>
<ul><li><a href="../api/npm.html">npm(3)</a></li></ul>
</div>
<p id="footer">config &mdash; npm@1.1.24</p>
<p id="footer">config &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/deprecate.html

@ -30,7 +30,7 @@ install the package.</p></li></ul>
<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.24</p>
<p id="footer">deprecate &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/docs.html

@ -25,7 +25,7 @@ optional version number.</p>
<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.24</p>
<p id="footer">docs &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/edit.html

@ -30,7 +30,7 @@ to open. The package can optionally have a version number attached.</p>
<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.24</p>
<p id="footer">edit &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/explore.html

@ -24,7 +24,7 @@ sure to use <code>npm rebuild &lt;pkg&gt;</code> if you make any changes.</p>
<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.24</p>
<p id="footer">explore &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/help-search.html

@ -32,7 +32,7 @@ Name of the file that matched</li></ul>
<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.24</p>
<p id="footer">help-search &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/init.html

@ -35,7 +35,7 @@ then go ahead and use this programmatically.</p>
<p><a href="../doc/json.html">json(1)</a></p>
</div>
<p id="footer">init &mdash; npm@1.1.24</p>
<p id="footer">init &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/install.html

@ -25,7 +25,7 @@ the name of a package to be installed.</p>
<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.24</p>
<p id="footer">install &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/link.html

@ -39,7 +39,7 @@ npm.commands.link('redis', cb) # link-install the package</code></pre>
<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.24</p>
<p id="footer">link &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/load.html

@ -32,7 +32,7 @@ config object.</p>
<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.24</p>
<p id="footer">load &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/ls.html

@ -59,7 +59,7 @@ project.</p>
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.24</p>
<p id="footer">ls &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/api/npm.html

@ -24,7 +24,7 @@ npm.load(configObject, function (er, npm) {
<h2 id="VERSION">VERSION</h2>
<p>1.1.24</p>
<p>1.1.37</p>
<h2 id="DESCRIPTION">DESCRIPTION</h2>
@ -91,7 +91,7 @@ method names. Use the <code>npm.deref</code> method to find the real name.</p>
<pre><code>var cmd = npm.deref("unp") // cmd === "unpublish"</code></pre>
</div>
<p id="footer">npm &mdash; npm@1.1.24</p>
<p id="footer">npm &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/outdated.html

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

2
deps/npm/html/api/owner.html

@ -34,7 +34,7 @@ that is not implemented at this time.</p>
<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.24</p>
<p id="footer">owner &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/pack.html

@ -25,7 +25,7 @@ overwritten the second time.</p>
<p>If no arguments are supplied, then npm packs the current package folder.</p>
</div>
<p id="footer">pack &mdash; npm@1.1.24</p>
<p id="footer">pack &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/prefix.html

@ -21,7 +21,7 @@
<p>This function is not useful programmatically</p>
</div>
<p id="footer">prefix &mdash; npm@1.1.24</p>
<p id="footer">prefix &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/prune.html

@ -23,7 +23,7 @@
<p>Extraneous packages are packages that are not listed on the parent
package's dependencies list.</p>
</div>
<p id="footer">prune &mdash; npm@1.1.24</p>
<p id="footer">prune &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/publish.html

@ -32,7 +32,7 @@ the registry. Overwrites when the "force" environment variable is set.</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../api/owner.html">owner(3)</a></li></ul>
</div>
<p id="footer">publish &mdash; npm@1.1.24</p>
<p id="footer">publish &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/rebuild.html

@ -22,7 +22,7 @@ the new binary. If no 'packages' parameter is specify, every package will be reb
<p>See <code>npm help build</code></p>
</div>
<p id="footer">rebuild &mdash; npm@1.1.24</p>
<p id="footer">rebuild &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/restart.html

@ -27,7 +27,7 @@ in the <code>packages</code> parameter.</p>
<ul><li><a href="../api/start.html">start(3)</a></li><li><a href="../api/stop.html">stop(3)</a></li></ul>
</div>
<p id="footer">restart &mdash; npm@1.1.24</p>
<p id="footer">restart &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/root.html

@ -21,7 +21,7 @@
<p>This function is not useful programmatically.</p>
</div>
<p id="footer">root &mdash; npm@1.1.24</p>
<p id="footer">root &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/run-script.html

@ -29,7 +29,7 @@ assumed to be the command to run. All other elements are ignored.</p>
<ul><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../api/test.html">test(3)</a></li><li><a href="../api/start.html">start(3)</a></li><li><a href="../api/restart.html">restart(3)</a></li><li><a href="../api/stop.html">stop(3)</a></li></ul>
</div>
<p id="footer">run-script &mdash; npm@1.1.24</p>
<p id="footer">run-script &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/search.html

@ -32,7 +32,7 @@ excluded term (the "searchexclude" config). The search is case insensitive
and doesn't try to read your mind (it doesn't do any verb tense matching or the
like).</p>
</div>
<p id="footer">search &mdash; npm@1.1.24</p>
<p id="footer">search &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/shrinkwrap.html

@ -26,7 +26,7 @@ but the shrinkwrap file will still be written.</p>
<p>Finally, 'callback' is a function that will be called when the shrinkwrap has
been saved.</p>
</div>
<p id="footer">shrinkwrap &mdash; npm@1.1.24</p>
<p id="footer">shrinkwrap &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/start.html

@ -19,7 +19,7 @@
<p>npm can run tests on multiple packages. Just specify multiple packages
in the <code>packages</code> parameter.</p>
</div>
<p id="footer">start &mdash; npm@1.1.24</p>
<p id="footer">start &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/stop.html

@ -19,7 +19,7 @@
<p>npm can run stop on multiple packages. Just specify multiple packages
in the <code>packages</code> parameter.</p>
</div>
<p id="footer">stop &mdash; npm@1.1.24</p>
<p id="footer">stop &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/submodule.html

@ -33,7 +33,7 @@ dependencies into the submodule folder.</p>
<ul><li>npm help json</li><li>git help submodule</li></ul>
</div>
<p id="footer">submodule &mdash; npm@1.1.24</p>
<p id="footer">submodule &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/tag.html

@ -29,7 +29,7 @@ parameter is missing or falsey (empty), the default froom the config will be
used. For more information about how to set this config, check
<code>man 3 npm-config</code> for programmatic usage or <code>man npm-config</code> for cli usage.</p>
</div>
<p id="footer">tag &mdash; npm@1.1.24</p>
<p id="footer">tag &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/test.html

@ -22,7 +22,7 @@ true.</p>
<p>npm can run tests on multiple packages. Just specify multiple packages
in the <code>packages</code> parameter.</p>
</div>
<p id="footer">test &mdash; npm@1.1.24</p>
<p id="footer">test &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/uninstall.html

@ -22,7 +22,7 @@ the name of a package to be uninstalled.</p>
<p>Finally, 'callback' is a function that will be called when all packages have been
uninstalled or when an error has been encountered.</p>
</div>
<p id="footer">uninstall &mdash; npm@1.1.24</p>
<p id="footer">uninstall &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/unpublish.html

@ -26,7 +26,7 @@ is what is meant.</p>
<p>If no version is specified, or if all versions are removed then
the root package entry is removed from the registry entirely.</p>
</div>
<p id="footer">unpublish &mdash; npm@1.1.24</p>
<p id="footer">unpublish &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/update.html

@ -18,7 +18,7 @@
<p>The 'packages' argument is an array of packages to update. The 'callback' parameter will be called when done or when an error occurs.</p>
</div>
<p id="footer">update &mdash; npm@1.1.24</p>
<p id="footer">update &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/version.html

@ -24,7 +24,7 @@ fail if the repo is not clean.</p>
parameter. The difference, however, is this function will fail if it does
not have exactly one element. The only element should be a version number.</p>
</div>
<p id="footer">version &mdash; npm@1.1.24</p>
<p id="footer">version &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/view.html

@ -99,7 +99,7 @@ the field name.</p>
<p>corresponding to the list of fields selected.</p>
</div>
<p id="footer">view &mdash; npm@1.1.24</p>
<p id="footer">view &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/whoami.html

@ -21,7 +21,7 @@
<p>This function is not useful programmatically</p>
</div>
<p id="footer">whoami &mdash; npm@1.1.24</p>
<p id="footer">whoami &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

10
deps/npm/html/doc/README.html

@ -96,21 +96,15 @@ git, and mess with it directly.</p>
<pre><code>git clone https://github.com/isaacs/npm.git
cd npm
git submodule update --init --recursive
sudo make install # (or: `node cli.js install -gf`)</code></pre>
<p>If you're sitting in the code folder reading this document in your
terminal, then you've already got the code. Just do:</p>
<pre><code>git submodule update --init --recursive
sudo make install</code></pre>
<pre><code>sudo make install</code></pre>
<p>and npm will install itself.</p>
<p>Note that github tarballs <strong>do not contain submodules</strong>, so
those won't work. You'll have to also fetch the appropriate submodules
listed in the .gitmodules file.</p>
<h2 id="Permissions-when-Using-npm-to-Install-Other-Stuff">Permissions when Using npm to Install Other Stuff</h2>
<p><strong>tl;dr</strong></p>
@ -267,7 +261,7 @@ will no doubt tell you to put the output in a gist or email.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/index.html">index(1)</a></li></ul>
</div>
<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.1.24</p>
<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/adduser.html

@ -39,7 +39,7 @@ authorize on a new machine.</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li><li><a href="../doc/whoami.html">whoami(1)</a></li></ul>
</div>
<p id="footer">adduser &mdash; npm@1.1.24</p>
<p id="footer">adduser &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/bin.html

@ -20,7 +20,7 @@
<ul><li><a href="../doc/prefix.html">prefix(1)</a></li><li><a href="../doc/root.html">root(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">bin &mdash; npm@1.1.24</p>
<p id="footer">bin &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/bugs.html

@ -36,7 +36,7 @@ config param.</p>
<ul><li><a href="../doc/docs.html">docs(1)</a></li><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">bugs &mdash; npm@1.1.24</p>
<p id="footer">bugs &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/build.html

@ -25,7 +25,7 @@ A folder containing a <code>package.json</code> file in its root.</li></ul>
<ul><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">build &mdash; npm@1.1.24</p>
<p id="footer">build &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/bundle.html

@ -20,7 +20,7 @@ install packages into the local space.</p>
<ul><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">bundle &mdash; npm@1.1.24</p>
<p id="footer">bundle &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/cache.html

@ -66,7 +66,7 @@ they do not make an HTTP request to the registry.</p>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/pack.html">pack(1)</a></li></ul>
</div>
<p id="footer">cache &mdash; npm@1.1.24</p>
<p id="footer">cache &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/changelog.html

@ -65,7 +65,7 @@
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li></ul>
</div>
<p id="footer">changelog &mdash; npm@1.1.24</p>
<p id="footer">changelog &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

23
deps/npm/html/doc/coding-style.html

@ -133,29 +133,18 @@ Just send the error message back as the first argument to the callback.</p>
<p>Always create a new Error object with your message. Don't just return a
string message to the callback. Stack traces are handy.</p>
<p>Use the <code>require("./utils/log").er</code> function. It takes a callback and an
error message, and returns an object that will report the message in the
event of a failure. It's quite handy.</p>
<pre><code>function myThing (args, cb) {
getData(args, function (er, data) {
if (er) return log.er(cb, "Couldn't get data")(er)
doSomethingElse(data, cb)
})
}
function justHasToWork (cb) {
doSomething(log.er(cb, "the doSomething failed."))
}</code></pre>
<h2 id="Logging">Logging</h2>
<p>Logging is done using the <a href="https://github.com/isaacs/npmlog">npmlog</a>
utility.</p>
<p>Please clean up logs when they are no longer helpful. In particular,
logging the same object over and over again is not helpful. Logs should
report what's happening so that it's easier to track down where a fault
occurs.</p>
<p>Use appropriate log levels. The default log() function logs at the
"info" level. See <code><a href="../doc/config.html">config(1)</a></code> and search for "loglevel".</p>
<p>Use appropriate log levels. See <code><a href="../doc/config.html">config(1)</a></code> and search for
"loglevel".</p>
<h2 id="Case-naming-etc">Case, naming, etc.</h2>
@ -191,7 +180,7 @@ set to anything."</p>
<ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
</div>
<p id="footer">coding-style &mdash; npm@1.1.24</p>
<p id="footer">coding-style &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/completion.html

@ -33,7 +33,7 @@ completions based on the arguments.</p>
<ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
</div>
<p id="footer">completion &mdash; npm@1.1.24</p>
<p id="footer">completion &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

135
deps/npm/html/doc/config.html

@ -105,7 +105,7 @@ global config.</p>
<p>The following shorthands are parsed on the command-line:</p>
<ul><li><code>-v</code>: <code>--version</code></li><li><code>-h</code>, <code>-?</code>, <code>--help</code>, <code>-H</code>: <code>--usage</code></li><li><code>-s</code>, <code>--silent</code>: <code>--loglevel silent</code></li><li><code>-q</code>, <code>--quiet</code>: <code>--loglevel warn</code></li><li><code>-d</code>: <code>--loglevel info</code></li><li><code>-dd</code>, <code>--verbose</code>: <code>--loglevel verbose</code></li><li><code>-ddd</code>: <code>--loglevel silly</code></li><li><code>-g</code>: <code>--global</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-m</code>: <code>--message</code></li><li><code>-p</code>, <code>--porcelain</code>: <code>--parseable</code></li><li><code>-reg</code>: <code>--registry</code></li><li><code>-v</code>: <code>--version</code></li><li><code>-f</code>: <code>--force</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-desc</code>: <code>--description</code></li><li><code>-S</code>: <code>--save</code></li><li><code>-D</code>: <code>--save-dev</code></li><li><code>-O</code>: <code>--save-optional</code></li><li><code>-y</code>: <code>--yes</code></li><li><code>-n</code>: <code>--yes false</code></li><li><code>ll</code> and <code>la</code> commands: <code>ls --long</code></li></ul>
<ul><li><code>-v</code>: <code>--version</code></li><li><code>-h</code>, <code>-?</code>, <code>--help</code>, <code>-H</code>: <code>--usage</code></li><li><code>-s</code>, <code>--silent</code>: <code>--loglevel silent</code></li><li><code>-q</code>, <code>--quiet</code>: <code>--loglevel warn</code></li><li><code>-d</code>: <code>--loglevel info</code></li><li><code>-dd</code>, <code>--verbose</code>: <code>--loglevel verbose</code></li><li><code>-ddd</code>: <code>--loglevel silly</code></li><li><code>-g</code>: <code>--global</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-m</code>: <code>--message</code></li><li><code>-p</code>, <code>--porcelain</code>: <code>--parseable</code></li><li><code>-reg</code>: <code>--registry</code></li><li><code>-v</code>: <code>--version</code></li><li><code>-f</code>: <code>--force</code></li><li><code>-l</code>: <code>--long</code></li><li><code>-desc</code>: <code>--description</code></li><li><code>-S</code>: <code>--save</code></li><li><code>-D</code>: <code>--save-dev</code></li><li><code>-O</code>: <code>--save-optional</code></li><li><code>-B</code>: <code>--save-bundle</code></li><li><code>-y</code>: <code>--yes</code></li><li><code>-n</code>: <code>--yes false</code></li><li><code>ll</code> and <code>la</code> commands: <code>ls --long</code></li></ul>
<p>If the specified configuration param resolves unambiguously to a known
configuration parameter, then it is expanded to that configuration
@ -152,30 +152,6 @@ the package.json has this:</p>
<p>Force npm to always require authentication when accessing the registry,
even for <code>GET</code> requests.</p>
<h3 id="bin-publish">bin-publish</h3>
<ul><li>Default: false</li><li>Type: Boolean</li></ul>
<p>If set to true, then binary packages will be created on publish.</p>
<p>This is the way to opt into the "bindist" behavior described below.</p>
<h3 id="bindist">bindist</h3>
<ul><li>Default: Unstable node versions, <code>null</code>, otherwise
<code>"&lt;node version&gt;-&lt;platform&gt;-&lt;os release&gt;"</code></li><li>Type: String or <code>null</code></li></ul>
<p>Experimental: on stable versions of node, binary distributions will be
created with this tag. If a user then installs that package, and their
<code>bindist</code> tag is found in the list of binary distributions, they will
get that prebuilt version.</p>
<p>Pre-build node packages have their preinstall, install, and postinstall
scripts stripped (since they are run prior to publishing), and do not
have their <code>build</code> directories automatically ignored.</p>
<p>It's yet to be seen if this is a good idea.</p>
<h3 id="browser">browser</h3>
<ul><li>Default: OS X: <code>"open"</code>, others: <code>"google-chrome"</code></li><li>Type: String</li></ul>
@ -200,6 +176,24 @@ to trust only that specific signing authority.</p>
<p>The location of npm's cache directory. See <code><a href="../doc/cache.html">cache(1)</a></code></p>
<h3 id="cache-lock-stale">cache-lock-stale</h3>
<ul><li>Default: 60000 (1 minute)</li><li>Type: Number</li></ul>
<p>The number of ms before cache folder lockfiles are considered stale.</p>
<h3 id="cache-lock-retries">cache-lock-retries</h3>
<ul><li>Default: 10</li><li>Type: Number</li></ul>
<p>Number of times to retry to acquire a lock on cache folder lockfiles.</p>
<h3 id="cache-lock-wait">cache-lock-wait</h3>
<ul><li>Default: 10000 (10 seconds)</li><li>Type: Number</li></ul>
<p>Number of ms to wait for cache lock files to expire.</p>
<h3 id="cache-max">cache-max</h3>
<ul><li>Default: Infinity</li><li>Type: Number</li></ul>
@ -263,6 +257,14 @@ or <code>"notepad"</code> on Windows.</li><li>Type: path</li></ul>
<p>The command to run for <code>npm edit</code> or <code>npm config edit</code>.</p>
<h3 id="engine-strict">engine-strict</h3>
<ul><li>Default: false</li><li>Type: Boolean</li></ul>
<p>If set to true, then npm will stubbornly refuse to install (or even
consider installing) any package that claims to not be compatible with
the current Node.js version.</p>
<h3 id="force">force</h3>
<ul><li>Default: false</li><li>Type: Boolean</li></ul>
@ -271,6 +273,34 @@ or <code>"notepad"</code> on Windows.</li><li>Type: path</li></ul>
<ul><li>lifecycle script failure does not block progress.</li><li>publishing clobbers previously published versions.</li><li>skips cache when requesting from the registry.</li><li>prevents checks against clobbering non-npm files.</li></ul>
<h3 id="fetch-retries">fetch-retries</h3>
<ul><li>Default: 2</li><li>Type: Number</li></ul>
<p>The "retries" config for the <code>retry</code> module to use when fetching
packages from the registry.</p>
<h3 id="fetch-retry-factor">fetch-retry-factor</h3>
<ul><li>Default: 10</li><li>Type: Number</li></ul>
<p>The "factor" config for the <code>retry</code> module to use when fetching
packages.</p>
<h3 id="fetch-retry-mintimeout">fetch-retry-mintimeout</h3>
<ul><li>Default: 10000 (10 seconds)</li><li>Type: Number</li></ul>
<p>The "minTimeout" config for the <code>retry</code> module to use when fetching
packages.</p>
<h3 id="fetch-retry-maxtimeout">fetch-retry-maxtimeout</h3>
<ul><li>Default: 60000 (1 minute)</li><li>Type: Number</li></ul>
<p>The "maxTimeout" config for the <code>retry</code> module to use when fetching
packages.</p>
<h3 id="git">git</h3>
<ul><li>Default: <code>"git"</code></li><li>Type: String</li></ul>
@ -333,6 +363,15 @@ user.</p>
<p>A white-space separated list of glob patterns of files to always exclude
from packages when building tarballs.</p>
<h3 id="init-module">init-module</h3>
<ul><li>Default: ~/.npm-init.js</li><li>Type: path</li></ul>
<p>A module that will be loaded by the <code>npm init</code> command. See the
documentation for the
<a href="https://github.com/isaacs/init-package-json">init-package-json</a> module
for more information, or <a href="../doc/init.html">init(1)</a>.</p>
<h3 id="init-version">init.version</h3>
<ul><li>Default: "0.0.0"</li><li>Type: semver</li></ul>
@ -381,12 +420,6 @@ if one of the two conditions are met:</p>
<ul><li>The package is not already installed globally, or</li><li>the globally installed version is identical to the version that is
being installed locally.</li></ul>
<h3 id="logfd">logfd</h3>
<ul><li>Default: stderr file descriptor</li><li>Type: Number or Stream</li></ul>
<p>The location to write log output.</p>
<h3 id="loglevel">loglevel</h3>
<ul><li>Default: "http"</li><li>Type: String</li><li>Values: "silent", "win", "error", "warn", "http", "info", "verbose", "silly"</li></ul>
@ -397,12 +430,16 @@ being installed locally.</li></ul>
<p>Any logs of a higher level than the setting are shown.
The default is "http", which shows http, warn, and error output.</p>
<h3 id="logprefix">logprefix</h3>
<h3 id="logstream">logstream</h3>
<ul><li>Default: process.stderr</li><li>Type: Stream</li></ul>
<ul><li>Default: true on Posix, false on Windows</li><li>Type: Boolean</li></ul>
<p>This is the stream that is passed to the
<a href="https://github.com/isaacs/npmlog">npmlog</a> module at run time.</p>
<p>Whether or not to prefix log messages with "npm" and the log level. See
also "color" and "loglevel".</p>
<p>It cannot be set from the command line, but if you are using npm
programmatically, you may wish to send logs to somewhere other than
stderr.</p>
<h3 id="long">long</h3>
@ -444,12 +481,6 @@ also "color" and "loglevel".</p>
<p>A node module to <code>require()</code> when npm loads. Useful for programmatic
usage.</p>
<h3 id="outfd">outfd</h3>
<ul><li>Default: standard output file descriptor</li><li>Type: Number or Stream</li></ul>
<p>Where to write "normal" output. This has no effect on log output.</p>
<h3 id="parseable">parseable</h3>
<ul><li>Default: false</li><li>Type: Boolean</li></ul>
@ -514,14 +545,31 @@ this as true.</p>
<p>Save installed packages to a package.json file as dependencies.</p>
<p>When used with the <code>npm rm</code> command, it removes it from the dependencies
hash.</p>
<p>Only works if there is already a package.json file present.</p>
<h3 id="save-bundle">save-bundle</h3>
<ul><li>Default: false</li><li>Type: Boolean</li></ul>
<p>If a package would be saved at install time by the use of <code>--save</code>,
<code>--save-dev</code>, or <code>--save-optional</code>, then also put it in the
<code>bundleDependencies</code> list.</p>
<p>When used with the <code>npm rm</code> command, it removes it from the
bundledDependencies list.</p>
<h3 id="save-dev">save-dev</h3>
<ul><li>Default: false</li><li>Type: Boolean</li></ul>
<p>Save installed packages to a package.json file as devDependencies.</p>
<p>When used with the <code>npm rm</code> command, it removes it from the devDependencies
hash.</p>
<p>Only works if there is already a package.json file present.</p>
<h3 id="save-optional">save-optional</h3>
@ -530,6 +578,9 @@ this as true.</p>
<p>Save installed packages to a package.json file as optionalDependencies.</p>
<p>When used with the <code>npm rm</code> command, it removes it from the devDependencies
hash.</p>
<p>Only works if there is already a package.json file present.</p>
<h3 id="searchopts">searchopts</h3>
@ -684,7 +735,7 @@ then answer "no" to any prompt.</p>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
</div>
<p id="footer">config &mdash; npm@1.1.24</p>
<p id="footer">config &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/deprecate.html

@ -29,7 +29,7 @@ something like this:</p>
<ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">deprecate &mdash; npm@1.1.24</p>
<p id="footer">deprecate &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/developers.html

@ -160,7 +160,7 @@ from a fresh checkout.</p>
<ul><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">developers &mdash; npm@1.1.24</p>
<p id="footer">developers &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/disputes.html

@ -80,7 +80,7 @@ license statement)</li><li>Illegal content.</li></ol>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li></ul>
</div>
<p id="footer">disputes &mdash; npm@1.1.24</p>
<p id="footer">disputes &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/docs.html

@ -37,7 +37,7 @@ config param.</p>
<ul><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">docs &mdash; npm@1.1.24</p>
<p id="footer">docs &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/edit.html

@ -37,7 +37,7 @@ or <code>"notepad"</code> on Windows.</li><li>Type: path</li></ul>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/explore.html">explore(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">edit &mdash; npm@1.1.24</p>
<p id="footer">edit &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/explore.html

@ -40,7 +40,7 @@ Windows</li><li>Type: path</li></ul>
<ul><li><a href="../doc/submodule.html">submodule(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/edit.html">edit(1)</a></li><li><a href="../doc/rebuild.html">rebuild(1)</a></li><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">explore &mdash; npm@1.1.24</p>
<p id="footer">explore &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/faq.html

@ -241,7 +241,7 @@ We'll have someone kick it or something.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li></ul>
</div>
<p id="footer">faq &mdash; npm@1.1.24</p>
<p id="footer">faq &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/folders.html

@ -205,7 +205,7 @@ cannot be found elsewhere. See <code><a href="../doc/json.html">json(1)</a></co
<ul><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/pack.html">pack(1)</a></li><li><a href="../doc/cache.html">cache(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li></ul>
</div>
<p id="footer">folders &mdash; npm@1.1.24</p>
<p id="footer">folders &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/help-search.html

@ -38,7 +38,7 @@ where the terms were found in the documentation.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/help.html">help(1)</a></li></ul>
</div>
<p id="footer">help-search &mdash; npm@1.1.24</p>
<p id="footer">help-search &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/help.html

@ -36,7 +36,7 @@ matches are equivalent to specifying a topic name.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/README.html">README</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/help-search.html">help-search(1)</a></li><li><a href="../doc/index.html">index(1)</a></li></ul>
</div>
<p id="footer">help &mdash; npm@1.1.24</p>
<p id="footer">help &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/index.html

@ -384,7 +384,7 @@
<p> Display npm username</p>
</div>
<p id="footer">index &mdash; npm@1.1.24</p>
<p id="footer">index &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/doc/init.html

@ -27,9 +27,9 @@ without a really good reason to do so.</p>
<h2 id="SEE-ALSO">SEE ALSO</h2>
<ul><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/version.html">version(1)</a></li></ul>
<ul><li><a href="https://github.com/isaacs/init-package-json">https://github.com/isaacs/init-package-json</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/version.html">version(1)</a></li></ul>
</div>
<p id="footer">init &mdash; npm@1.1.24</p>
<p id="footer">init &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/doc/install.html

@ -72,7 +72,7 @@ local copy exists on disk.</p>
<pre><code>npm install sax --force</code></pre>
<p>The <code>--global</code> argument will cause npm to install the package globally
rather than locally. See <code><a href="../doc/global.html">global(1)</a></code>.</p>
rather than locally. See <code><a href="../doc/folders.html">folders(1)</a></code>.</p>
<p>The <code>--link</code> argument will cause npm to link global installs into the
local space in some cases.</p>
@ -133,7 +133,7 @@ affects a real use-case, it will be investigated.</p>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/rebuild.html">rebuild(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/tag.html">tag(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/shrinkwrap.html">shrinkwrap(1)</a></li></ul>
</div>
<p id="footer">install &mdash; npm@1.1.24</p>
<p id="footer">install &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

21
deps/npm/html/doc/json.html

@ -425,8 +425,7 @@ if (foo) {
<h2 id="engines">engines</h2>
<p>You can specify the version of
node that your stuff works on:</p>
<p>You can specify the version of node that your stuff works on:</p>
<pre><code>{ "engines" : { "node" : "&gt;=0.1.27 &lt;0.1.30" } }</code></pre>
@ -442,6 +441,22 @@ are capable of properly installing your program. For example:</p>
<pre><code>{ "engines" : { "npm" : "~1.0.20" } }</code></pre>
<p>Note that, unless the user has set the <code>engine-strict</code> config flag, this
field is advisory only.</p>
<h2 id="engineStrict">engineStrict</h2>
<p>If you are sure that your module will <em>definitely not</em> run properly on
versions of Node/npm other than those specified in the <code>engines</code> hash,
then you can set <code>"engineStrict": true</code> in your package.json file.
This will override the user's <code>engine-strict</code> config setting.</p>
<p>Please do not do this unless you are really very very sure. If your
engines hash is something overly restrictive, you can quite easily and
inadvertently lock yourself into obscurity and prevent your users from
updating to new versions of Node. Consider this choice carefully. If
people abuse it, it will be removed in a future version of npm.</p>
<h2 id="os">os</h2>
<p>You can specify which operating systems your
@ -509,7 +524,7 @@ overridden.</p>
<ul><li><a href="../doc/semver.html">semver(1)</a></li><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/version.html">version(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li></ul>
</div>
<p id="footer">json &mdash; npm@1.1.24</p>
<p id="footer">json &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/link.html

@ -58,7 +58,7 @@ installation target into your project's <code>node_modules</code> folder.</p>
<ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">link &mdash; npm@1.1.24</p>
<p id="footer">link &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

22
deps/npm/html/doc/list.html

@ -10,20 +10,26 @@
<h2 id="SYNOPSIS">SYNOPSIS</h2>
<pre><code>npm list
npm ls
npm la
npm ll</code></pre>
<pre><code>npm list [&lt;pkg&gt; ...]
npm ls [&lt;pkg&gt; ...]
npm la [&lt;pkg&gt; ...]
npm ll [&lt;pkg&gt; ...]</code></pre>
<h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>This command will print to stdout all the versions of packages that are
installed, as well as their dependencies, in a tree-structure.</p>
<p>It does not take positional arguments, though you may set config flags
like with any other command, such as <code>-g</code> to list global packages.</p>
<p>Positional arguments are <code>name@version-range</code> identifiers, which will
limit the results to only the paths to the packages named. Note that
nested packages will <em>also</em> show the paths to the specified packages.
For example, running <code>npm ls promzard</code> in npm's source tree will show:</p>
<p>It will print out extraneous, missing, and invalid packages.</p>
<pre><code>npm@1.1.37 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5</code></pre>
<p>It will show print out extraneous, missing, and invalid packages.</p>
<p>When run as <code>ll</code> or <code>la</code>, it shows extended information by default.</p>
@ -58,7 +64,7 @@ project.</p>
<ul><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/prune.html">prune(1)</a></li><li><a href="../doc/outdated.html">outdated(1)</a></li><li><a href="../doc/update.html">update(1)</a></li></ul>
</div>
<p id="footer">list &mdash; npm@1.1.24</p>
<p id="footer">list &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/doc/npm.html

@ -14,7 +14,7 @@
<h2 id="VERSION">VERSION</h2>
<p>1.1.24</p>
<p>1.1.37</p>
<h2 id="DESCRIPTION">DESCRIPTION</h2>
@ -135,7 +135,7 @@ will no doubt tell you to put the output in a gist or email.</p>
<ul><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/README.html">README</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/index.html">index(1)</a></li><li><a href="../api/npm.html">npm(3)</a></li></ul>
</div>
<p id="footer">npm &mdash; npm@1.1.24</p>
<p id="footer">npm &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/outdated.html

@ -21,7 +21,7 @@ packages are currently outdated.</p>
<ul><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li></ul>
</div>
<p id="footer">outdated &mdash; npm@1.1.24</p>
<p id="footer">outdated &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/owner.html

@ -34,7 +34,7 @@ that is not implemented at this time.</p>
<ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/disputes.html">disputes(1)</a></li></ul>
</div>
<p id="footer">owner &mdash; npm@1.1.24</p>
<p id="footer">owner &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/pack.html

@ -29,7 +29,7 @@ overwritten the second time.</p>
<ul><li><a href="../doc/cache.html">cache(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">pack &mdash; npm@1.1.24</p>
<p id="footer">pack &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/prefix.html

@ -20,7 +20,7 @@
<ul><li><a href="../doc/root.html">root(1)</a></li><li><a href="../doc/bin.html">bin(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">prefix &mdash; npm@1.1.24</p>
<p id="footer">prefix &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/prune.html

@ -25,7 +25,7 @@ package's dependencies list.</p>
<ul><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/list.html">list(1)</a></li></ul>
</div>
<p id="footer">prune &mdash; npm@1.1.24</p>
<p id="footer">prune &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/publish.html

@ -29,7 +29,7 @@ the registry. Overwrites when the "--force" flag is set.</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li><li><a href="../doc/deprecate.html">deprecate(1)</a></li><li><a href="../doc/tag.html">tag(1)</a></li></ul>
</div>
<p id="footer">publish &mdash; npm@1.1.24</p>
<p id="footer">publish &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/rebuild.html

@ -25,7 +25,7 @@ the new binary.</p>
<ul><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">rebuild &mdash; npm@1.1.24</p>
<p id="footer">rebuild &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/registry.html

@ -97,7 +97,7 @@ ask for help on the <a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com
<ul><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/disputes.html">disputes(1)</a></li></ul>
</div>
<p id="footer">registry &mdash; npm@1.1.24</p>
<p id="footer">registry &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/removing-npm.html

@ -58,7 +58,7 @@ modules. To track those down, you can do the following:</p>
<ul><li><a href="../doc/README.html">README</a></li><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/prune.html">prune(1)</a></li></ul>
</div>
<p id="footer">removing-npm &mdash; npm@1.1.24</p>
<p id="footer">removing-npm &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/restart.html

@ -24,7 +24,7 @@ the "start" script.</p>
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
</div>
<p id="footer">restart &mdash; npm@1.1.24</p>
<p id="footer">restart &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/root.html

@ -20,7 +20,7 @@
<ul><li><a href="../doc/prefix.html">prefix(1)</a></li><li><a href="../doc/bin.html">bin(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">root &mdash; npm@1.1.24</p>
<p id="footer">root &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/run-script.html

@ -23,7 +23,7 @@ called directly, as well.</p>
<ul><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
</div>
<p id="footer">run-script &mdash; npm@1.1.24</p>
<p id="footer">run-script &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/scripts.html

@ -177,7 +177,7 @@ will sudo the npm command in question.</li></ul>
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">scripts &mdash; npm@1.1.24</p>
<p id="footer">scripts &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/search.html

@ -24,7 +24,7 @@ expression characters must be escaped or quoted in most shells.)</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/view.html">view(1)</a></li></ul>
</div>
<p id="footer">search &mdash; npm@1.1.24</p>
<p id="footer">search &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/semver.html

@ -104,7 +104,7 @@ that satisfies the range, or null if none of them do.</li></ul>
<ul><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">semver &mdash; npm@1.1.24</p>
<p id="footer">semver &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/shrinkwrap.html

@ -169,7 +169,7 @@ versions.</p>
<ul><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/list.html">list(1)</a></li></ul>
</div>
<p id="footer">shrinkwrap &mdash; npm@1.1.24</p>
<p id="footer">shrinkwrap &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/star.html

@ -26,7 +26,7 @@ a vaguely positive way to show that you care.</p>
<ul><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/whoami.html">whoami(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li></ul>
</div>
<p id="footer">star &mdash; npm@1.1.24</p>
<p id="footer">star &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/start.html

@ -20,7 +20,7 @@
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
</div>
<p id="footer">start &mdash; npm@1.1.24</p>
<p id="footer">start &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/stop.html

@ -20,7 +20,7 @@
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li></ul>
</div>
<p id="footer">stop &mdash; npm@1.1.24</p>
<p id="footer">stop &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/submodule.html

@ -33,7 +33,7 @@ dependencies into the submodule folder.</p>
<ul><li><a href="../doc/json.html">json(1)</a></li><li>git help submodule</li></ul>
</div>
<p id="footer">submodule &mdash; npm@1.1.24</p>
<p id="footer">submodule &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/tag.html

@ -21,7 +21,7 @@
<ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">tag &mdash; npm@1.1.24</p>
<p id="footer">tag &mdash; npm@1.1.37</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

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

Loading…
Cancel
Save