1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

deps: upgrade to npm 3.7.3

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/5369
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
This commit is contained in:
Kat Marchán 2016-02-22 11:59:14 -08:00 committed by Myles Borins
parent 061ebb39c9
commit 4ed038808f
390 changed files with 8503 additions and 6560 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
deps/npm/.mailmap vendored
View File

@ -11,6 +11,7 @@ Cedric Nelson <cedric.nelson@gmail.com>
Charlie Robbins <charlie.robbins@gmail.com>
Dalmais Maxence <root@ip-10-195-202-5.ec2.internal>
Danila Gerasimov <danila.gerasimov@gmail.com>
Dave Galbraith <dave@jut.io>
David Beitey <david@davidjb.com>
Domenic Denicola <domenic@domenicdenicola.com>
Einar Otto Stangvik <einaros@gmail.com>

3
deps/npm/.travis.yml vendored
View File

@ -11,7 +11,8 @@ env:
before_install:
- "npm config set spin false"
- "node . install -g ."
- "sudo mkdir -p /var/run/couchdb"
- "mkdir -p /var/run/couchdb"
sudo: false
script: "npm run-script test-all"
notifications:
slack: npm-inc:kRqQjto7YbINqHPb1X6nS3g8

12
deps/npm/AUTHORS vendored
View File

@ -352,3 +352,15 @@ Jimb Esser <jimb@yahoo-inc.com>
Alexis Campailla <alexis@janeasystems.com>
Chris Chua <chris.sirhc@gmail.com>
Beau Gunderson <beau@beaugunderson.com>
Dave Galbraith <dave@jut.io>
s100 <shughes1@uk.ibm.com>
Sergey Simonchik <sergey.simonchik@jetbrains.com>
Vanja Radovanović <elvanja@gmail.com>
Jonathan Persson <persson.jonathan@gmail.com>
Vedat Mahir YILMAZ <mahir@vedatmahir.com>
Samuel Reed <samuel.trace.reed@gmail.com>
Rafał Legiędź <rafal.legiedz@gmail.com>
Jan Schär <jscissr@gmail.com>
Xcat Liu <xcatliu@gmail.com>
harryh <Aourin@users.noreply.github.com>
Prayag Verma <prayag.verma@gmail.com>

274
deps/npm/CHANGELOG.md vendored
View File

@ -1,3 +1,277 @@
### v3.7.3 (2016-02-11):
Hey all! We've got a pretty small release this week -- just documentation
updates and a couple of dependencies. This release also includes a particular
dependency upgrade that makes it so we're exclusively using the latest version
of `graceful-fs`, which'll make it so things keep working with future Node.js
releases.
A certain internal Node.js API was deprecated and slated for future removal from
Node Core. This API was critical for versions of `graceful-fs@<4`, before a
different approach was used to achieve similar ends. By upgrading this library,
and making sure all our dependencies are also updated, we've ensured npm will
continue to work once the API is finally removed. Older versions of npm, on the
other hand, will simply not work on future versions of Node.js.
#### DEPENDENCY UPGRADES
* [`29536f4`](https://github.com/npm/npm/commit/29536f42da6c06091c9acbc8952f72daa8a9412c)
`cmd-shim@2.0.2`:
Final straggler using `graceful-fs@<4`.
([@ForbesLindesay](https://github.com/ForbesLindesay))
* [`5f59e74`](https://github.com/npm/npm/commit/5f59e748ef4c066756bb204a452cecd0543c7a2f)
`lodash.uniq@4.1.0`
([@jdalton](https://github.com/jdalton))
* [`987cabe`](https://github.com/npm/npm/commit/987cabe8a18abcb5a685685958bf74c7258a979c)
`lodash.union@4.1.0`
([@jdalton](https://github.com/jdalton))
* [`5c641f0`](https://github.com/npm/npm/commit/5c641f05fdc153c6bb06a89c46fe2a345ce413db)
`lodash.clonedeep@4.1.0`
([@jdalton](https://github.com/jdalton))
#### EVERYONE GETTING SOCKS LIKE IT'S OPRAH'S SHOW
* [`9ea5658`](https://github.com/npm/npm/commit/9ea56582ca4d0991dbed44f992c88f08a643cb4b)
[#11410](https://github.com/npm/npm/pull/11410)
Fixed a small spelling error in `npm-config.md`.
([@pra85](https://github.com/pra85))
* [`2a11e56`](https://github.com/npm/npm/commit/2a11e562a14bce18b6ddca6c20d17f97b6a8ec2f)
[#11403](https://github.com/npm/npm/pull/11403)
Removes `--depth Infinity` warning from documentation -- this operation should
actually be totally safe as of `npm@3`. (The warning remains for `npm@2`.)
([@Aourin](https://github.com/Aourin))
* [`42a4727`](https://github.com/npm/npm/commit/42a4727bfb1e21c890b8e2babda55e06ac2bda29)
[#11391](https://github.com/npm/npm/pull/11391)
Fixed versions of `shrinkwrap.json` in examples in documentation for `npm
shrinkwrap`, which did not quite match up.
([@xcatliu](https://github.com/xcatliu))
### v3.7.2 (2016-02-04):
This week, the CLI team has been busy working on rewriting tests to support
getting coverage reports going and running all of our tests on Windows.
Meanwhile, we've got a bunch of dependency updates and one or two other
things.
#### TESTS WENT INTO HIDING
Last week we took a patch from [@substack](https://github.com/substack) to
stop the installer from reordering arrays in an installed module's
`package.json`... but somehow I dropped the test when I was rebasing.
* [`21b9271`](https://github.com/npm/npm/commit/21b927182514a0ff6d9f34480bfc39f72e3e9f8c)
[#10063](https://github.com/npm/npm/issues/10063)
Restore test that verifies that we don't re-order arrays in a module's
`package.json` on install.
([@substack](https://github.com/substack))
#### DOCUMENTATION FIXES
* [`c67521d`](https://github.com/npm/npm/commit/c67521dc6c1e41d39d02c74105e41442851d23bb)
[#11348](https://github.com/npm/npm/pull/11348)
Improve the documentation around which files are ALWAYS included in published packages
and which are ALWAYS excluded.
([@jscissr](https://github.com/jscissr))
* [`7ef6793`](https://github.com/npm/npm/commit/7ef6793cd191cc8d88340f7e1ce9c9e3d6f0b2f4)
[#11348](https://github.com/npm/npm/pull/11348)
The release date on the 3.7.0 changelog entry was wrong. I honestly don't
know how I keep doing this. =D
([@rafek](https://github.com/rafek))
#### DEPENDENCY UPDATES
* [`8a3c80c`](https://github.com/npm/npm/commit/8a3c80c4fd3d82fe937f30bc7cbd3dee51a8a893)
`graceful-fs@4.1.3`:
Fix a bug where close wasn't getting made graceful.
([@isaacs](https://github.com/isaacs))
`lodash` saw updates across most of its modules this week with browser
campatibility fixes that don't really impact us.
* [`2df342b`](https://github.com/npm/npm/commit/2df342bf30efa99b98016acc8a5dc03e00b58b9c)
`lodash.without@4.0.2`
([@jdalton](https://github.com/jdalton))
* [`86aa91d`](https://github.com/npm/npm/commit/86aa91dce60f6b6a92bb3ba2bf6e6be1f6afc750)
`lodash.uniq@4.0.2`
([@jdalton](https://github.com/jdalton))
* [`0a94bf6`](https://github.com/npm/npm/commit/0a94bf6af0ebd38d080f92257e0cd9bae40b31ff)
`lodash.union@4.0.2`
([@jdalton](https://github.com/jdalton))
* [`b4c9582`](https://github.com/npm/npm/commit/b4c9582b4ef5991f3d155e0c6142ed1c631860af)
`lodash.isarguments@3.0.6`
([@jdalton](https://github.com/jdalton))
* [`efe766c`](https://github.com/npm/npm/commit/efe766c63c0948a4ae4c0d12f2b834629ab86e92)
`lodash.keys@4.0.2`: Minor code cleanup and the above.
([@jdalton](https://github.com/jdalton))
* [`36abb24`](https://github.com/npm/npm/commit/36abb24ef31017adbf325e7f833d5d4b0f03f5d4)
`lodash.clonedeep@4.0.4`:
Add support for cloning prototype objects and the above.
([@jdalton](https://github.com/jdalton))
### v3.7.1 (2016-02-01):
Super quick Monday patch on last week's release.
If you ever wondered why we release things to the `npm@next` tag for a week
before promoting them to `npm@latest`, this is it!
#### RELEASE TRAIN VINDICATED (again)
* [`adcaf04`](adcaf047811dcc475ab1984fc93fe34540fc03d7)
[#11349](https://github.com/npm/npm/issues/11349)
Revert last weeks change to use JSON clone instead of `lodash.cloneDeep`.
([@iarna](https://github.com/iarna))
### v3.7.0 (2016-01-29):
Hi all! This week brings us some important performance improvements,
support for git submodules(!) and a bunch of bug fixes.
#### PERFORMANCE
`gauge`, the module responsible for drawing `npm`'s progress bars, had an
embarrassing bug in its debounce implementation that resulted in it, on many
systems, actually being _slower_ than if it hadn't been debouncing. This was
due to it destroying and then creating a timer object any time it got an
update while waiting on its minimum update period to elapse. This only was
a measurable slowdown when sending thousands of updates a second, but
unfortunately parts of `npm`'s logging do exactly that. This has been patched
to eliminate that churn, and our testing shows the progress bar as being
eliminated as a source of slow down.
Meanwhile, `are-we-there-yet` is the module that tracks just how complete
our big asynchronous install process is. [@STRML](https://github.com/STRML)
spent some time auditing its source and made a few smaller performance
improvements to it. Most impactful was eliminating a bizarre bit of code
that was both binding to AND closing over the current object. I don't have
any explanation for how that crept in. =D
* [`c680fa9`](https://github.com/npm/npm/commit/c680fa9f8135759eb5512f4b86e47fa265733f79)
`npmlog@2.0.2`: New `are-we-there-yet` with performance patches from
[@STRML](https://github.com/STRML). New `gauge` with timer churn
performance patch.
([@iarna](https://github.com/iarna))
We were also using `lodash`'s `cloneDeep` on `package.json` data which is
definitely overkill, seeing as `package.json` data has all the restrictions
of being `json`. The fix for this is just swapping that out for something
that does a pair of `JSON.stringify`/`JSON.parse`, which is distinctly more
speedy.
* [`1d1ea7e`](https://github.com/npm/npm/commit/1d1ea7eeb958034878eb6573149aeecc686888d3)
[#11306](https://github.com/npm/npm/pull/11306)
Use JSON clone instead of `lodash.cloneDeep`.
([@STRML](https://github.com/STRML))
#### NEW FEATURE: GIT SUBMODULE SUPPORT
Long, long requested– the referenced issue is from 2011– we're finally
getting rudimentary git submodule support.
* [`39dea9c`](https://github.com/npm/npm/commit/39dea9ca4216c6ea628f5ca47d2b34a4b251a1ed)
[#1876](https://github.com/npm/npm/issues/1876)
Add support for git submodules in git remotes. This is a fairly simple
approach, which does not leverage the git caching mechanism to cache
submodules. It also doesn't provide a means to disable automatic
initialization, e.g. via a setting in the `.gitmodules` file.
([@gagern](https://github.com/gagern))
#### ROBUSTNESS
* [`5dec02a`](https://github.com/npm/npm/commit/5dec02a3d0e82202c021e27aff9d006283fdc25a)
[#10347](https://github.com/npm/npm/issues/10347)
There is an obscure feature that lets you monkey-patch npm when it starts
up. If the module being required with this feature failed, it would
previously just make `npm` error out– this reduces that to a warning.
([@evanlucas](https://github.com/evanlucas))
#### BUG FIXES
* [`9ab8b8d`](https://github.com/npm/npm/commit/9ab8b8d047792612ae7f9a6079745d51d5283a53)
[#10820](https://github.com/npm/npm/issues/10820)
Fix a bug with `npm ls` where if you asked for ONLY production dependencies in output
it would exclude dependencies that were BOTH production AND development dependencies.
([@davidvgalbraith](https://github.com/davidvgalbraith))
* [`6803fed`](https://github.com/npm/npm/commit/6803fedadb8f9b36cd85f7338ecf75d1d183c833)
[#8982](https://github.com/npm/npm/issues/8982)
Fix a bug where, under some circumstances, if you had a path that
contained the name of a package being installed somewhere in it, `npm`
would incorrectly refuse to run lifecycle scripts.
([@elvanja](https://github.com/elvanja))
* [`3eae40b`](https://github.com/npm/npm/commit/3eae40b7a681aa067dfe4fea8c9a76da5b508b48)
[#9253](https://github.com/npm/npm/issues/9253)
Fix a bug where, when running lifecycle scripts, if the Node.js binary you ran
`npm` with wasn't in your `PATH`, `npm` wouldn't use it to run your scripts.
([@segrey](https://github.com/segrey))
* [`61daa6a`](https://github.com/npm/npm/commit/61daa6ae8cbc041d3a0d8a6f8f268b47dd8176eb)
[#11014](https://github.com/npm/npm/issues/11014)
Fix a bug where running `rimraf node_modules/<package>` followed by `npm
rm --save <package>` would fail. `npm` now correctly removes the module
from your `package.json` even though it doesn't exist on disk.
([@davidvgalbraith](https://github.com/davidvgalbraith))
* [`a605586`](https://github.com/npm/npm/commit/a605586df134ee97c95f89c4b4bd6bc73f7aa439)
[#9679](https://github.com/npm/npm/issues/9679)
Fix a bug where `npm install --save git+https://…` would save a `https://`
url to your `package.json` which was a problem because `npm` wouldn't then
know that it was a git repo.
([@gagern](https://github.com/gagern))
* [`bbdc700`](https://github.com/npm/npm/commit/bbdc70024467c365cc4e06b8410947c04b6f145b)
[#10063](https://github.com/npm/npm/issues/10063)
Fix a bug where `npm` would change the order of array properties in the
`package.json` files of dependencies. `npm` adds a bunch of stuff to
`package.json` files in your `node_modules` folder for debugging and
bookkeeping purposes. As a part of this process it sorts the object to
reduce file churn when it does updates. This fixes a bug where the arrays
in the object were also getting sorted. This wasn't a problem for
properties that `npm` itself maintains, but _is_ a problem for properties
used by other packages.
([@substack](https://github.com/substack))
#### DOCS IMPROVEMENTS
* [`2609a29`](https://github.com/npm/npm/commit/2609a2950704f577ac888668e81ba514568fab44)
[#11273](https://github.com/npm/npm/pull/11273)
Include an example of viewing package version history in the `npm view` documentation.
([@vedatmahir](https://github.com/vedatmahir))
* [`719ea9c`](https://github.com/npm/npm/commit/719ea9c45a5c3233f3afde043b89824aad2df0a7)
[#11272](https://github.com/npm/npm/pull/11272)
Fix typographical issue in `npm update` documentation.
([@jonathanp](https://github.com/jonathanp))
* [`cb9df5a`](https://github.com/npm/npm/commit/cb9df5a37091e06071d8704b629e7ebaa41c37fe)
[#11215](https://github.com/npm/npm/pull/11215)
Do not call `SEE LICENSE IN <filename>` an _SPDX expression_, as it's not.
([@kemitchell](https://github.com/kemitchell))
* [`f427934`](https://github.com/npm/npm/commit/f4279346c368da4bca09385f773e8eed1d389e5e)
[#11196](https://github.com/npm/npm/pull/11196)
Correct the `package.json` examples in the `npm update` documentation to actually be
valid JSON and not just JavaScript object literals.
([@s100](https://github.com/s100))
#### DEPENDENCY UPDATES
* [`a7b2407`](https://github.com/npm/npm/commit/a7b24074cb59a1ab17c0d8eff1498047e6a123e5)
`retry@0.9.0`: New features and interface agnostic refactoring.
([@tim-kos](https://github.com/tim-kos))
* [`220fc77`](https://github.com/npm/npm/commit/220fc7702ae3e5d601dfefd3e95c14e9b32327de)
`request@2.69.0`:
A bunch of small bug fixes and module updates.
([@simov](https://github.com/simov))
* [`9e5c84f`](https://github.com/npm/npm/commit/9e5c84f1903748897e54f8ff099729ff744eab0f)
`which@1.2.4`:
Update `isexe` and fix bug in `pathExt`, in which files without extensions
would sometimes be preferred to files with extensions on Windows, even though
those without extensions aren't executable.
`pathExt` is a list of extensions that are considered executable (exe, cmd,
bat, com on Windows).
([@isaacs](https://github.com/isaacs))
* [`375b9c4`](https://github.com/npm/npm/commit/375b9c42fe0c6de47ac2f92527354b2ea79b7968)
`rimraf@2.5.1`: Minor doc formatting fixes.
([@isaacs](https://github.com/isaacs))
* [`ef1971e`](https://github.com/npm/npm/commit/ef1971e6270c2bc72e6392b51a8b84f52708f7e7)
`lodash.clonedeep@4.0.2`:
Misc minor code cleanup. No functional changes.
([@jdalton](https://github.com/jdalton))
### v3.6.0 (2016-01-20):
Hi all! This is a bigger release, in part 'cause we didn't have one last

9
deps/npm/doc/cli/npm-install.md vendored
View File

@ -169,9 +169,12 @@ after packing it up into a tarball (b).
<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<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`, `git+https`,
or `git+file`.
If no `<commit-ish>` is specified, then `master` is used.
If the repository makes use of submodules, those submodules will
be cloned as well.
The following git environment variables are recognized by npm and will be added
to the environment when running git:

12
deps/npm/doc/cli/npm-shrinkwrap.md vendored
View File

@ -82,16 +82,16 @@ This generates `npm-shrinkwrap.json`, which will look something like this:
{
"name": "A",
"version": "1.1.0",
"version": "0.1.0",
"dependencies": {
"B": {
"version": "1.0.1",
"from": "B@^1.0.0",
"resolved": "https://registry.npmjs.org/B/-/B-1.0.1.tgz",
"version": "0.0.1",
"from": "B@^0.0.1",
"resolved": "https://registry.npmjs.org/B/-/B-0.0.1.tgz",
"dependencies": {
"C": {
"version": "1.0.1",
"from": "org/C#v1.0.1",
"version": "0.0.1",
"from": "org/C#v0.0.1",
"resolved": "git://github.com/org/C.git#5c380ae319fc4efe9e7f2d9c78b0faa588fd99b4"
}
}

58
deps/npm/doc/cli/npm-update.md vendored
View File

@ -22,16 +22,7 @@ or local) will be updated.
As of `npm@2.6.1`, the `npm update` will only inspect top-level packages.
Prior versions of `npm` would also recursively inspect all dependencies.
To get the old behavior, use `npm --depth Infinity update`, but be warned that
simultaneous asynchronous update of all packages, including `npm` itself
and packages that `npm` depends on, often causes problems up to and including
the uninstallation of `npm` itself.
To restore a missing `npm`, use the command:
```
curl -L https://npmjs.com/install.sh | sh
```
To get the old behavior, use `npm --depth Infinity update`.
## EXAMPLES
@ -44,16 +35,17 @@ on dependencies, `dep1` (`dep2`, .. etc.). The published versions of `dep1` are
```
{
dist-tags: { latest: "1.2.2" },
versions: { "1.2.2",
"1.2.1",
"1.2.0",
"1.1.2",
"1.1.1",
"1.0.0",
"0.4.1",
"0.4.0",
"0.2.0"
"dist-tags": { "latest": "1.2.2" },
"versions": {
"1.2.2",
"1.2.1",
"1.2.0",
"1.1.2",
"1.1.1",
"1.0.0",
"0.4.1",
"0.4.0",
"0.2.0"
}
}
```
@ -63,8 +55,8 @@ on dependencies, `dep1` (`dep2`, .. etc.). The published versions of `dep1` are
If `app`'s `package.json` contains:
```
dependencies: {
dep1: "^1.1.1"
"dependencies": {
"dep1": "^1.1.1"
}
```
@ -76,8 +68,8 @@ Then `npm update` will install `dep1@1.2.2`, because `1.2.2` is `latest` and
However, if `app`'s `package.json` contains:
```
dependencies: {
dep1: "~1.1.1"
"dependencies": {
"dep1": "~1.1.1"
}
```
@ -91,8 +83,8 @@ which is `1.1.2`.
Suppose `app` has a caret dependency on a version below `1.0.0`, for example:
```
dependencies: {
dep1: "^0.2.0"
"dependencies": {
"dep1": "^0.2.0"
}
```
@ -102,8 +94,8 @@ versions which satisfy `^0.2.0`.
If the dependence were on `^0.4.0`:
```
dependencies: {
dep1: "^0.4.0"
"dependencies": {
"dep1": "^0.4.0"
}
```
@ -118,8 +110,8 @@ the minimum required dependency in `package.json`, you can use
`package.json` contains:
```
dependencies: {
dep1: "^1.1.1"
"dependencies": {
"dep1": "^1.1.1"
}
```
@ -127,8 +119,8 @@ Then `npm update --save` will install `dep1@1.2.2` (i.e., `latest`),
and `package.json` will be modified:
```
dependencies: {
dep1: "^1.2.2"
"dependencies": {
"dep1": "^1.2.2"
}
```
@ -137,7 +129,7 @@ if it installs a new package.
### Updating Globally-Installed Packages
`npm update -g` will apply the `update` action to each globally- installed
`npm update -g` will apply the `update` action to each globally installed
package that is `outdated` -- that is, has a version that is different from
`latest`.

5
deps/npm/doc/cli/npm-view.md vendored
View File

@ -67,6 +67,11 @@ was required by each matching version of yui3:
npm view yui3@'>0.5.4' dependencies.jsdom
To show the `connect` package version history, you can do
this:
npm view connect versions
## OUTPUT
If only a single string field for a single version is output, then it

12
deps/npm/doc/files/package.json.md vendored
View File

@ -113,7 +113,7 @@ expression syntax version 2.0 string](https://npmjs.com/package/spdx), like this
{ "license" : "(ISC OR GPL-3.0)" }
If you are using a license that hasn't been assigned an SPDX identifier, or if
you are using a custom license, use the following valid SPDX expression:
you are using a custom license, use a string value like this one:
{ "license" : "SEE LICENSE IN <filename>" }
@ -186,9 +186,12 @@ works just like a `.gitignore`.
Certain files are always included, regardless of settings:
* `package.json`
* `README` (and its variants)
* `CHANGELOG` (and its variants)
* `README`
* `CHANGES` / `CHANGELOG` / `HISTORY`
* `LICENSE` / `LICENCE`
* The file in the "main" field
`README`, `CHANGES` & `LICENSE` can have any case and extension.
Conversely, some files are always ignored:
@ -198,10 +201,11 @@ Conversely, some files are always ignored:
* `.hg`
* `.lock-wscript`
* `.wafpickle-N`
* `*.swp`
* `.*.swp`
* `.DS_Store`
* `._*`
* `npm-debug.log`
* `.npmrc`
## main

2
deps/npm/doc/misc/npm-config.md vendored
View File

@ -394,7 +394,7 @@ Causes npm to install the package into your local `node_modules` folder with
the same layout it uses with the global `node_modules` folder. Only your
direct dependencies will show in `node_modules` and everything they depend
on will be flattened in their `node_modules` folders. This obviously will
elminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be
eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be
preferred.
### group

2
deps/npm/html/doc/README.html vendored
View File

@ -127,5 +127,5 @@ will no doubt tell you to put the output in a gist or email.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@3.6.0</p>
<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-access.html vendored
View File

@ -84,5 +84,5 @@ with an HTTP 402 status code (logically enough), unless you use
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-access &mdash; npm@3.6.0</p>
<p id="footer">npm-access &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-adduser.html vendored
View File

@ -68,5 +68,5 @@ precedence over any global configuration.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-adduser &mdash; npm@3.6.0</p>
<p id="footer">npm-adduser &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-bin.html vendored
View File

@ -35,5 +35,5 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-bin &mdash; npm@3.6.0</p>
<p id="footer">npm-bin &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-bugs.html vendored
View File

@ -53,5 +53,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-bugs &mdash; npm@3.6.0</p>
<p id="footer">npm-bugs &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-build.html vendored
View File

@ -40,5 +40,5 @@ directly, run:</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-build &mdash; npm@3.6.0</p>
<p id="footer">npm-build &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-bundle.html vendored
View File

@ -31,5 +31,5 @@ install packages into the local space.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-bundle &mdash; npm@3.6.0</p>
<p id="footer">npm-bundle &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-cache.html vendored
View File

@ -81,5 +81,5 @@ they do not make an HTTP request to the registry.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-cache &mdash; npm@3.6.0</p>
<p id="footer">npm-cache &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-completion.html vendored
View File

@ -44,5 +44,5 @@ completions based on the arguments.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-completion &mdash; npm@3.6.0</p>
<p id="footer">npm-completion &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-config.html vendored
View File

@ -65,5 +65,5 @@ global config.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-config &mdash; npm@3.6.0</p>
<p id="footer">npm-config &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-dedupe.html vendored
View File

@ -59,5 +59,5 @@ result in new modules being installed.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-dedupe &mdash; npm@3.6.0</p>
<p id="footer">npm-dedupe &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-deprecate.html vendored
View File

@ -38,5 +38,5 @@ something like this:</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-deprecate &mdash; npm@3.6.0</p>
<p id="footer">npm-deprecate &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-dist-tag.html vendored
View File

@ -85,5 +85,5 @@ begin with a number or the letter <code>v</code>.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-dist-tag &mdash; npm@3.6.0</p>
<p id="footer">npm-dist-tag &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-docs.html vendored
View File

@ -56,5 +56,5 @@ the current folder and use the <code>name</code> property.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-docs &mdash; npm@3.6.0</p>
<p id="footer">npm-docs &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-edit.html vendored
View File

@ -49,5 +49,5 @@ or <code>&quot;notepad&quot;</code> on Windows.</li>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-edit &mdash; npm@3.6.0</p>
<p id="footer">npm-edit &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-explore.html vendored
View File

@ -49,5 +49,5 @@ Windows</li>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-explore &mdash; npm@3.6.0</p>
<p id="footer">npm-explore &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-help-search.html vendored
View File

@ -46,5 +46,5 @@ where the terms were found in the documentation.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-help-search &mdash; npm@3.6.0</p>
<p id="footer">npm-help-search &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-help.html vendored
View File

@ -51,5 +51,5 @@ matches are equivalent to specifying a topic name.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-help &mdash; npm@3.6.0</p>
<p id="footer">npm-help &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-init.html vendored
View File

@ -48,5 +48,5 @@ defaults and not prompt you for any options.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-init &mdash; npm@3.6.0</p>
<p id="footer">npm-init &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-install-test.html vendored
View File

@ -42,4 +42,4 @@ takes exactly the same arguments as <code>npm install</code>.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-install-test &mdash; npm@3.6.0</p>
<p id="footer">npm-install-test &mdash; npm@3.7.3</p>

10
deps/npm/html/doc/cli/npm-install.html vendored
View File

@ -140,9 +140,11 @@ fetch the package by name if it is not valid.
<p> Installs the package from the hosted git provider, cloning it with
<code>git</code>. First it tries via the https (git with github) and if that fails, via ssh.</p>
<pre><code> &lt;protocol&gt;://[&lt;user&gt;[:&lt;password&gt;]@]&lt;hostname&gt;[:&lt;port&gt;][:][/]&lt;path&gt;[#&lt;commit-ish&gt;]
</code></pre><p> <code>&lt;protocol&gt;</code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, or
<code>git+https</code>. If no <code>&lt;commit-ish&gt;</code> is specified, then <code>master</code> is
used.</p>
</code></pre><p> <code>&lt;protocol&gt;</code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, <code>git+https</code>,
or <code>git+file</code>.
If no <code>&lt;commit-ish&gt;</code> is specified, then <code>master</code> is used.</p>
<p> If the repository makes use of submodules, those submodules will
be cloned as well.</p>
<p> The following git environment variables are recognized by npm and will be added
to the environment when running git:</p>
<ul>
@ -305,5 +307,5 @@ affects a real use-case, it will be investigated.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-install &mdash; npm@3.6.0</p>
<p id="footer">npm-install &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-link.html vendored
View File

@ -73,5 +73,5 @@ include that scope, e.g.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-link &mdash; npm@3.6.0</p>
<p id="footer">npm-link &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-logout.html vendored
View File

@ -55,5 +55,5 @@ that registry at the same time.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-logout &mdash; npm@3.6.0</p>
<p id="footer">npm-logout &mdash; npm@3.7.3</p>

4
deps/npm/html/doc/cli/npm-ls.html vendored
View File

@ -21,7 +21,7 @@ installed, as well as their dependencies, in a tree-structure.</p>
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&#39;s source tree will show:</p>
<pre><code>npm@3.6.0 /path/to/npm
<pre><code>npm@3.7.3 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
</code></pre><p>It will print out extraneous, missing, and invalid packages.</p>
@ -104,5 +104,5 @@ project.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-ls &mdash; npm@3.6.0</p>
<p id="footer">npm-ls &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-outdated.html vendored
View File

@ -116,5 +116,5 @@ project.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-outdated &mdash; npm@3.6.0</p>
<p id="footer">npm-outdated &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-owner.html vendored
View File

@ -49,5 +49,5 @@ that is not implemented at this time.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-owner &mdash; npm@3.6.0</p>
<p id="footer">npm-owner &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-pack.html vendored
View File

@ -41,5 +41,5 @@ overwritten the second time.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-pack &mdash; npm@3.6.0</p>
<p id="footer">npm-pack &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-ping.html vendored
View File

@ -32,4 +32,4 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-ping &mdash; npm@3.6.0</p>
<p id="footer">npm-ping &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-prefix.html vendored
View File

@ -38,5 +38,5 @@ to contain a package.json file unless <code>-g</code> is also specified.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-prefix &mdash; npm@3.6.0</p>
<p id="footer">npm-prefix &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-prune.html vendored
View File

@ -40,5 +40,5 @@ negate <code>NODE_ENV</code> being set to <code>production</code>.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-prune &mdash; npm@3.6.0</p>
<p id="footer">npm-prune &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-publish.html vendored
View File

@ -72,5 +72,5 @@ it is removed with <a href="../cli/npm-unpublish.html">npm-unpublish(1)</a>.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-publish &mdash; npm@3.6.0</p>
<p id="footer">npm-publish &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-rebuild.html vendored
View File

@ -35,5 +35,5 @@ the new binary.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-rebuild &mdash; npm@3.6.0</p>
<p id="footer">npm-rebuild &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-repo.html vendored
View File

@ -41,5 +41,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-repo &mdash; npm@3.6.0</p>
<p id="footer">npm-repo &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-restart.html vendored
View File

@ -53,5 +53,5 @@ behavior will be accompanied by an increase in major version number</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-restart &mdash; npm@3.6.0</p>
<p id="footer">npm-restart &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-root.html vendored
View File

@ -35,5 +35,5 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-root &mdash; npm@3.6.0</p>
<p id="footer">npm-root &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-run-script.html vendored
View File

@ -60,5 +60,5 @@ you will be given a warning to run <code>npm install</code>, just in case you&#3
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-run-script &mdash; npm@3.6.0</p>
<p id="footer">npm-run-script &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-search.html vendored
View File

@ -49,5 +49,5 @@ fall on multiple lines.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-search &mdash; npm@3.6.0</p>
<p id="footer">npm-search &mdash; npm@3.7.3</p>

14
deps/npm/html/doc/cli/npm-shrinkwrap.html vendored
View File

@ -72,16 +72,16 @@ when B hasn&#39;t changed at all.</p>
</code></pre><p>This generates <code>npm-shrinkwrap.json</code>, which will look something like this:</p>
<pre><code>{
&quot;name&quot;: &quot;A&quot;,
&quot;version&quot;: &quot;1.1.0&quot;,
&quot;version&quot;: &quot;0.1.0&quot;,
&quot;dependencies&quot;: {
&quot;B&quot;: {
&quot;version&quot;: &quot;1.0.1&quot;,
&quot;from&quot;: &quot;B@^1.0.0&quot;,
&quot;resolved&quot;: &quot;https://registry.npmjs.org/B/-/B-1.0.1.tgz&quot;,
&quot;version&quot;: &quot;0.0.1&quot;,
&quot;from&quot;: &quot;B@^0.0.1&quot;,
&quot;resolved&quot;: &quot;https://registry.npmjs.org/B/-/B-0.0.1.tgz&quot;,
&quot;dependencies&quot;: {
&quot;C&quot;: {
&quot;version&quot;: &quot;1.0.1&quot;,
&quot;from&quot;: &quot;org/C#v1.0.1&quot;,
&quot;version&quot;: &quot;0.0.1&quot;,
&quot;from&quot;: &quot;org/C#v0.0.1&quot;,
&quot;resolved&quot;: &quot;git://github.com/org/C.git#5c380ae319fc4efe9e7f2d9c78b0faa588fd99b4&quot;
}
}
@ -169,5 +169,5 @@ contents rather than versions.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-shrinkwrap &mdash; npm@3.6.0</p>
<p id="footer">npm-shrinkwrap &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-star.html vendored
View File

@ -36,5 +36,5 @@ a vaguely positive way to show that you care.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-star &mdash; npm@3.6.0</p>
<p id="footer">npm-star &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-stars.html vendored
View File

@ -36,5 +36,5 @@ you will most certainly enjoy this command.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-stars &mdash; npm@3.6.0</p>
<p id="footer">npm-stars &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-start.html vendored
View File

@ -39,5 +39,5 @@ more details.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-start &mdash; npm@3.6.0</p>
<p id="footer">npm-start &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-stop.html vendored
View File

@ -34,5 +34,5 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-stop &mdash; npm@3.6.0</p>
<p id="footer">npm-stop &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-tag.html vendored
View File

@ -63,5 +63,5 @@ that do not begin with a number or the letter <code>v</code>.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-tag &mdash; npm@3.6.0</p>
<p id="footer">npm-tag &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-team.html vendored
View File

@ -67,4 +67,4 @@ use the <code>npm access</code> command to grant or revoke the appropriate permi
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-team &mdash; npm@3.6.0</p>
<p id="footer">npm-team &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-test.html vendored
View File

@ -37,5 +37,5 @@ true.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-test &mdash; npm@3.6.0</p>
<p id="footer">npm-test &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-uninstall.html vendored
View File

@ -60,5 +60,5 @@ npm uninstall dtrace-provider --save-optional
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-uninstall &mdash; npm@3.6.0</p>
<p id="footer">npm-uninstall &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-unpublish.html vendored
View File

@ -47,5 +47,5 @@ package again, a new version number must be used.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-unpublish &mdash; npm@3.6.0</p>
<p id="footer">npm-unpublish &mdash; npm@3.7.3</p>

58
deps/npm/html/doc/cli/npm-update.html vendored
View File

@ -24,42 +24,38 @@ packages.</p>
or local) will be updated.</p>
<p>As of <code>npm@2.6.1</code>, the <code>npm update</code> will only inspect top-level packages.
Prior versions of <code>npm</code> would also recursively inspect all dependencies.
To get the old behavior, use <code>npm --depth Infinity update</code>, but be warned that
simultaneous asynchronous update of all packages, including <code>npm</code> itself
and packages that <code>npm</code> depends on, often causes problems up to and including
the uninstallation of <code>npm</code> itself.</p>
<p>To restore a missing <code>npm</code>, use the command:</p>
<pre><code>curl -L https://npmjs.com/install.sh | sh
</code></pre><h2 id="examples">EXAMPLES</h2>
To get the old behavior, use <code>npm --depth Infinity update</code>.</p>
<h2 id="examples">EXAMPLES</h2>
<p>IMPORTANT VERSION NOTE: these examples assume <code>npm@2.6.1</code> or later. For
older versions of <code>npm</code>, you must specify <code>--depth 0</code> to get the behavior
described below.</p>
<p>For the examples below, assume that the current package is <code>app</code> and it depends
on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published versions of <code>dep1</code> are:</p>
<pre><code>{
dist-tags: { latest: &quot;1.2.2&quot; },
versions: { &quot;1.2.2&quot;,
&quot;1.2.1&quot;,
&quot;1.2.0&quot;,
&quot;1.1.2&quot;,
&quot;1.1.1&quot;,
&quot;1.0.0&quot;,
&quot;0.4.1&quot;,
&quot;0.4.0&quot;,
&quot;0.2.0&quot;
&quot;dist-tags&quot;: { &quot;latest&quot;: &quot;1.2.2&quot; },
&quot;versions&quot;: {
&quot;1.2.2&quot;,
&quot;1.2.1&quot;,
&quot;1.2.0&quot;,
&quot;1.1.2&quot;,
&quot;1.1.1&quot;,
&quot;1.0.0&quot;,
&quot;0.4.1&quot;,
&quot;0.4.0&quot;,
&quot;0.2.0&quot;
}
}
</code></pre><h3 id="caret-dependencies">Caret Dependencies</h3>
<p>If <code>app</code>&#39;s <code>package.json</code> contains:</p>
<pre><code>dependencies: {
dep1: &quot;^1.1.1&quot;
<pre><code>&quot;dependencies&quot;: {
&quot;dep1&quot;: &quot;^1.1.1&quot;
}
</code></pre><p>Then <code>npm update</code> will install <code>dep1@1.2.2</code>, because <code>1.2.2</code> is <code>latest</code> and
<code>1.2.2</code> satisfies <code>^1.1.1</code>.</p>
<h3 id="tilde-dependencies">Tilde Dependencies</h3>
<p>However, if <code>app</code>&#39;s <code>package.json</code> contains:</p>
<pre><code>dependencies: {
dep1: &quot;~1.1.1&quot;
<pre><code>&quot;dependencies&quot;: {
&quot;dep1&quot;: &quot;~1.1.1&quot;
}
</code></pre><p>In this case, running <code>npm update</code> will install <code>dep1@1.1.2</code>. Even though the <code>latest</code>
tag points to <code>1.2.2</code>, this version does not satisfy <code>~1.1.1</code>, which is equivalent
@ -67,14 +63,14 @@ to <code>&gt;=1.1.1 &lt;1.2.0</code>. So the highest-sorting version that satis
which is <code>1.1.2</code>.</p>
<h3 id="caret-dependencies-below-1-0-0">Caret Dependencies below 1.0.0</h3>
<p>Suppose <code>app</code> has a caret dependency on a version below <code>1.0.0</code>, for example:</p>
<pre><code>dependencies: {
dep1: &quot;^0.2.0&quot;
<pre><code>&quot;dependencies&quot;: {
&quot;dep1&quot;: &quot;^0.2.0&quot;
}
</code></pre><p><code>npm update</code> will install <code>dep1@0.2.0</code>, because there are no other
versions which satisfy <code>^0.2.0</code>.</p>
<p>If the dependence were on <code>^0.4.0</code>:</p>
<pre><code>dependencies: {
dep1: &quot;^0.4.0&quot;
<pre><code>&quot;dependencies&quot;: {
&quot;dep1&quot;: &quot;^0.4.0&quot;
}
</code></pre><p>Then <code>npm update</code> will install <code>dep1@0.4.1</code>, because that is the highest-sorting
version that satisfies <code>^0.4.0</code> (<code>&gt;= 0.4.0 &lt;0.5.0</code>)</p>
@ -83,18 +79,18 @@ version that satisfies <code>^0.4.0</code> (<code>&gt;= 0.4.0 &lt;0.5.0</code>)<
the minimum required dependency in <code>package.json</code>, you can use
<code>npm update -S</code> or <code>npm update --save</code>. For example if
<code>package.json</code> contains:</p>
<pre><code>dependencies: {
dep1: &quot;^1.1.1&quot;
<pre><code>&quot;dependencies&quot;: {
&quot;dep1&quot;: &quot;^1.1.1&quot;
}
</code></pre><p>Then <code>npm update --save</code> will install <code>dep1@1.2.2</code> (i.e., <code>latest</code>),
and <code>package.json</code> will be modified:</p>
<pre><code>dependencies: {
dep1: &quot;^1.2.2&quot;
<pre><code>&quot;dependencies&quot;: {
&quot;dep1&quot;: &quot;^1.2.2&quot;
}
</code></pre><p>Note that <code>npm</code> will only write an updated version to <code>package.json</code>
if it installs a new package.</p>
<h3 id="updating-globally-installed-packages">Updating Globally-Installed Packages</h3>
<p><code>npm update -g</code> will apply the <code>update</code> action to each globally- installed
<p><code>npm update -g</code> will apply the <code>update</code> action to each globally installed
package that is <code>outdated</code> -- that is, has a version that is different from
<code>latest</code>.</p>
<p>NOTE: If a package has been upgraded to a version newer than <code>latest</code>, it will
@ -120,5 +116,5 @@ be <em>downgraded</em>.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-update &mdash; npm@3.6.0</p>
<p id="footer">npm-update &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-version.html vendored
View File

@ -100,5 +100,5 @@ and tag up to the server, and deletes the <code>build/temp</code> directory.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-version &mdash; npm@3.6.0</p>
<p id="footer">npm-version &mdash; npm@3.7.3</p>

5
deps/npm/html/doc/cli/npm-view.html vendored
View File

@ -53,6 +53,9 @@ the shortened string format. (See <code><a href="../files/package.json.html">pa
matching version of the package. This will show which version of jsdom
was required by each matching version of yui3:</p>
<pre><code>npm view yui3@&#39;&gt;0.5.4&#39; dependencies.jsdom
</code></pre><p>To show the <code>connect</code> package version history, you can do
this:</p>
<pre><code>npm view connect versions
</code></pre><h2 id="output">OUTPUT</h2>
<p>If only a single string field for a single version is output, then it
will not be colorized or quoted, so as to enable piping the output to
@ -83,5 +86,5 @@ the field name.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-view &mdash; npm@3.6.0</p>
<p id="footer">npm-view &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/cli/npm-whoami.html vendored
View File

@ -33,5 +33,5 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-whoami &mdash; npm@3.6.0</p>
<p id="footer">npm-whoami &mdash; npm@3.7.3</p>

10
deps/npm/html/doc/cli/npm.html vendored
View File

@ -13,7 +13,7 @@
<h2 id="synopsis">SYNOPSIS</h2>
<pre><code>npm &lt;command&gt; [args]
</code></pre><h2 id="version">VERSION</h2>
<p>3.6.0</p>
<p>3.7.3</p>
<h2 id="description">DESCRIPTION</h2>
<p>npm is the package manager for the Node JavaScript platform. It puts
modules in place so that node can find them, and manages dependency
@ -110,7 +110,7 @@ easily by doing <code>npm view npm contributors</code>.</p>
the issues list or ask on the mailing list.</p>
<ul>
<li><a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li>
<li><a href="&#x6d;&#x61;&#105;&#108;&#x74;&#x6f;&#x3a;&#110;&#x70;&#109;&#x2d;&#64;&#x67;&#x6f;&#x6f;&#x67;&#108;&#x65;&#x67;&#x72;&#x6f;&#117;&#112;&#115;&#x2e;&#99;&#111;&#x6d;">&#110;&#x70;&#109;&#x2d;&#64;&#x67;&#x6f;&#x6f;&#x67;&#108;&#x65;&#x67;&#x72;&#x6f;&#117;&#112;&#115;&#x2e;&#99;&#111;&#x6d;</a></li>
<li><a href="&#x6d;&#97;&#x69;&#108;&#116;&#111;&#58;&#110;&#112;&#x6d;&#x2d;&#x40;&#103;&#111;&#111;&#103;&#108;&#101;&#x67;&#114;&#x6f;&#117;&#112;&#x73;&#x2e;&#99;&#x6f;&#109;">&#110;&#112;&#x6d;&#x2d;&#x40;&#103;&#111;&#111;&#103;&#108;&#101;&#x67;&#114;&#x6f;&#117;&#112;&#x73;&#x2e;&#99;&#x6f;&#109;</a></li>
</ul>
<h2 id="bugs">BUGS</h2>
<p>When you find issues, please report them:</p>
@ -118,7 +118,7 @@ the issues list or ask on the mailing list.</p>
<li>web:
<a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li>
<li>email:
<a href="&#x6d;&#x61;&#x69;&#108;&#x74;&#x6f;&#58;&#110;&#x70;&#x6d;&#x2d;&#x40;&#x67;&#111;&#x6f;&#x67;&#108;&#x65;&#x67;&#114;&#x6f;&#x75;&#x70;&#x73;&#46;&#x63;&#111;&#109;">&#110;&#x70;&#x6d;&#x2d;&#x40;&#x67;&#111;&#x6f;&#x67;&#108;&#x65;&#x67;&#114;&#x6f;&#x75;&#x70;&#x73;&#46;&#x63;&#111;&#109;</a></li>
<a href="&#x6d;&#x61;&#x69;&#x6c;&#x74;&#x6f;&#58;&#110;&#112;&#109;&#45;&#x40;&#x67;&#x6f;&#111;&#x67;&#x6c;&#x65;&#103;&#x72;&#111;&#117;&#112;&#115;&#x2e;&#99;&#111;&#109;">&#110;&#112;&#109;&#45;&#x40;&#x67;&#x6f;&#111;&#x67;&#x6c;&#x65;&#103;&#x72;&#111;&#117;&#112;&#115;&#x2e;&#99;&#111;&#109;</a></li>
</ul>
<p>Be sure to include <em>all</em> of the output from the npm command that didn&#39;t work
as expected. The <code>npm-debug.log</code> file is also helpful to provide.</p>
@ -128,7 +128,7 @@ will no doubt tell you to put the output in a gist or email.</p>
<p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> ::
<a href="https://github.com/isaacs/">isaacs</a> ::
<a href="http://twitter.com/izs">@izs</a> ::
<a href="&#109;&#97;&#105;&#108;&#116;&#111;&#x3a;&#x69;&#x40;&#x69;&#122;&#115;&#46;&#109;&#101;">&#x69;&#x40;&#x69;&#122;&#115;&#46;&#109;&#101;</a></p>
<a href="&#109;&#x61;&#105;&#108;&#x74;&#111;&#x3a;&#105;&#64;&#105;&#122;&#x73;&#46;&#x6d;&#101;">&#105;&#64;&#105;&#122;&#x73;&#46;&#x6d;&#101;</a></p>
<h2 id="see-also">SEE ALSO</h2>
<ul>
<li><a href="../cli/npm-help.html">npm-help(1)</a></li>
@ -153,5 +153,5 @@ will no doubt tell you to put the output in a gist or email.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm &mdash; npm@3.6.0</p>
<p id="footer">npm &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/files/npm-folders.html vendored
View File

@ -183,5 +183,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-folders &mdash; npm@3.6.0</p>
<p id="footer">npm-folders &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/files/npm-global.html vendored
View File

@ -183,5 +183,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-folders &mdash; npm@3.6.0</p>
<p id="footer">npm-folders &mdash; npm@3.7.3</p>

13
deps/npm/html/doc/files/npm-json.html vendored
View File

@ -90,7 +90,7 @@ Ideally you should pick one that is
expression syntax version 2.0 string</a>, like this:</p>
<pre><code>{ &quot;license&quot; : &quot;(ISC OR GPL-3.0)&quot; }
</code></pre><p>If you are using a license that hasn&#39;t been assigned an SPDX identifier, or if
you are using a custom license, use the following valid SPDX expression:</p>
you are using a custom license, use a string value like this one:</p>
<pre><code>{ &quot;license&quot; : &quot;SEE LICENSE IN &lt;filename&gt;&quot; }
</code></pre><p>Then include a file named <code>&lt;filename&gt;</code> at the top level of the package.</p>
<p>Some old packages used license objects or a &quot;licenses&quot; property containing an
@ -143,10 +143,12 @@ works just like a <code>.gitignore</code>.</p>
<p>Certain files are always included, regardless of settings:</p>
<ul>
<li><code>package.json</code></li>
<li><code><a href="../../doc/README.html">README</a></code> (and its variants)</li>
<li><code>CHANGELOG</code> (and its variants)</li>
<li><code><a href="../../doc/README.html">README</a></code></li>
<li><code>CHANGES</code> / <code>CHANGELOG</code> / <code>HISTORY</code></li>
<li><code>LICENSE</code> / <code>LICENCE</code></li>
<li>The file in the &quot;main&quot; field</li>
</ul>
<p><code><a href="../../doc/README.html">README</a></code>, <code>CHANGES</code> &amp; <code>LICENSE</code> can have any case and extension.</p>
<p>Conversely, some files are always ignored:</p>
<ul>
<li><code>.git</code></li>
@ -155,10 +157,11 @@ works just like a <code>.gitignore</code>.</p>
<li><code>.hg</code></li>
<li><code>.lock-wscript</code></li>
<li><code>.wafpickle-N</code></li>
<li><code>*.swp</code></li>
<li><code>.*.swp</code></li>
<li><code>.DS_Store</code></li>
<li><code>._*</code></li>
<li><code>npm-debug.log</code></li>
<li><code>.npmrc</code></li>
</ul>
<h2 id="main">main</h2>
<p>The main field is a module ID that is the primary entry point to your program.
@ -559,5 +562,5 @@ ignored.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">package.json &mdash; npm@3.6.0</p>
<p id="footer">package.json &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/files/npmrc.html vendored
View File

@ -83,5 +83,5 @@ manner.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npmrc &mdash; npm@3.6.0</p>
<p id="footer">npmrc &mdash; npm@3.7.3</p>

13
deps/npm/html/doc/files/package.json.html vendored
View File

@ -90,7 +90,7 @@ Ideally you should pick one that is
expression syntax version 2.0 string</a>, like this:</p>
<pre><code>{ &quot;license&quot; : &quot;(ISC OR GPL-3.0)&quot; }
</code></pre><p>If you are using a license that hasn&#39;t been assigned an SPDX identifier, or if
you are using a custom license, use the following valid SPDX expression:</p>
you are using a custom license, use a string value like this one:</p>
<pre><code>{ &quot;license&quot; : &quot;SEE LICENSE IN &lt;filename&gt;&quot; }
</code></pre><p>Then include a file named <code>&lt;filename&gt;</code> at the top level of the package.</p>
<p>Some old packages used license objects or a &quot;licenses&quot; property containing an
@ -143,10 +143,12 @@ works just like a <code>.gitignore</code>.</p>
<p>Certain files are always included, regardless of settings:</p>
<ul>
<li><code>package.json</code></li>
<li><code><a href="../../doc/README.html">README</a></code> (and its variants)</li>
<li><code>CHANGELOG</code> (and its variants)</li>
<li><code><a href="../../doc/README.html">README</a></code></li>
<li><code>CHANGES</code> / <code>CHANGELOG</code> / <code>HISTORY</code></li>
<li><code>LICENSE</code> / <code>LICENCE</code></li>
<li>The file in the &quot;main&quot; field</li>
</ul>
<p><code><a href="../../doc/README.html">README</a></code>, <code>CHANGES</code> &amp; <code>LICENSE</code> can have any case and extension.</p>
<p>Conversely, some files are always ignored:</p>
<ul>
<li><code>.git</code></li>
@ -155,10 +157,11 @@ works just like a <code>.gitignore</code>.</p>
<li><code>.hg</code></li>
<li><code>.lock-wscript</code></li>
<li><code>.wafpickle-N</code></li>
<li><code>*.swp</code></li>
<li><code>.*.swp</code></li>
<li><code>.DS_Store</code></li>
<li><code>._*</code></li>
<li><code>npm-debug.log</code></li>
<li><code>.npmrc</code></li>
</ul>
<h2 id="main">main</h2>
<p>The main field is a module ID that is the primary entry point to your program.
@ -559,5 +562,5 @@ ignored.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">package.json &mdash; npm@3.6.0</p>
<p id="footer">package.json &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/index.html vendored
View File

@ -162,5 +162,5 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-index &mdash; npm@3.6.0</p>
<p id="footer">npm-index &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/npm-coding-style.html vendored
View File

@ -154,5 +154,5 @@ set to anything.&quot;</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-coding-style &mdash; npm@3.6.0</p>
<p id="footer">npm-coding-style &mdash; npm@3.7.3</p>

4
deps/npm/html/doc/misc/npm-config.html vendored
View File

@ -341,7 +341,7 @@ current working directory.</li>
the same layout it uses with the global <code>node_modules</code> folder. Only your
direct dependencies will show in <code>node_modules</code> and everything they depend
on will be flattened in their <code>node_modules</code> folders. This obviously will
elminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be
eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be
preferred.</p>
<h3 id="group">group</h3>
<ul>
@ -849,5 +849,5 @@ exit successfully.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-config &mdash; npm@3.6.0</p>
<p id="footer">npm-config &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/npm-developers.html vendored
View File

@ -195,5 +195,5 @@ from a fresh checkout.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-developers &mdash; npm@3.6.0</p>
<p id="footer">npm-developers &mdash; npm@3.7.3</p>

8
deps/npm/html/doc/misc/npm-disputes.html vendored
View File

@ -13,7 +13,7 @@
<h2 id="synopsis">SYNOPSIS</h2>
<ol>
<li>Get the author email with <code>npm owner ls &lt;pkgname&gt;</code></li>
<li>Email the author, CC <a href="&#109;&#97;&#105;&#x6c;&#x74;&#x6f;&#x3a;&#115;&#117;&#x70;&#112;&#x6f;&#x72;&#x74;&#x40;&#x6e;&#x70;&#109;&#x6a;&#115;&#46;&#99;&#x6f;&#109;">&#115;&#117;&#x70;&#112;&#x6f;&#x72;&#x74;&#x40;&#x6e;&#x70;&#109;&#x6a;&#115;&#46;&#99;&#x6f;&#109;</a></li>
<li>Email the author, CC <a href="&#109;&#x61;&#x69;&#x6c;&#116;&#111;&#x3a;&#x73;&#117;&#112;&#x70;&#x6f;&#114;&#x74;&#64;&#110;&#112;&#x6d;&#106;&#115;&#x2e;&#99;&#111;&#x6d;">&#x73;&#117;&#112;&#x70;&#x6f;&#114;&#x74;&#64;&#110;&#112;&#x6d;&#106;&#115;&#x2e;&#99;&#111;&#x6d;</a></li>
<li>After a few weeks, if there&#39;s no resolution, we&#39;ll sort it out.</li>
</ol>
<p>Don&#39;t squat on package names. Publish code or move out of the way.</p>
@ -51,12 +51,12 @@ Joe&#39;s appropriate course of action in each case is the same.</p>
owner (Bob).</li>
<li>Joe emails Bob, explaining the situation <strong>as respectfully as
possible</strong>, and what he would like to do with the module name. He
adds the npm support staff <a href="&#109;&#97;&#x69;&#x6c;&#116;&#111;&#x3a;&#x73;&#117;&#x70;&#x70;&#111;&#x72;&#116;&#x40;&#x6e;&#x70;&#109;&#x6a;&#115;&#46;&#99;&#x6f;&#x6d;">&#x73;&#117;&#x70;&#x70;&#111;&#x72;&#116;&#x40;&#x6e;&#x70;&#109;&#x6a;&#115;&#46;&#99;&#x6f;&#x6d;</a> to the CC list of
adds the npm support staff <a href="&#109;&#97;&#105;&#x6c;&#x74;&#x6f;&#58;&#115;&#x75;&#x70;&#112;&#111;&#x72;&#x74;&#64;&#110;&#112;&#109;&#x6a;&#115;&#46;&#99;&#x6f;&#109;">&#115;&#x75;&#x70;&#112;&#111;&#x72;&#x74;&#64;&#110;&#112;&#109;&#x6a;&#115;&#46;&#99;&#x6f;&#109;</a> to the CC list of
the email. Mention in the email that Bob can run <code>npm owner add
joe foo</code> to add Joe as an owner of the <code>foo</code> package.</li>
<li>After a reasonable amount of time, if Bob has not responded, or if
Bob and Joe can&#39;t come to any sort of resolution, email support
<a href="&#x6d;&#x61;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#115;&#117;&#112;&#x70;&#x6f;&#114;&#116;&#x40;&#110;&#x70;&#x6d;&#x6a;&#x73;&#46;&#x63;&#111;&#x6d;">&#115;&#117;&#112;&#x70;&#x6f;&#114;&#116;&#x40;&#110;&#x70;&#x6d;&#x6a;&#x73;&#46;&#x63;&#111;&#x6d;</a> and we&#39;ll sort it out. (&quot;Reasonable&quot; is
<a href="&#x6d;&#97;&#105;&#x6c;&#x74;&#x6f;&#58;&#115;&#x75;&#x70;&#112;&#x6f;&#x72;&#x74;&#64;&#x6e;&#112;&#109;&#x6a;&#x73;&#46;&#x63;&#x6f;&#109;">&#115;&#x75;&#x70;&#112;&#x6f;&#x72;&#x74;&#64;&#x6e;&#112;&#109;&#x6a;&#x73;&#46;&#x63;&#x6f;&#109;</a> and we&#39;ll sort it out. (&quot;Reasonable&quot; is
usually at least 4 weeks, but extra time is allowed around common
holidays.)</li>
</ol>
@ -112,5 +112,5 @@ things into it.</li>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-disputes &mdash; npm@3.6.0</p>
<p id="footer">npm-disputes &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/npm-index.html vendored
View File

@ -162,4 +162,4 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-index &mdash; npm@3.6.0</p>
<p id="footer">npm-index &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/npm-orgs.html vendored
View File

@ -86,4 +86,4 @@
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-orgs &mdash; npm@3.6.0</p>
<p id="footer">npm-orgs &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/npm-registry.html vendored
View File

@ -70,5 +70,5 @@ effectively implement the entire CouchDB API anyway.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-registry &mdash; npm@3.6.0</p>
<p id="footer">npm-registry &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/npm-scope.html vendored
View File

@ -91,5 +91,5 @@ that registry instead.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-scope &mdash; npm@3.6.0</p>
<p id="footer">npm-scope &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/npm-scripts.html vendored
View File

@ -207,5 +207,5 @@ scripts is for compilation which must be done on the target architecture.</li>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">npm-scripts &mdash; npm@3.6.0</p>
<p id="footer">npm-scripts &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/removing-npm.html vendored
View File

@ -57,5 +57,5 @@ modules. To track those down, you can do the following:</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">removing-npm &mdash; npm@3.6.0</p>
<p id="footer">removing-npm &mdash; npm@3.7.3</p>

2
deps/npm/html/doc/misc/semver.html vendored
View File

@ -302,5 +302,5 @@ range, use the <code>satisfies(version, range)</code> function.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
<p id="footer">semver &mdash; npm@3.6.0</p>
<p id="footer">semver &mdash; npm@3.7.3</p>

18
deps/npm/lib/cache/add-remote-git.js vendored
View File

@ -346,6 +346,24 @@ function checkoutTreeish (from, resolvedURL, resolvedTreeish, tmpdir, cb) {
}
log.verbose('checkoutTreeish', from, 'checkout', stdout)
updateSubmodules(from, resolvedURL, tmpdir, cb)
}
)
}
function updateSubmodules (from, resolvedURL, tmpdir, cb) {
var args = ['submodule', '-q', 'update', '--init', '--recursive']
git.whichAndExec(
args,
{ cwd: tmpdir, env: gitEnv() },
function (er, stdout, stderr) {
stdout = (stdout + '\n' + stderr).trim()
if (er) {
log.error('git ' + args.join(' ') + ':', stderr)
return cb(er)
}
log.verbose('updateSubmodules', from, 'submodule update', stdout)
// convince addLocal that the checkout is a local dependency
realizePackageSpecifier(tmpdir, function (er, spec) {
if (er) {

7
deps/npm/lib/install/deps.js vendored
View File

@ -231,10 +231,9 @@ exports.removeDeps = function (args, tree, saveToDependencies, log, next) {
var pkgName = moduleName(pkg)
if (saveToDependencies) {
var toRemove = tree.children.filter(moduleNameMatches(pkgName))
replaceModule(tree, 'removed', toRemove[0])
toRemove.forEach(function (parent) {
parent.save = saveToDependencies
})
var pkgToRemove = toRemove[0] || createChild({package: {name: pkgName}})
replaceModule(tree, 'removed', pkgToRemove)
pkgToRemove.save = saveToDependencies
}
tree.children = tree.children.filter(noModuleNameMatches(pkgName))
})

4
deps/npm/lib/install/save.js vendored
View File

@ -180,8 +180,10 @@ function computeVersionSpec (child) {
pathname: relativePath
})
}
} else {
} else if (requested.type === 'hosted') {
return requested.spec
} else {
return requested.rawSpec
}
}

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

@ -120,7 +120,6 @@ function filterByEnv (data) {
var devDependencies = data.devDependencies || []
Object.keys(data.dependencies).forEach(function (name) {
var keys = Object.keys(devDependencies)
if (production && !dev && keys.indexOf(name) !== -1) return
if (dev && !production && keys.indexOf(name) === -1) return
if (!dev && keys.indexOf(name) !== -1 && data.dependencies[name].missing) return
dependencies[name] = data.dependencies[name]

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

@ -287,7 +287,12 @@
loadCb(loadErr = er)
onload = onload && npm.config.get('onload-script')
if (onload) {
require(onload)
try {
require(onload)
} catch (err) {
log.warn('onload-script', 'failed to require onload script', onload)
log.warn('onload-script', err)
}
onload = false
}
}

6
deps/npm/lib/utils/deep-sort-object.js vendored
View File

@ -3,7 +3,11 @@ var sortedObject = require('sorted-object')
module.exports = function deepSortObject (obj, sortBy) {
if (obj == null || typeof obj !== 'object') return obj
if (obj instanceof Array) return obj.sort(sortBy)
if (obj instanceof Array) {
return obj.map(function (x) {
return deepSortObject(x, sortBy)
})
}
obj = sortedObject(obj)
Object.keys(obj).forEach(function (key) {
obj[key] = deepSortObject(obj[key], sortBy)

11
deps/npm/lib/utils/lifecycle.js vendored
View File

@ -1,6 +1,7 @@
exports = module.exports = lifecycle
exports.cmd = cmd
exports.makeEnv = makeEnv
exports._incorrectWorkingDirectory = _incorrectWorkingDirectory
var log = require('npmlog')
var spawn = require('./spawn')
@ -52,8 +53,7 @@ function lifecycle (pkg, stage, wd, unsafe, failOk, cb) {
unsafe = unsafe || npm.config.get('unsafe-perm')
if ((wd.indexOf(npm.dir) !== 0 ||
wd.indexOf(pkg.name) !== wd.length - pkg.name.length) &&
if ((wd.indexOf(npm.dir) !== 0 || _incorrectWorkingDirectory(wd, pkg)) &&
!unsafe && pkg.scripts[stage]) {
log.warn('lifecycle', logid(pkg, stage), 'cannot run in wd',
'%s %s (wd=%s)', pkg._id, pkg.scripts[stage], wd
@ -75,6 +75,10 @@ function lifecycle (pkg, stage, wd, unsafe, failOk, cb) {
})
}
function _incorrectWorkingDirectory (wd, pkg) {
return wd.lastIndexOf(pkg.name) !== wd.length - pkg.name.length
}
function lifecycle_ (pkg, stage, wd, env, unsafe, failOk, cb) {
var pathArr = []
var p = wd.split('node_modules')
@ -90,6 +94,9 @@ function lifecycle_ (pkg, stage, wd, env, unsafe, failOk, cb) {
// the bundled one will be used for installing things.
pathArr.unshift(path.join(__dirname, '..', '..', 'bin', 'node-gyp-bin'))
// prefer current node interpreter in child scripts
pathArr.push(path.dirname(process.execPath))
if (env[PATH]) pathArr.push(env[PATH])
env[PATH] = pathArr.join(process.platform === 'win32' ? ';' : ':')

2
deps/npm/man/man1/npm-README.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM" "1" "January 2016" "" ""
.TH "NPM" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm\fR \- a JavaScript package manager
.P

2
deps/npm/man/man1/npm-access.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-ACCESS" "1" "January 2016" "" ""
.TH "NPM\-ACCESS" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-access\fR \- Set access level on published packages
.SH SYNOPSIS

2
deps/npm/man/man1/npm-adduser.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-ADDUSER" "1" "January 2016" "" ""
.TH "NPM\-ADDUSER" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-adduser\fR \- Add a registry user account
.SH SYNOPSIS

2
deps/npm/man/man1/npm-bin.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-BIN" "1" "January 2016" "" ""
.TH "NPM\-BIN" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-bin\fR \- Display npm bin folder
.SH SYNOPSIS

2
deps/npm/man/man1/npm-bugs.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-BUGS" "1" "January 2016" "" ""
.TH "NPM\-BUGS" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-bugs\fR \- Bugs for a package in a web browser maybe
.SH SYNOPSIS

2
deps/npm/man/man1/npm-build.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-BUILD" "1" "January 2016" "" ""
.TH "NPM\-BUILD" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-build\fR \- Build a package
.SH SYNOPSIS

2
deps/npm/man/man1/npm-bundle.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-BUNDLE" "1" "January 2016" "" ""
.TH "NPM\-BUNDLE" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-bundle\fR \- REMOVED
.SH DESCRIPTION

2
deps/npm/man/man1/npm-cache.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-CACHE" "1" "January 2016" "" ""
.TH "NPM\-CACHE" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-cache\fR \- Manipulates packages cache
.SH SYNOPSIS

2
deps/npm/man/man1/npm-completion.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-COMPLETION" "1" "January 2016" "" ""
.TH "NPM\-COMPLETION" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-completion\fR \- Tab Completion for npm
.SH SYNOPSIS

2
deps/npm/man/man1/npm-config.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-CONFIG" "1" "January 2016" "" ""
.TH "NPM\-CONFIG" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-config\fR \- Manage the npm configuration files
.SH SYNOPSIS

2
deps/npm/man/man1/npm-dedupe.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-DEDUPE" "1" "January 2016" "" ""
.TH "NPM\-DEDUPE" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-dedupe\fR \- Reduce duplication
.SH SYNOPSIS

2
deps/npm/man/man1/npm-deprecate.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-DEPRECATE" "1" "January 2016" "" ""
.TH "NPM\-DEPRECATE" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-deprecate\fR \- Deprecate a version of a package
.SH SYNOPSIS

2
deps/npm/man/man1/npm-dist-tag.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-DIST\-TAG" "1" "January 2016" "" ""
.TH "NPM\-DIST\-TAG" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-dist-tag\fR \- Modify package distribution tags
.SH SYNOPSIS

2
deps/npm/man/man1/npm-docs.1 vendored
View File

@ -1,4 +1,4 @@
.TH "NPM\-DOCS" "1" "January 2016" "" ""
.TH "NPM\-DOCS" "1" "February 2016" "" ""
.SH "NAME"
\fBnpm-docs\fR \- Docs for a package in a web browser maybe
.SH SYNOPSIS

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