deps: upgrade npm to 3.8.3
PR-URL: https://github.com/npm/node/pull/6 Reviewed-By: Evan Lucas <evanlucas@me.com>
This commit is contained in:
Forrest L Norvell
Myles Borins
parent
39de601e1c
commit
0928584444
2
deps/npm/.mailmap
vendored
2
deps/npm/.mailmap
vendored
@ -23,6 +23,7 @@ Forbes Lindesay <forbes@lindesay.co.uk>
|
||||
Forrest L Norvell <ogd@aoaioxxysz.net> <forrest@npmjs.com>
|
||||
Gabriel Barros <descartavel1@gmail.com>
|
||||
Geoff Flarity <geoff.flarity@gmail.com> <gflarity@raptvm-x02.(none)>
|
||||
Ifeanyi Oraelosi <ifeanyioraelosi@gmail.com>
|
||||
Isaac Z. Schlueter <i@izs.me> <i@foohack.com>
|
||||
Isaac Z. Schlueter <i@izs.me> isaacs <i@izs.me>
|
||||
Jake Verbaten <raynos2@gmail.com>
|
||||
@ -59,3 +60,4 @@ Will Elwood <w.elwood08@gmail.com>
|
||||
Wout Mertens <Wout.Mertens@gmail.com>
|
||||
Yeonghoon Park <sola92@gmail.com>
|
||||
Zeke Sikelianos <zeke@sikelianos.com>
|
||||
Zoujie Wzj <zoujie.wzj@alibaba-inc.com>
|
||||
|
||||
1
deps/npm/.npmignore
vendored
1
deps/npm/.npmignore
vendored
@ -7,6 +7,7 @@ npm-debug.log
|
||||
/test/packages/npm-test-depends-on-spark/which-spark.log
|
||||
/test/packages/test-package/random-data.txt
|
||||
/test/root
|
||||
/test/npm_cache
|
||||
node_modules/marked
|
||||
node_modules/ronn
|
||||
node_modules/tap
|
||||
|
||||
2
deps/npm/.travis.yml
vendored
2
deps/npm/.travis.yml
vendored
@ -13,6 +13,6 @@ before_install:
|
||||
- "node . install -g ."
|
||||
- "mkdir -p /var/run/couchdb"
|
||||
sudo: false
|
||||
script: "npm run-script test-all"
|
||||
script: "npm test"
|
||||
notifications:
|
||||
slack: npm-inc:kRqQjto7YbINqHPb1X6nS3g8
|
||||
|
||||
18
deps/npm/AUTHORS
vendored
18
deps/npm/AUTHORS
vendored
@ -364,3 +364,21 @@ Jan Schär <jscissr@gmail.com>
|
||||
Xcat Liu <xcatliu@gmail.com>
|
||||
harryh <Aourin@users.noreply.github.com>
|
||||
Prayag Verma <prayag.verma@gmail.com>
|
||||
Neil Kistner <neil.kistner@gmail.com>
|
||||
Zoujie Wzj <zoujie.wzj@alibaba-inc.com>
|
||||
Ryan Hendrickson <ryan.hendrickson@alum.mit.edu>
|
||||
Arturo Coronel <aoitsu3@gmail.com>
|
||||
Hutson Betts <hbetts@factset.com>
|
||||
Lewis Cowper <lewis.cowper@googlemail.com>
|
||||
Adam Byrne <misterbyrne@gmail.com>
|
||||
Ifeanyi Oraelosi <ifeanyioraelosi@gmail.com>
|
||||
Robert Ludwig <rob.ludwig@rideamigos.com>
|
||||
Chris Warren <chris@ixalon.net>
|
||||
Scott Plumlee <scott@plumlee.org>
|
||||
Daniel Pedersen <daniel@scandinav.se>
|
||||
rhgb <kaiserdaemon@gmail.com>
|
||||
doug.wade <doug.wade@redfin.com>
|
||||
Zac <zdoege@gm.slc.edu>
|
||||
GriffinSchneider <griffinschneider@gmail.com>
|
||||
Andres Kalle <mjomble@gmail.com>
|
||||
thefourtheye <thefourtheye@users.noreply.github.com>
|
||||
|
||||
476
deps/npm/CHANGELOG.md
vendored
476
deps/npm/CHANGELOG.md
vendored
@ -1,3 +1,465 @@
|
||||
### v3.8.3 (2016-03-17):
|
||||
|
||||
#### PERFORMANCE IMPROVEMENTS
|
||||
|
||||
The updated [`are-we-there-yet`](https://npm.com/package/are-we-there-yet)
|
||||
changes how it tracks how complete things are to be much more efficient.
|
||||
The summary is that `are-we-there-yet` was refactored to remove an expensive
|
||||
tree walk.
|
||||
|
||||
The result for you should be faster installs when working with very large trees.
|
||||
|
||||
Previously `are-we-there-yet` computed this when you asked by passing the request down
|
||||
its tree of progress indicators, totaling up the results. In doing so, it had to walk the
|
||||
entire tree of progress indicators.
|
||||
|
||||
By contrast, `are-we-there-yet` now updates a running total when a change
|
||||
is made, bubbling that up the tree from whatever branch made progress. This
|
||||
bubbling was already going on so there was nearly no cost associated with taking advantage of it.
|
||||
|
||||
* [`32f2bd0`](https://github.com/npm/npm/commit/32f2bd0e26116db253e619d67c4feae1de3ad2c2)
|
||||
`npmlog@2.0.3`:
|
||||
Bring in substantial performance improvements from `are-we-there-yet`.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
#### DUCT TAPE FOR BUGS
|
||||
|
||||
* [`473d324`](https://github.com/npm/npm/commit/473d3244a8ddfd6b260d0aa0d395b119d595bf97)
|
||||
[#11947](https://github.com/npm/npm/pull/11947)
|
||||
Guard against bugs that could cause the installer to crash with errors like:
|
||||
|
||||
```
|
||||
TypeError: Cannot read property 'target' of null
|
||||
```
|
||||
|
||||
This doesn't fix the bugs, but it does at least make the installer less
|
||||
likely to explode.
|
||||
([@thefourtheye](https://github.com/thefourtheye))
|
||||
|
||||
#### DOC FIXES
|
||||
|
||||
* [`ffa428a`](https://github.com/npm/npm/commit/ffa428a4eee482aa620819bc8df994a76fad7b0c)
|
||||
[#11880](https://github.com/npm/npm/pull/11880)
|
||||
Fix typo in `npm install` documentation.
|
||||
([@watilde](https://github.com/watilde))
|
||||
|
||||
#### DEPENDENCY UPDATES
|
||||
|
||||
* [`7537fe1`](https://github.com/npm/npm/commit/7537fe1748c27e6f1144b279b256cd3376d5c41c)
|
||||
`sorted-object@2.0.0`:
|
||||
Create objects with `{}` instead of `Object.create(null)` to make the results
|
||||
strictly equal to what, say, parsed JSON would provide.
|
||||
([@domenic](https://github.com/domenic))
|
||||
* [`8defb0f`](https://github.com/npm/npm/commit/8defb0f7b3ebdbe15c9ef5036052c10eda7e3161)
|
||||
`readable-stream@2.0.6`:
|
||||
Fix sync write issue on 0.10.
|
||||
([@calvinmetcalf](https://github.com/calvinmetcalf))
|
||||
|
||||
#### TEST FIXES FOR THE SELF TESTS
|
||||
|
||||
* [`c3edeab`](https://github.com/npm/npm/commit/c3edeabece4400308264e7cf4bc4448bd2729f55)
|
||||
[#11912](https://github.com/npm/npm/pull/11912)
|
||||
Change the self installation test to do its work in `/tmp`.
|
||||
Previously this was installing into a temp subdir in `test/tap`, which
|
||||
wouldn't catch the case where a module was installed in the local
|
||||
`node_modules` folder but not in dependencies, as node would look up
|
||||
the tree and use the copy from the version of npm being tested.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
### v3.8.2 (2016-03-10):
|
||||
|
||||
#### HAVING TROUBLE INSTALLING C MODULES ON ANDROID?
|
||||
|
||||
This release includes an updated `node-gyp` with fixes for Android.
|
||||
|
||||
* [`634ecba`](https://github.com/npm/npm/commit/634ecba320fb5a3287e8b7debfd8b931827b9e19)
|
||||
`node-gyp@3.3.1`:
|
||||
Fix bug in builds for Android.
|
||||
([@bnoordhuis](https://github.com/bnoordhuis))
|
||||
|
||||
#### NPM LOGOUT CLEANS UP BETTER
|
||||
|
||||
* [`460ed21`](https://github.com/npm/npm/commit/460ed217876ac78d21477c288f1c06563fb770b4)
|
||||
[#10529](https://github.com/npm/npm/issues/10529)
|
||||
If you ran `npm logout` with a scope, while we did invalidate your auth
|
||||
token, we weren't removing the auth token from your config file. This patch causes
|
||||
the auth token to be removed.
|
||||
([@wyze](https://github.com/wyze))
|
||||
|
||||
#### HELP MORE HELPFUL
|
||||
|
||||
* [`d1d0233`](https://github.com/npm/npm/commit/d1d02335d297da2734b538de44d8967bdcd354cf)
|
||||
[#11003](https://github.com/npm/npm/issues/11003)
|
||||
Update help to only show command names and their shortcuts. Previously
|
||||
some typo corrections were shown, along with various alternate
|
||||
spellings.
|
||||
([@watilde](https://github.com/watilde))
|
||||
* [`47928cd`](https://github.com/npm/npm/commit/47928cd6264e1d6d0ef67435b71c66d01bea664a)
|
||||
[#11003](https://github.com/npm/npm/issues/11003)
|
||||
Remove "verison" typo from the help listing.
|
||||
([@doug-wade](https://github.com/doug-wade))
|
||||
|
||||
#### MORE COMPLETE CONFIG LISTINGS
|
||||
|
||||
* [`cf5fd40`](https://github.com/npm/npm/commit/cf5fd401494d96325d74a8bb8c326aa0045a714c)
|
||||
[#11472](https://github.com/npm/npm/issues/11472)
|
||||
Make `npm config list` include the per-project `.npmrc` in the output.
|
||||
([@mjomble](https://github.com/mjomble))
|
||||
|
||||
#### DEPTH LIMITED PARSEABLE DEP LISTINGS
|
||||
|
||||
* [`611070f`](https://github.com/npm/npm/commit/611070f0f7a1e185c75cadae46179194084b398f)
|
||||
[#11495](https://github.com/npm/npm/issues/11495)
|
||||
Made `npm ls --parseable` honor the `--depth=#` option.
|
||||
([@zacdoe](https://github.com/zacdoe))
|
||||
|
||||
#### PROGRESS FOR THE (NON) UNICODE REVOLUTION
|
||||
|
||||
* [`ff90382`](https://github.com/npm/npm/commit/ff9038227a1976b5e936442716d9877f43c6c9b4)
|
||||
[#11781](https://github.com/npm/npm/issues/11781)
|
||||
Make the progress bars honor the unicode option.
|
||||
([@watilde](https://github.com/watilde))
|
||||
|
||||
#### `npm view --json`, NOW ACTUALLY JSON
|
||||
|
||||
* [`24ab70a`](https://github.com/npm/npm/commit/24ab70a4ccfeaa005b80252da313bb589510668e)
|
||||
[#11808](https://github.com/npm/npm/issues/11808)
|
||||
Make `npm view` produce valid JSON when requested with `--json`.
|
||||
Previously `npm view` produced some sort of weird hybrid output, with multiple
|
||||
JSON docs.
|
||||
([@doug-wade](https://github.com/doug-wade))
|
||||
|
||||
#### DOCUMENTATION CHANGES
|
||||
|
||||
* [`6fb0499`](https://github.com/npm/npm/commit/6fb0499bea868fdc637656d210c94f051481ecd4)
|
||||
[#11726](https://github.com/npm/npm/issues/11726)
|
||||
Previously we patched the `npm update` docs to suggest using `--depth
|
||||
Infinity` instead of `--depth 9999`, but that was a mistake. We forgot
|
||||
that `npm outdated` (on which `npm update` is built) has a special
|
||||
case where it treats `Infinity` as `0`. This reverts that patch.
|
||||
([@GriffinSchneider](https://github.com/GriffinSchneider))
|
||||
* [`f0bf684`](https://github.com/npm/npm/commit/f0bf684a87ea5eea03432a17f38678fed4960d43)
|
||||
[#11748](https://github.com/npm/npm/pull/11748)
|
||||
Document all of the various aliases for commands in the documentation
|
||||
for those commands.
|
||||
([@watilde](https://github.com/watilde))
|
||||
* [`fe04443`](https://github.com/npm/npm/commit/fe04443d8988e2e41bd4047078e06a26d05d380d)
|
||||
[#10968](https://github.com/npm/npm/issues/10968)
|
||||
The `npm-scope` document notes that scopes have been available on the
|
||||
public registry for a while. This adds that you'll need `npm@2` or later
|
||||
to use them.
|
||||
([@doug-wade](https://github.com/doug-wade))
|
||||
* [`3db37a5`](https://github.com/npm/npm/commit/3db37a52b2b2e3193ef250ad2cf96dfd2def2777)
|
||||
[#11820](https://github.com/npm/npm/pull/11820)
|
||||
The command `npm link` should be linking package from local folder to
|
||||
global, and `npm link package-name` should be from global to local. The
|
||||
description in the documentation was reversed and this fixes that.
|
||||
([@rhgb](https://github.com/rhgb))
|
||||
|
||||
#### GLOB FOR THE GLOB THRONE
|
||||
|
||||
* [`be55882`](https://github.com/npm/npm/commit/be55882dc4ee5ce0777b4badc9141dab5bf5be4d)
|
||||
`glob@7.0.3`:
|
||||
Fix a race condition and some windows edge cases.
|
||||
([@isaacs](https://github.com/isaacs))
|
||||
|
||||
### v3.8.1 (2016-03-03):
|
||||
|
||||
This week the install summary got better, killing your npm process now
|
||||
also kills the scripts it was running and a rarely used search flag got
|
||||
documented.
|
||||
|
||||
Our improvements on the test suite on Windows are beginning to pick up
|
||||
steam, you can follow along by
|
||||
[watching the PR](https://github.com/npm/npm/pull/11444).
|
||||
|
||||
#### BETTER INSTALL SUMMARIES
|
||||
|
||||
* [`e40d457`](https://github.com/npm/npm/commit/e40d4572cc98db06757df5b8bb6b7dbd0546d3d7)
|
||||
[#11699](https://github.com/npm/npm/issues/11699)
|
||||
Ensure that flags like `--production` passed to install don't result in
|
||||
the summary at the end being incorrectly filtered. That summary is
|
||||
produced by the same code as `npm ls` and therefore responds to flags
|
||||
the same way it does. This is undesirable when it's an install summary,
|
||||
however, as we don't want it to filter anything.
|
||||
|
||||
This fixes an issue where `npm install --production <module>` would
|
||||
result in npm exiting with an error code. The `--production` flag would
|
||||
make `npm ls` filter out `<module>` as it wasn't saved to the
|
||||
`package.json` and thus wasn't a production dependency. The install
|
||||
report is limited to show just the modules installed, so with that
|
||||
filtered out nothing is available. With nothing available `npm ls`
|
||||
would set `npm` to exit with an error code.
|
||||
([@ixalon](https://github.com/ixalon))
|
||||
* [`99337b4`](https://github.com/npm/npm/commit/99337b469163a4b211b9c6ff1aa9712ae0d601d2)
|
||||
[#11600](https://github.com/npm/npm/pull/11600)
|
||||
Make the report of installed modules really only show those modules
|
||||
that were installed. Previously it selected which modules from your
|
||||
tree to display based on `name@version` which worked great when your
|
||||
tree was deduped but would list things it hadn't touched when there
|
||||
were duplicates.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
#### SCRIPTS BETTER FOLLOW THE LEADER
|
||||
|
||||
* [`5454347`](https://github.com/npm/npm/commit/545434766eb3681d3f40b745f9f3187ed63f310a)
|
||||
[#10868](https://github.com/npm/npm/pull/10868)
|
||||
When running a lifecycle script, say through `npm start`, killing npm
|
||||
wouldn't forward that on to the children. It does now.
|
||||
([@daniel-pedersen](https://github.com/daniel-pedersen))
|
||||
|
||||
#### SEARCHING SPECIFIC REGISTRIES
|
||||
|
||||
* [`6020447`](https://github.com/npm/npm/commit/60204479f76458a9864aa530cda2b3333f95c2b0)
|
||||
[#11490](https://github.com/npm/npm/pull/11490)
|
||||
Add docs for using the `--registry` flag with search.
|
||||
([@plumlee](https://github.com/plumlee))
|
||||
|
||||
#### LODASH UPDATES
|
||||
|
||||
* [`bb14204`](https://github.com/npm/npm/commit/bb14204183dad620a6650452a26cdc64111f8136)
|
||||
`lodash.without@4.1.1`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`0089059`](https://github.com/npm/npm/commit/0089059c562aee9ad0398e55d2c12c68a6150e79)
|
||||
`lodash.keys@4.0.5`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`6ee1de4`](https://github.com/npm/npm/commit/6ee1de4474d9683a1f7023067d440780eeb10311)
|
||||
`lodash.clonedeep@4.3.1`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
|
||||
### v3.8.0 (2016-02-25):
|
||||
|
||||
This week brings a quality of life improvement for some Windows users, and
|
||||
an important knob to be tuned for folks experiencing network problems.
|
||||
|
||||
#### LIMIT CONCURRENT REQUESTS
|
||||
|
||||
We've long known that `npm`'s tendency to try to request all your
|
||||
dependencies simultaneously upset some network hardware (particular,
|
||||
consumer grade routers & proxies of all sorts). One of the reasons that we're
|
||||
planning to write our own npm specific version of `request` is to be able to
|
||||
more easily control this sort of thing.
|
||||
|
||||
But fortunately, you don't have to wait for that.
|
||||
[@misterbyrne](https://github.com/misterbyrne) took a look at our existing
|
||||
code and realized it could be added painlessly TODAY. The new default
|
||||
maximum is `50`, instead of `Infinity`. If you're having network issues you
|
||||
can try setting that value down to something lower (if you do, please let us
|
||||
know... the default is subject to tuning).
|
||||
|
||||
* [`910f9ac`](https://github.com/npm/npm/commit/910f9accf398466b8497952bee9f566ab50ade8c)
|
||||
[`f7be667`](https://github.com/npm/npm/commit/f7be667548a132ec190ac9d60a31885a7b4fe2b3)
|
||||
Add a new config option, `maxsockets` and `npm-registry-client@7.1.0` to
|
||||
take advantage of it.
|
||||
([@misterbyrne](https://github.com/misterbyrne))
|
||||
|
||||
#### WINDOWS GIT BASH
|
||||
|
||||
We think it's pretty keen too, we were making it really hard to actually
|
||||
upgrade if you were using it. NO MORE!
|
||||
|
||||
* [`d60351c`](https://github.com/npm/npm/commit/d60351ccae87d71a5f5eac73e3085c6290b52a69)
|
||||
[#11524](https://github.com/npm/npm/issues/11524)
|
||||
Prefer locally installed npm in Git Bash -- previous behavior was to use
|
||||
the global one. This was done previously for other shells, but not for Git
|
||||
Bash.
|
||||
([@destroyerofbuilds](https://github.com/destroyerofbuilds))
|
||||
|
||||
#### DOCUMENTATION IMPROVEMENTS
|
||||
|
||||
* [`b63de3c`](https://github.com/npm/npm/commit/b63de3c97c4c27078944249a4d5bbe1c502c23bc)
|
||||
[#11636](https://github.com/npm/npm/issues/11636)
|
||||
Document `--save-bundle` option in main install page.
|
||||
([@datyayu](https://github.com/datyayu))
|
||||
* [`3d26453`](https://github.com/npm/npm/commit/3d264532d6d9df60420e985334aebb53c668d32b)
|
||||
[#11644](https://github.com/npm/npm/pull/11644)
|
||||
Add `directories.test` to the `package.json` documentation.
|
||||
([@lewiscowper](https://github.com/lewiscowper))
|
||||
* [`b64d124`](https://github.com/npm/npm/commit/b64d12432fdad344199b678d700306340d3607eb)
|
||||
[#11441](https://github.com/npm/npm/pull/11441)
|
||||
Add a link in documentation to the contribution guidelines.
|
||||
([@watilde](https://github.com/watilde))
|
||||
* [`82fc548`](https://github.com/npm/npm/commit/82fc548b0e2abbdc4f7968c20b118c30cca79a24)
|
||||
[#11441](https://github.com/npm/npm/pull/11441/commits)
|
||||
Remove mentions of the long defunct Google group.
|
||||
([@watilde](https://github.com/watilde))
|
||||
* [`c6ad091`](https://github.com/npm/npm/commit/c6ad09131af2e2766d6034257a8fcaa294184121)
|
||||
[#11474](https://github.com/npm/npm/pull/11474)
|
||||
Correct invalid JSON in npm-update docs.
|
||||
([@robludwig](https://github.com/robludwig))
|
||||
* [`4906c90`](https://github.com/npm/npm/commit/4906c90ed2668adf59ebee759c7ebb811aa46e57)
|
||||
Expand on the documentation for `bundlededDependencies`, explaining what they are
|
||||
and when you might want to use them.
|
||||
([@gnerkus](https://github.com/gnerkus))
|
||||
|
||||
#### DEPENDENCY UPDATES
|
||||
|
||||
* [`93cdc25`](https://github.com/npm/npm/commit/93cdc25432b71cbc9c25c54ae316770e18f4b01e)
|
||||
`strip-ansi@3.0.1`:
|
||||
Non-user visible tests & maintainer doc updates.
|
||||
([@jbnicolai](https://github.com/jbnicolai))
|
||||
* [`3b2ccef`](https://github.com/npm/npm/commit/3b2ccef30dc2038b99ba93cd1404a1d01dac8790)
|
||||
`lodash.keys@4.0.4`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`30e9eb9`](https://github.com/npm/npm/commit/30e9eb97397a8f85081d328ea9aa54c2a7852613)
|
||||
`lodash._baseuniq@4.5.0`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
|
||||
|
||||
### v3.7.5 (2016-02-22):
|
||||
|
||||
A quick fixup release because when I updated glob, I missed the subdep copies of itself
|
||||
that it installed deeper in the tree. =/
|
||||
|
||||
This only effected people trying to update to `3.7.4` from `npm@2` or `npm@1`. Updates from
|
||||
`npm@3` worked fine (as it fixes up the missing subdeps during installation).
|
||||
|
||||
#### OH MY GLOB
|
||||
|
||||
* [`63fa704`](https://github.com/npm/npm/commit/63fa7044569127e6e29510dc499a865189806076)
|
||||
[#11633](https://github.com/npm/npm/issues/11633)
|
||||
When updating the top level `npm` to `glob@7`, the subdeps that
|
||||
still depended on `glob@6` got new versions installed but they
|
||||
weren't added to the commit. This adds them back in.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
### v3.7.4 (2016-02-18):
|
||||
|
||||
I'm ([@iarna](https://github.com/iarna)) back from vacation in the frozen
|
||||
wastes of Maine! This release sees a couple of bug fixes, some
|
||||
documentation updates, a bunch of dependency updates and improvements to our
|
||||
test suite.
|
||||
|
||||
#### FIXES FOR `update`, FIXES FOR `ls`
|
||||
|
||||
* [`53cdb96`](https://github.com/npm/npm/commit/53cdb96634fc329378b4ea4e767ba9987986a76e)
|
||||
[#11362](https://github.com/npm/npm/issues/11362)
|
||||
Make `npm update` stop trying to update linked packages.
|
||||
([@rhendric](https://github.com/rhendric))
|
||||
* [`8d90d25`](https://github.com/npm/npm/commit/8d90d25b3da086843ce43911329c9572bd109078)
|
||||
[#11559](https://github.com/npm/npm/issues/11559)
|
||||
Only list runtime dependencies when doing `npm ls --production`.
|
||||
([@yibn2008](https://github.com/yibn2008))
|
||||
|
||||
#### @wyze, DOCUMENTATION HERO OF THE PEOPLE, GETS THEIR OWN HEADER
|
||||
|
||||
* [`b78b301`](https://github.com/npm/npm/commit/b78b30171038ab737eff0b070281277e35af25b4)
|
||||
[#11416](https://github.com/npm/npm/pull/11416)
|
||||
Logout docs were using a section copy-pasted from the adduser docs.
|
||||
([@wyze](https://github.com/wyze))
|
||||
* [`649e28f`](https://github.com/npm/npm/commit/649e28f50aa323e75202eeedb824434535a0a4a0)
|
||||
[#11414](https://github.com/npm/npm/pull/11414)
|
||||
Add colon for consistency.
|
||||
([@wyze](https://github.com/wyze))
|
||||
|
||||
#### WHITTLING AWAY AT PATH LENGTHS
|
||||
|
||||
So for all of you who don't know -- Node.js does, in fact, support long Windows
|
||||
paths. Unfortunately, depending on the tool and the Windows version, a lot of
|
||||
external tooling does not. This means, for example, that some (all?) versions of
|
||||
Windows Explorer *can literally never delete npm from their system entirely
|
||||
because of deeply-nested npm dependencies*. Which is pretty gnarly.
|
||||
|
||||
Incidentally, if you run into that in particularly, you can use
|
||||
[rimraf](npm.im/rimraf) to remove such files 💁.
|
||||
|
||||
The latest victim of this issue was the Node.js CI setup for testing on Windows,
|
||||
which uses some tooling or another that croaks on the usual path length limit
|
||||
for that OS: 255 characters.
|
||||
|
||||
This isn't ordinarily an issue with `npm@3` as it produces mostly flat
|
||||
trees, but you may be surprised to learn that `npm`'s own distribution isn't
|
||||
flat, due to needing to be compatible with `npm@1.2`, which ships with
|
||||
`node@0.8`!
|
||||
|
||||
We've taken another baby step towards alleviating this in this release by
|
||||
updating a couple of dependencies that were preventing `npmlog` from deduping,
|
||||
and then doing a dedupe on that and `gauge`. Hopefully it helps.
|
||||
|
||||
* [`f3c32bc`](https://github.com/npm/npm/commit/f3c32bc3127301741d2fa3a26be6f5f127a35908)
|
||||
[#11528](https://github.com/npm/npm/pull/11528)
|
||||
`node-gyp@3.3.0`:
|
||||
Update to a more recent version that uses a version of npmlog compatible
|
||||
with npm itself. Also adds: AIX support, new `gyp`, `--cafile` command
|
||||
line option, and allows configuration of Node.js and io.js mirrors.
|
||||
([@rvagg](https://github.com/rvagg))
|
||||
|
||||
#### INTERNAL TEST IMPROVEMENTS
|
||||
|
||||
The `npm` core team's time recently has been sunk into `npm`'s many years of
|
||||
tech debt. Specifically, we've been working on improving the test suite.
|
||||
This isn't user visible, but in future should mean a more stable, easier to
|
||||
contribute to `npm`. Ordinarily we don't report these kinds of changes in
|
||||
the change log, but I thought I might share this week as this chunk is
|
||||
bigger than usual.
|
||||
|
||||
* [`07f020a`](https://github.com/npm/npm/commit/07f020a09e94ae393c67526985444e128ef6f83c)
|
||||
[#11292](https://github.com/npm/npm/pull/11292)
|
||||
`tacks@1.0.9`:
|
||||
Add a package that provides a tool to generate fixtures from folders and, relatedly,
|
||||
a module that an create and tear down filesystem fixtures easily.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`0837346`](https://github.com/npm/npm/commit/083734631f9b11b17c08bca8ba8cb736a7b1e3fb)
|
||||
[#11292](https://github.com/npm/npm/pull/11292)
|
||||
Remove all the relatively cryptic legacy tests and creates new tap tests
|
||||
that check the same functionality. The *legacy* tests were tests that
|
||||
were originally a shell script that was ported to javascript early in
|
||||
`npm`'s history.
|
||||
([@iarna](https://github.com/iarna))
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`5a701e7`](https://github.com/npm/npm/commit/5a701e71a0130787fb98450f9de92117b4ef88e1)
|
||||
[#11292](https://github.com/npm/npm/pull/11292)
|
||||
Test that we don't leak auth info into the environment.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`502d7d0`](https://github.com/npm/npm/commit/502d7d0628f08b09d8d13538ebccc63de8b3edf5)
|
||||
[#11292](https://github.com/npm/npm/pull/11292)
|
||||
Test that env vars properly passed into scripts.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`420f267`](https://github.com/npm/npm/commit/420f2672ee8c909f18bee10b1fc7d4ad91cf328b)
|
||||
[#11292](https://github.com/npm/npm/pull/11292)
|
||||
Test that npm's distribution binary is complete and can be installed and used.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`b7e99be`](https://github.com/npm/npm/commit/b7e99be1b1086f2d6098c653c1e20791269c9177)
|
||||
[#11292](https://github.com/npm/npm/pull/11292)
|
||||
Test that the `package.json` `files` section and `.npmignore` do what
|
||||
they're supposed to.
|
||||
([@zkat](https://github.com/zkat))
|
||||
|
||||
#### DEPENDENCY UPDATES
|
||||
|
||||
* [`4611098`](https://github.com/npm/npm/commit/4611098fd8c65d61a0645deb05bf38c81300ffca)
|
||||
`rimraf@2.5.2`:
|
||||
Use `glob@7.0.0`.
|
||||
([@isaacs](https://github.com/isaacs))
|
||||
* [`41b2772`](https://github.com/npm/npm/commit/41b2772cb83627f3b5b926cf81e150e7148cb124)
|
||||
`glob@7.0.0`:
|
||||
Raise error if `options.cwd` is specified, and not a directory.
|
||||
([@isaacs](https://github.com/isaacs))
|
||||
* [`c14e74a`](https://github.com/npm/npm/commit/c14e74ab5d17c764f3aa37123a9632fa965f8760)
|
||||
`gauge@1.2.7`: Update to newer lodash versions, for a smaller tree.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`d629363`](https://github.com/npm/npm/commit/d6293630ddc25bfa26d19b6be4fd2685976d7358)
|
||||
`lodash.without@4.1.0`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`3ea4c80`](https://github.com/npm/npm/commit/3ea4c8049ca8df9f64426b1db8a29b9579950134)
|
||||
`lodash.uniq@4.2.0`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`8ddcc8d`](https://github.com/npm/npm/commit/8ddcc8deb554660a3f7f474fae9758c967d94552)
|
||||
`lodash.union@4.2.0`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`2b656a6`](https://github.com/npm/npm/commit/2b656a672d351f32ee2af24dcee528356dcd64f4)
|
||||
`lodash.keys@4.0.3`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`ac171f8`](https://github.com/npm/npm/commit/ac171f8f0318a7dd3c515f3b83502dfa9e87adb8)
|
||||
`lodash.isarguments@3.0.7`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`bcccd90`](https://github.com/npm/npm/commit/bcccd9057b75d800c799ab15f00924f700415d3e)
|
||||
`lodash.clonedeep@4.3.0`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
* [`8165bca`](https://github.com/npm/npm/commit/8165bca537d86305a3d08f080f86223a26615aa8)
|
||||
`lodash._baseuniq@4.4.0`
|
||||
([@jdalton](https://github.com/jdalton))
|
||||
|
||||
### v3.7.3 (2016-02-11):
|
||||
|
||||
Hey all! We've got a pretty small release this week -- just documentation
|
||||
@ -389,7 +851,7 @@ version of Node.js and now suppress those other warnings.
|
||||
([@chrisirhc](https://github.com/chrisirhc))
|
||||
* [`00720db`](https://github.com/npm/npm/commit/00720db2c326cf8f968c662444a4575ae8c3020a)
|
||||
[#11158](https://github.com/npm/npm/pull/11158)
|
||||
On windows, the `node-gyp` wrapper would fail if your path to `node-gyp`
|
||||
On Windows, the `node-gyp` wrapper would fail if your path to `node-gyp`
|
||||
contained spaces. This fixes that problem by quoting use of that path.
|
||||
([@orangemocha](https://github.com/orangemocha))
|
||||
* [`69ac933`](https://github.com/npm/npm/commit/69ac9333506752bf2e5af70b3b3e03c6181de3e7)
|
||||
@ -520,13 +982,13 @@ particularly with Windows, so there's not too much to call out here.
|
||||
`glob@6.0.3`: Remove deprecated features and fix a bunch of bugs.
|
||||
([@isaacs](https://github.com/isaacs))
|
||||
* [`5b820c4`](https://github.com/npm/npm/commit/5b820c4e17c907fa8c23771c0cd8e74dd5fdaa51)
|
||||
`has-unicode@2.0.0`: Change the default on windows to be false, as
|
||||
international windows installs often install to non-unicode codepages and
|
||||
`has-unicode@2.0.0`: Change the default on Windows to be false, as
|
||||
international Windows installs often install to non-unicode codepages and
|
||||
there's no way to detect this short of a system call or a call to a
|
||||
command line program.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`238fe84`](https://github.com/npm/npm/commit/238fe84ac61297f1d71701d80368afaa40463305)
|
||||
`which@1.2.1`: Fixed bugs with uid/gid checks and with quoted windows PATH
|
||||
`which@1.2.1`: Fixed bugs with uid/gid checks and with quoted Windows PATH
|
||||
parts.
|
||||
([@isaacs](https://github.com/isaacs))
|
||||
* [`5e510e1`](https://github.com/npm/npm/commit/5e510e13d022a22d58742b126482d3b38a14cc83)
|
||||
@ -1624,7 +2086,7 @@ Unix-specific, so on Windows it just threw up its hands and
|
||||
stopped removing installed binaries at all. Not great.
|
||||
|
||||
So today we're fixing that– it let us maintain the same safety
|
||||
that we added in #9198, but ALSO works with windows.
|
||||
that we added in #9198, but ALSO works with Windows.
|
||||
|
||||
* [`25fbaed`](https://github.com/npm/npm/commit/25fbaed)
|
||||
[#9394](https://github.com/npm/npm/issues/9394)
|
||||
@ -1653,7 +2115,7 @@ release candidate.
|
||||
|
||||
* [`6665e54`](https://github.com/npm/npm/commit/6665e54)
|
||||
[#9505](https://github.com/npm/npm/pull/9505)
|
||||
Allow npm link to run on windows with prerelease versions of
|
||||
Allow npm link to run on Windows with prerelease versions of
|
||||
node
|
||||
([@jon-hall](https://github.com/jon-hall))
|
||||
|
||||
@ -2614,7 +3076,7 @@ nesting. You'll only see modules nested underneath one another when two (or
|
||||
more) modules have conflicting dependencies.
|
||||
|
||||
* [#3697](https://github.com/npm/npm/issues/3697)
|
||||
This will hopefully eliminate most cases where windows users ended up
|
||||
This will hopefully eliminate most cases where Windows users ended up
|
||||
with paths that were too long for Explorer and other standard tools to
|
||||
deal with.
|
||||
* [#6912](https://github.com/npm/npm/issues/6912)
|
||||
|
||||
13
deps/npm/Makefile
vendored
13
deps/npm/Makefile
vendored
@ -160,18 +160,23 @@ test: doc
|
||||
tag:
|
||||
npm tag npm@$(PUBLISHTAG) latest
|
||||
|
||||
publish: link doc
|
||||
ls-ok:
|
||||
node . ls >/dev/null
|
||||
|
||||
gitclean:
|
||||
git clean -fd
|
||||
|
||||
publish: gitclean ls-ok link doc
|
||||
@git push origin :v$(shell npm -v) 2>&1 || true
|
||||
git clean -fd &&\
|
||||
git push origin $(BRANCH) &&\
|
||||
git push origin --tags &&\
|
||||
npm publish --tag=$(PUBLISHTAG)
|
||||
|
||||
release: markedclean marked-manclean doc-clean doc
|
||||
release: gitclean ls-ok markedclean marked-manclean doc-clean doc
|
||||
node cli.js prune --production
|
||||
@bash scripts/release.sh
|
||||
|
||||
sandwich:
|
||||
@[ $$(whoami) = "root" ] && (echo "ok"; echo "ham" > sandwich) || (echo "make it yourself" && exit 13)
|
||||
|
||||
.PHONY: all latest install dev link doc clean uninstall test man doc-clean docclean release
|
||||
.PHONY: all latest install dev link doc clean uninstall test man doc-clean docclean release ls-ok realclean
|
||||
|
||||
7
deps/npm/bin/npm
vendored
7
deps/npm/bin/npm
vendored
@ -15,6 +15,13 @@ fi
|
||||
NPM_CLI_JS="$basedir/node_modules/npm/bin/npm-cli.js"
|
||||
|
||||
case `uname` in
|
||||
*MINGW*)
|
||||
NPM_PREFIX=`"$NODE_EXE" "$NPM_CLI_JS" prefix -g`
|
||||
NPM_PREFIX_NPM_CLI_JS="$NPM_PREFIX/node_modules/npm/bin/npm-cli.js"
|
||||
if [ -f "$NPM_PREFIX_NPM_CLI_JS" ]; then
|
||||
NPM_CLI_JS="$NPM_PREFIX_NPM_CLI_JS"
|
||||
fi
|
||||
;;
|
||||
*CYGWIN*)
|
||||
NPM_PREFIX=`"$NODE_EXE" "$NPM_CLI_JS" prefix -g`
|
||||
NPM_PREFIX_NPM_CLI_JS="$NPM_PREFIX/node_modules/npm/bin/npm-cli.js"
|
||||
|
||||
10
deps/npm/doc/cli/npm-adduser.md
vendored
10
deps/npm/doc/cli/npm-adduser.md
vendored
@ -5,6 +5,8 @@ npm-adduser(1) -- Add a registry user account
|
||||
|
||||
npm adduser [--registry=url] [--scope=@orgname] [--always-auth]
|
||||
|
||||
aliases: login, add-user
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
Create or verify a user named `<username>` in the specified registry, and
|
||||
@ -57,9 +59,11 @@ registries. Can be used with `--registry` and / or `--scope`, e.g.
|
||||
npm adduser --registry=http://private-registry.example.com --always-auth
|
||||
|
||||
This will ensure that all requests to that registry (including for tarballs)
|
||||
include an authorization header. See `always-auth` in `npm-config(7)` for more
|
||||
details on always-auth. Registry-specific configuration of `always-auth` takes
|
||||
precedence over any global configuration.
|
||||
include an authorization header. This setting may be necessary for use with
|
||||
private registries where metadata and package tarballs are stored on hosts with
|
||||
different hostnames. See `always-auth` in `npm-config(7)` for more details on
|
||||
always-auth. Registry-specific configuration of `always-auth` takes precedence
|
||||
over any global configuration.
|
||||
|
||||
## SEE ALSO
|
||||
|
||||
|
||||
2
deps/npm/doc/cli/npm-bugs.md
vendored
2
deps/npm/doc/cli/npm-bugs.md
vendored
@ -5,6 +5,8 @@ npm-bugs(1) -- Bugs for a package in a web browser maybe
|
||||
|
||||
npm bugs [<pkgname>]
|
||||
|
||||
aliases: issues
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
This command tries to guess at the likely location of a package's
|
||||
|
||||
2
deps/npm/doc/cli/npm-config.md
vendored
2
deps/npm/doc/cli/npm-config.md
vendored
@ -11,6 +11,8 @@ npm-config(1) -- Manage the npm configuration files
|
||||
npm get <key>
|
||||
npm set <key> <value> [-g|--global]
|
||||
|
||||
aliases: c
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
npm gets its config settings from the command line, environment
|
||||
|
||||
2
deps/npm/doc/cli/npm-dedupe.md
vendored
2
deps/npm/doc/cli/npm-dedupe.md
vendored
@ -6,6 +6,8 @@ npm-dedupe(1) -- Reduce duplication
|
||||
npm dedupe
|
||||
npm ddp
|
||||
|
||||
aliases: find-dupes, ddp
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
Searches the local package tree and attempts to simplify the overall
|
||||
|
||||
2
deps/npm/doc/cli/npm-dist-tag.md
vendored
2
deps/npm/doc/cli/npm-dist-tag.md
vendored
@ -7,6 +7,8 @@ npm-dist-tag(1) -- Modify package distribution tags
|
||||
npm dist-tag rm <pkg> <tag>
|
||||
npm dist-tag ls [<pkg>]
|
||||
|
||||
aliases: dist-tags
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
Add, remove, and enumerate distribution tags on a package:
|
||||
|
||||
2
deps/npm/doc/cli/npm-help-search.md
vendored
2
deps/npm/doc/cli/npm-help-search.md
vendored
@ -21,7 +21,7 @@ command directly.
|
||||
### long
|
||||
|
||||
* Type: Boolean
|
||||
* Default false
|
||||
* Default: false
|
||||
|
||||
If true, the "long" flag will cause help-search to output context around
|
||||
where the terms were found in the documentation.
|
||||
|
||||
9
deps/npm/doc/cli/npm-install.md
vendored
9
deps/npm/doc/cli/npm-install.md
vendored
@ -13,7 +13,7 @@ npm-install(1) -- Install a package
|
||||
npm install <folder>
|
||||
|
||||
alias: npm i
|
||||
common options: [-S|--save|-D|--save-dev|-O|--save-optional] [-E|--save-exact] [--dry-run]
|
||||
common options: [-S|--save|-D|--save-dev|-O|--save-optional] [-E|--save-exact] [-B|--save-bundle] [--dry-run]
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
@ -97,12 +97,14 @@ after packing it up into a tarball (b).
|
||||
* `-O, --save-optional`: Package will appear in your `optionalDependencies`.
|
||||
|
||||
When using any of the above options to save dependencies to your
|
||||
package.json, there is an additional, optional flag:
|
||||
package.json, there are two additional, optional flags:
|
||||
|
||||
* `-E, --save-exact`: Saved dependencies will be configured with an
|
||||
exact version rather than using npm's default semver range
|
||||
operator.
|
||||
|
||||
* `-B, --save-bundle`: Saved dependencies will also be added to your `bundleDependencies` list.
|
||||
|
||||
Further, if you have an `npm-shrinkwrap.json` then it will be updated as
|
||||
well.
|
||||
|
||||
@ -122,6 +124,7 @@ after packing it up into a tarball (b).
|
||||
npm install node-tap --save-dev
|
||||
npm install dtrace-provider --save-optional
|
||||
npm install readable-stream --save --save-exact
|
||||
npm install ansi-regex --save --save-bundle
|
||||
|
||||
|
||||
**Note**: If there is a file or folder named `<name>` in the current
|
||||
@ -266,7 +269,7 @@ The `--global-style` argument will cause 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.
|
||||
`node_modules` folders. This obviously will eliminate some deduping.
|
||||
|
||||
The `--legacy-bundling` argument will cause npm to install the package such
|
||||
that versions of npm prior to 1.4, such as the one included with node 0.8,
|
||||
|
||||
11
deps/npm/doc/cli/npm-link.md
vendored
11
deps/npm/doc/cli/npm-link.md
vendored
@ -12,12 +12,13 @@ npm-link(1) -- Symlink a package folder
|
||||
|
||||
Package linking is a two-step process.
|
||||
|
||||
First, `npm link` in a package folder will create a globally-installed
|
||||
symbolic link from `prefix/package-name` to the current folder (see
|
||||
`npm-config(7)` for the value of `prefix`).
|
||||
First, `npm link` in a package folder will create a symlink in the global folder
|
||||
`{prefix}/lib/node_modules/<package>` that links to the package where the `npm
|
||||
link` command was executed. (see `npm-config(7)` for the value of `prefix`).
|
||||
|
||||
Next, in some other location, `npm link package-name` will create a
|
||||
symlink from the local `node_modules` folder to the global symlink.
|
||||
symbolic link from globally-installed `package-name` to `node_modules/`
|
||||
of the current folder.
|
||||
|
||||
Note that `package-name` is taken from `package.json`,
|
||||
not from directory name.
|
||||
@ -40,7 +41,7 @@ For example:
|
||||
|
||||
Now, any changes to ~/projects/node-redis will be reflected in
|
||||
~/projects/node-bloggy/node_modules/node-redis/. Note that the link should
|
||||
be to the package name, not the directory name for that package.
|
||||
be to the package name, not the directory name for that package.
|
||||
|
||||
You may also shortcut the two steps in one. For example, to do the
|
||||
above use-case in a shorter way:
|
||||
|
||||
9
deps/npm/doc/cli/npm-logout.md
vendored
9
deps/npm/doc/cli/npm-logout.md
vendored
@ -31,14 +31,9 @@ it takes precedence.
|
||||
|
||||
Default: none
|
||||
|
||||
If specified, the user and login credentials given will be associated
|
||||
with the specified scope. See `npm-scope(7)`. You can use both at the same time,
|
||||
e.g.
|
||||
If specified, you will be logged out of the specified scope. See `npm-scope(7)`.
|
||||
|
||||
npm adduser --registry=http://myregistry.example.com --scope=@myco
|
||||
|
||||
This will set a registry for the given scope and login or create a user for
|
||||
that registry at the same time.
|
||||
npm logout --scope=@myco
|
||||
|
||||
## SEE ALSO
|
||||
|
||||
|
||||
2
deps/npm/doc/cli/npm-owner.md
vendored
2
deps/npm/doc/cli/npm-owner.md
vendored
@ -7,6 +7,8 @@ npm-owner(1) -- Manage package owners
|
||||
npm owner rm <user> [<@scope>/]<pkg>
|
||||
npm owner ls [<@scope>/]<pkg>
|
||||
|
||||
aliases: author
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
Manage ownership of published packages.
|
||||
|
||||
11
deps/npm/doc/cli/npm-search.md
vendored
11
deps/npm/doc/cli/npm-search.md
vendored
@ -5,7 +5,7 @@ npm-search(1) -- Search for packages
|
||||
|
||||
npm search [-l|--long] [search terms ...]
|
||||
|
||||
aliases: s, se
|
||||
aliases: s, se, find
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
@ -27,6 +27,15 @@ lines. When disabled (default) search results are truncated to fit
|
||||
neatly on a single line. Modules with extremely long names will
|
||||
fall on multiple lines.
|
||||
|
||||
### registry
|
||||
|
||||
* Default: https://registry.npmjs.org/
|
||||
* Type : url
|
||||
|
||||
Search the specified registry for modules. If you have configured npm to point to a different default registry,
|
||||
such as your internal private module repository, `npm search` will default to that registry when searching.
|
||||
Pass a different registry url such as the default above in order to override this setting.
|
||||
|
||||
## SEE ALSO
|
||||
|
||||
* npm-registry(7)
|
||||
|
||||
3
deps/npm/doc/cli/npm-test.md
vendored
3
deps/npm/doc/cli/npm-test.md
vendored
@ -4,7 +4,8 @@ npm-test(1) -- Test a package
|
||||
## SYNOPSIS
|
||||
|
||||
npm test [-- <args>]
|
||||
npm tst [-- <args>]
|
||||
|
||||
aliases: t, tst
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
|
||||
8
deps/npm/doc/cli/npm-update.md
vendored
8
deps/npm/doc/cli/npm-update.md
vendored
@ -5,6 +5,8 @@ npm-update(1) -- Update a package
|
||||
|
||||
npm update [-g] [<pkg>...]
|
||||
|
||||
aliases: up, upgrade
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
This command will update all the packages listed to the latest version
|
||||
@ -22,7 +24,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`.
|
||||
To get the old behavior, use `npm --depth 9999 update`.
|
||||
|
||||
## EXAMPLES
|
||||
|
||||
@ -36,7 +38,7 @@ on dependencies, `dep1` (`dep2`, .. etc.). The published versions of `dep1` are
|
||||
```
|
||||
{
|
||||
"dist-tags": { "latest": "1.2.2" },
|
||||
"versions": {
|
||||
"versions": [
|
||||
"1.2.2",
|
||||
"1.2.1",
|
||||
"1.2.0",
|
||||
@ -46,7 +48,7 @@ on dependencies, `dep1` (`dep2`, .. etc.). The published versions of `dep1` are
|
||||
"0.4.1",
|
||||
"0.4.0",
|
||||
"0.2.0"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
8
deps/npm/doc/cli/npm.md
vendored
8
deps/npm/doc/cli/npm.md
vendored
@ -127,11 +127,11 @@ Patches welcome!
|
||||
Contributors are listed in npm's `package.json` file. You can view them
|
||||
easily by doing `npm view npm contributors`.
|
||||
|
||||
If you would like to contribute, but don't know what to work on, check
|
||||
the issues list or ask on the mailing list.
|
||||
If you would like to contribute, but don't know what to work on, read
|
||||
the contributing guidelines and check the issues list.
|
||||
|
||||
* https://github.com/npm/npm/wiki/Contributing-Guidelines
|
||||
* <https://github.com/npm/npm/issues>
|
||||
* <npm-@googlegroups.com>
|
||||
|
||||
## BUGS
|
||||
|
||||
@ -139,8 +139,6 @@ When you find issues, please report them:
|
||||
|
||||
* web:
|
||||
<https://github.com/npm/npm/issues>
|
||||
* email:
|
||||
<npm-@googlegroups.com>
|
||||
|
||||
Be sure to include *all* of the output from the npm command that didn't work
|
||||
as expected. The `npm-debug.log` file is also helpful to provide.
|
||||
|
||||
31
deps/npm/doc/files/package.json.md
vendored
31
deps/npm/doc/files/package.json.md
vendored
@ -329,6 +329,11 @@ maybe, someday.
|
||||
|
||||
Put example scripts in here. Someday, it might be exposed in some clever way.
|
||||
|
||||
### directories.test
|
||||
|
||||
Put your tests in here. It is currently not exposed, but it might be in the
|
||||
future.
|
||||
|
||||
## repository
|
||||
|
||||
Specify the place where your code lives. This is helpful for people who
|
||||
@ -573,7 +578,31 @@ this. If you depend on features introduced in 1.5.2, use `">= 1.5.2 < 2"`.
|
||||
|
||||
## bundledDependencies
|
||||
|
||||
Array of package names that will be bundled when publishing the package.
|
||||
This defines an array of package names that will be bundled when publishing
|
||||
the package.
|
||||
|
||||
In cases where you need to preserve npm packages locally or have them
|
||||
available through a single file download, you can bundle the packages in a
|
||||
tarball file by specifying the package names in the `bundledDependencies`
|
||||
array and executing `npm pack`.
|
||||
|
||||
For example:
|
||||
|
||||
If we define a package.json like this:
|
||||
|
||||
```
|
||||
{
|
||||
"name": "awesome-web-framework",
|
||||
"version": "1.0.0",
|
||||
"bundledDependencies": [
|
||||
'renderized', 'super-streams'
|
||||
]
|
||||
}
|
||||
```
|
||||
we can obtain `awesome-web-framework-1.0.0.tgz` file by running `npm pack`.
|
||||
This file contains the dependencies `renderized` and `super-streams` which
|
||||
can be installed in a new project by executing `npm install
|
||||
awesome-web-framework-1.0.0.tgz`.
|
||||
|
||||
If this is spelled `"bundleDependencies"`, then that is also honored.
|
||||
|
||||
|
||||
8
deps/npm/doc/misc/npm-config.md
vendored
8
deps/npm/doc/misc/npm-config.md
vendored
@ -571,6 +571,14 @@ colored output if it is a TTY.
|
||||
|
||||
Show extended information in `npm ls` and `npm search`.
|
||||
|
||||
### maxsockets
|
||||
|
||||
* Default: 50
|
||||
* Type: Number
|
||||
|
||||
The maximum number of connections to use per origin (protocol/host/port
|
||||
combination). Passed to the `http` `Agent` used to make the request.
|
||||
|
||||
### message
|
||||
|
||||
* Default: "%s"
|
||||
|
||||
2
deps/npm/doc/misc/npm-scope.md
vendored
2
deps/npm/doc/misc/npm-scope.md
vendored
@ -54,7 +54,7 @@ just specifying to require the module `mypackage` in the folder called `@myorg`.
|
||||
Scoped packages can be published to any registry that supports them, including
|
||||
the public npm registry.
|
||||
|
||||
(As of 2015-04-19, the public npm registry **does** support scoped packages)
|
||||
(As of 2015-04-19, and with npm 2.0 or better, the public npm registry **does** support scoped packages)
|
||||
|
||||
If you wish, you may associate a scope with a registry; see below.
|
||||
|
||||
|
||||
2
deps/npm/html/doc/README.html
vendored
2
deps/npm/html/doc/README.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer"><a href="../doc/README.html">README</a> — npm@3.7.3</p>
|
||||
<p id="footer"><a href="../doc/README.html">README</a> — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-access.html
vendored
2
deps/npm/html/doc/cli/npm-access.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-access — npm@3.7.3</p>
|
||||
<p id="footer">npm-access — npm@3.8.3</p>
|
||||
|
||||
|
||||
12
deps/npm/html/doc/cli/npm-adduser.html
vendored
12
deps/npm/html/doc/cli/npm-adduser.html
vendored
@ -12,6 +12,8 @@
|
||||
<h1><a href="../cli/npm-adduser.html">npm-adduser</a></h1> <p>Add a registry user account</p>
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm adduser [--registry=url] [--scope=@orgname] [--always-auth]
|
||||
|
||||
aliases: login, add-user
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>Create or verify a user named <code><username></code> in the specified registry, and
|
||||
save the credentials to the <code>.npmrc</code> file. If no registry is specified,
|
||||
@ -44,9 +46,11 @@ registry should include authorization information. Useful for private
|
||||
registries. Can be used with <code>--registry</code> and / or <code>--scope</code>, e.g.</p>
|
||||
<pre><code>npm adduser --registry=http://private-registry.example.com --always-auth
|
||||
</code></pre><p>This will ensure that all requests to that registry (including for tarballs)
|
||||
include an authorization header. See <code>always-auth</code> in <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more
|
||||
details on always-auth. Registry-specific configuration of <code>always-auth</code> takes
|
||||
precedence over any global configuration.</p>
|
||||
include an authorization header. This setting may be necessary for use with
|
||||
private registries where metadata and package tarballs are stored on hosts with
|
||||
different hostnames. See <code>always-auth</code> in <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more details on
|
||||
always-auth. Registry-specific configuration of <code>always-auth</code> takes precedence
|
||||
over any global configuration.</p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../misc/npm-registry.html">npm-registry(7)</a></li>
|
||||
@ -68,5 +72,5 @@ precedence over any global configuration.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-adduser — npm@3.7.3</p>
|
||||
<p id="footer">npm-adduser — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-bin.html
vendored
2
deps/npm/html/doc/cli/npm-bin.html
vendored
@ -35,5 +35,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-bin — npm@3.7.3</p>
|
||||
<p id="footer">npm-bin — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-bugs.html
vendored
4
deps/npm/html/doc/cli/npm-bugs.html
vendored
@ -12,6 +12,8 @@
|
||||
<h1><a href="../cli/npm-bugs.html">npm-bugs</a></h1> <p>Bugs for a package in a web browser maybe</p>
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm bugs [<pkgname>]
|
||||
|
||||
aliases: issues
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>This command tries to guess at the likely location of a package's
|
||||
bug tracker URL, and then tries to open it using the <code>--browser</code>
|
||||
@ -53,5 +55,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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-bugs — npm@3.7.3</p>
|
||||
<p id="footer">npm-bugs — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-build.html
vendored
2
deps/npm/html/doc/cli/npm-build.html
vendored
@ -40,5 +40,5 @@ directly, run:</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-build — npm@3.7.3</p>
|
||||
<p id="footer">npm-build — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-bundle.html
vendored
2
deps/npm/html/doc/cli/npm-bundle.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-bundle — npm@3.7.3</p>
|
||||
<p id="footer">npm-bundle — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-cache.html
vendored
2
deps/npm/html/doc/cli/npm-cache.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-cache — npm@3.7.3</p>
|
||||
<p id="footer">npm-cache — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-completion.html
vendored
2
deps/npm/html/doc/cli/npm-completion.html
vendored
@ -44,5 +44,5 @@ completions based on the arguments.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-completion — npm@3.7.3</p>
|
||||
<p id="footer">npm-completion — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-config.html
vendored
4
deps/npm/html/doc/cli/npm-config.html
vendored
@ -18,6 +18,8 @@ npm config list
|
||||
npm config edit
|
||||
npm get <key>
|
||||
npm set <key> <value> [-g|--global]
|
||||
|
||||
aliases: c
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>npm gets its config settings from the command line, environment
|
||||
variables, <code>npmrc</code> files, and in some cases, the <code>package.json</code> file.</p>
|
||||
@ -65,5 +67,5 @@ global config.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-config — npm@3.7.3</p>
|
||||
<p id="footer">npm-config — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-dedupe.html
vendored
4
deps/npm/html/doc/cli/npm-dedupe.html
vendored
@ -13,6 +13,8 @@
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm dedupe
|
||||
npm ddp
|
||||
|
||||
aliases: find-dupes, ddp
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>Searches the local package tree and attempts to simplify the overall
|
||||
structure by moving dependencies further up the tree, where they can
|
||||
@ -59,5 +61,5 @@ result in new modules being installed.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-dedupe — npm@3.7.3</p>
|
||||
<p id="footer">npm-dedupe — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-deprecate.html
vendored
2
deps/npm/html/doc/cli/npm-deprecate.html
vendored
@ -38,5 +38,5 @@ something like this:</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-deprecate — npm@3.7.3</p>
|
||||
<p id="footer">npm-deprecate — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-dist-tag.html
vendored
4
deps/npm/html/doc/cli/npm-dist-tag.html
vendored
@ -14,6 +14,8 @@
|
||||
<pre><code>npm dist-tag add <pkg>@<version> [<tag>]
|
||||
npm dist-tag rm <pkg> <tag>
|
||||
npm dist-tag ls [<pkg>]
|
||||
|
||||
aliases: dist-tags
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>Add, remove, and enumerate distribution tags on a package:</p>
|
||||
<ul>
|
||||
@ -85,5 +87,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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-dist-tag — npm@3.7.3</p>
|
||||
<p id="footer">npm-dist-tag — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-docs.html
vendored
2
deps/npm/html/doc/cli/npm-docs.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-docs — npm@3.7.3</p>
|
||||
<p id="footer">npm-docs — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-edit.html
vendored
2
deps/npm/html/doc/cli/npm-edit.html
vendored
@ -49,5 +49,5 @@ or <code>"notepad"</code> on Windows.</li>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-edit — npm@3.7.3</p>
|
||||
<p id="footer">npm-edit — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-explore.html
vendored
2
deps/npm/html/doc/cli/npm-explore.html
vendored
@ -49,5 +49,5 @@ Windows</li>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-explore — npm@3.7.3</p>
|
||||
<p id="footer">npm-explore — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-help-search.html
vendored
4
deps/npm/html/doc/cli/npm-help-search.html
vendored
@ -23,7 +23,7 @@ command directly.</p>
|
||||
<h3 id="long">long</h3>
|
||||
<ul>
|
||||
<li>Type: Boolean</li>
|
||||
<li>Default false</li>
|
||||
<li>Default: false</li>
|
||||
</ul>
|
||||
<p>If true, the "long" flag will cause help-search to output context around
|
||||
where the terms were found in the documentation.</p>
|
||||
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-help-search — npm@3.7.3</p>
|
||||
<p id="footer">npm-help-search — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-help.html
vendored
2
deps/npm/html/doc/cli/npm-help.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-help — npm@3.7.3</p>
|
||||
<p id="footer">npm-help — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-init.html
vendored
2
deps/npm/html/doc/cli/npm-init.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-init — npm@3.7.3</p>
|
||||
<p id="footer">npm-init — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-install-test.html
vendored
2
deps/npm/html/doc/cli/npm-install-test.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-install-test — npm@3.7.3</p>
|
||||
<p id="footer">npm-install-test — npm@3.8.3</p>
|
||||
|
||||
11
deps/npm/html/doc/cli/npm-install.html
vendored
11
deps/npm/html/doc/cli/npm-install.html
vendored
@ -21,7 +21,7 @@ npm install <tarball url>
|
||||
npm install <folder>
|
||||
|
||||
alias: npm i
|
||||
common options: [-S|--save|-D|--save-dev|-O|--save-optional] [-E|--save-exact] [--dry-run]
|
||||
common options: [-S|--save|-D|--save-dev|-O|--save-optional] [-E|--save-exact] [-B|--save-bundle] [--dry-run]
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>This command installs a package, and any packages that it depends on. If the
|
||||
package has a shrinkwrap file, the installation of dependencies will be driven
|
||||
@ -84,11 +84,13 @@ after packing it up into a tarball (b).</p>
|
||||
</li>
|
||||
<li><p><code>-O, --save-optional</code>: Package will appear in your <code>optionalDependencies</code>.</p>
|
||||
<p>When using any of the above options to save dependencies to your
|
||||
package.json, there is an additional, optional flag:</p>
|
||||
package.json, there are two additional, optional flags:</p>
|
||||
</li>
|
||||
<li><p><code>-E, --save-exact</code>: Saved dependencies will be configured with an
|
||||
exact version rather than using npm's default semver range
|
||||
operator.</p>
|
||||
</li>
|
||||
<li><p><code>-B, --save-bundle</code>: Saved dependencies will also be added to your <code>bundleDependencies</code> list.</p>
|
||||
<p>Further, if you have an <code>npm-shrinkwrap.json</code> then it will be updated as
|
||||
well.</p>
|
||||
<p><code><scope></code> is optional. The package will be downloaded from the registry
|
||||
@ -104,6 +106,7 @@ npm install @myorg/privatepackage
|
||||
npm install node-tap --save-dev
|
||||
npm install dtrace-provider --save-optional
|
||||
npm install readable-stream --save --save-exact
|
||||
npm install ansi-regex --save --save-bundle
|
||||
</code></pre></li>
|
||||
</ul>
|
||||
</li>
|
||||
@ -213,7 +216,7 @@ rather than locally. See <code><a href="../files/npm-folders.html">npm-folders(
|
||||
your local <code>node_modules</code> folder with 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.</p>
|
||||
<code>node_modules</code> folders. This obviously will eliminate some deduping.</p>
|
||||
<p>The <code>--legacy-bundling</code> argument will cause npm to install the package such
|
||||
that versions of npm prior to 1.4, such as the one included with node 0.8,
|
||||
can install the package. This eliminates all automatic deduping.</p>
|
||||
@ -307,5 +310,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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-install — npm@3.7.3</p>
|
||||
<p id="footer">npm-install — npm@3.8.3</p>
|
||||
|
||||
|
||||
13
deps/npm/html/doc/cli/npm-link.html
vendored
13
deps/npm/html/doc/cli/npm-link.html
vendored
@ -17,11 +17,12 @@ npm link [<@scope>/]<pkg>[@<version>]
|
||||
alias: npm ln
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>Package linking is a two-step process.</p>
|
||||
<p>First, <code>npm link</code> in a package folder will create a globally-installed
|
||||
symbolic link from <code>prefix/package-name</code> to the current folder (see
|
||||
<code><a href="../misc/npm-config.html">npm-config(7)</a></code> for the value of <code>prefix</code>).</p>
|
||||
<p>First, <code>npm link</code> in a package folder will create a symlink in the global folder
|
||||
<code>{prefix}/lib/node_modules/<package></code> that links to the package where the <code>npm
|
||||
link</code> command was executed. (see <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for the value of <code>prefix</code>).</p>
|
||||
<p>Next, in some other location, <code>npm link package-name</code> will create a
|
||||
symlink from the local <code>node_modules</code> folder to the global symlink.</p>
|
||||
symbolic link from globally-installed <code>package-name</code> to <code>node_modules/</code>
|
||||
of the current folder.</p>
|
||||
<p>Note that <code>package-name</code> is taken from <code>package.json</code>,
|
||||
not from directory name.</p>
|
||||
<p>The package name can be optionally prefixed with a scope. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.
|
||||
@ -37,7 +38,7 @@ cd ~/projects/node-bloggy # go into some other package directory.
|
||||
npm link redis # link-install the package
|
||||
</code></pre><p>Now, any changes to ~/projects/node-redis will be reflected in
|
||||
~/projects/node-bloggy/node_modules/node-redis/. Note that the link should
|
||||
be to the package name, not the directory name for that package. </p>
|
||||
be to the package name, not the directory name for that package.</p>
|
||||
<p>You may also shortcut the two steps in one. For example, to do the
|
||||
above use-case in a shorter way:</p>
|
||||
<pre><code>cd ~/projects/node-bloggy # go into the dir of your main project
|
||||
@ -73,5 +74,5 @@ include that scope, e.g.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-link — npm@3.7.3</p>
|
||||
<p id="footer">npm-link — npm@3.8.3</p>
|
||||
|
||||
|
||||
12
deps/npm/html/doc/cli/npm-logout.html
vendored
12
deps/npm/html/doc/cli/npm-logout.html
vendored
@ -28,13 +28,9 @@ connected to that scope, if set.</p>
|
||||
it takes precedence.</p>
|
||||
<h3 id="scope">scope</h3>
|
||||
<p>Default: none</p>
|
||||
<p>If specified, the user and login credentials given will be associated
|
||||
with the specified scope. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>. You can use both at the same time,
|
||||
e.g.</p>
|
||||
<pre><code>npm adduser --registry=http://myregistry.example.com --scope=@myco
|
||||
</code></pre><p>This will set a registry for the given scope and login or create a user for
|
||||
that registry at the same time.</p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<p>If specified, you will be logged out of the specified scope. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p>
|
||||
<pre><code>npm logout --scope=@myco
|
||||
</code></pre><h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li>
|
||||
<li><a href="../misc/npm-registry.html">npm-registry(7)</a></li>
|
||||
@ -55,5 +51,5 @@ that registry at the same time.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-logout — npm@3.7.3</p>
|
||||
<p id="footer">npm-logout — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-ls.html
vendored
4
deps/npm/html/doc/cli/npm-ls.html
vendored
@ -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's source tree will show:</p>
|
||||
<pre><code>npm@3.7.3 /path/to/npm
|
||||
<pre><code>npm@3.8.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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-ls — npm@3.7.3</p>
|
||||
<p id="footer">npm-ls — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-outdated.html
vendored
2
deps/npm/html/doc/cli/npm-outdated.html
vendored
@ -116,5 +116,5 @@ project.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-outdated — npm@3.7.3</p>
|
||||
<p id="footer">npm-outdated — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-owner.html
vendored
4
deps/npm/html/doc/cli/npm-owner.html
vendored
@ -14,6 +14,8 @@
|
||||
<pre><code>npm owner add <user> [<@scope>/]<pkg>
|
||||
npm owner rm <user> [<@scope>/]<pkg>
|
||||
npm owner ls [<@scope>/]<pkg>
|
||||
|
||||
aliases: author
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>Manage ownership of published packages.</p>
|
||||
<ul>
|
||||
@ -49,5 +51,5 @@ that is not implemented at this time.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-owner — npm@3.7.3</p>
|
||||
<p id="footer">npm-owner — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-pack.html
vendored
2
deps/npm/html/doc/cli/npm-pack.html
vendored
@ -41,5 +41,5 @@ overwritten the second time.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-pack — npm@3.7.3</p>
|
||||
<p id="footer">npm-pack — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-ping.html
vendored
2
deps/npm/html/doc/cli/npm-ping.html
vendored
@ -32,4 +32,4 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-ping — npm@3.7.3</p>
|
||||
<p id="footer">npm-ping — npm@3.8.3</p>
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-prefix.html
vendored
2
deps/npm/html/doc/cli/npm-prefix.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-prefix — npm@3.7.3</p>
|
||||
<p id="footer">npm-prefix — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-prune.html
vendored
2
deps/npm/html/doc/cli/npm-prune.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-prune — npm@3.7.3</p>
|
||||
<p id="footer">npm-prune — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-publish.html
vendored
2
deps/npm/html/doc/cli/npm-publish.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-publish — npm@3.7.3</p>
|
||||
<p id="footer">npm-publish — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-rebuild.html
vendored
2
deps/npm/html/doc/cli/npm-rebuild.html
vendored
@ -35,5 +35,5 @@ the new binary.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-rebuild — npm@3.7.3</p>
|
||||
<p id="footer">npm-rebuild — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-repo.html
vendored
2
deps/npm/html/doc/cli/npm-repo.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-repo — npm@3.7.3</p>
|
||||
<p id="footer">npm-repo — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-restart.html
vendored
2
deps/npm/html/doc/cli/npm-restart.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-restart — npm@3.7.3</p>
|
||||
<p id="footer">npm-restart — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-root.html
vendored
2
deps/npm/html/doc/cli/npm-root.html
vendored
@ -35,5 +35,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-root — npm@3.7.3</p>
|
||||
<p id="footer">npm-root — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-run-script.html
vendored
2
deps/npm/html/doc/cli/npm-run-script.html
vendored
@ -60,5 +60,5 @@ you will be given a warning to run <code>npm install</code>, just in case you
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-run-script — npm@3.7.3</p>
|
||||
<p id="footer">npm-run-script — npm@3.8.3</p>
|
||||
|
||||
|
||||
12
deps/npm/html/doc/cli/npm-search.html
vendored
12
deps/npm/html/doc/cli/npm-search.html
vendored
@ -13,7 +13,7 @@
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm search [-l|--long] [search terms ...]
|
||||
|
||||
aliases: s, se
|
||||
aliases: s, se, find
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>Search the registry for packages matching the search terms.</p>
|
||||
<p>If a term starts with <code>/</code>, then it's interpreted as a regular expression.
|
||||
@ -29,6 +29,14 @@ expression characters must be escaped or quoted in most shells.)</p>
|
||||
lines. When disabled (default) search results are truncated to fit
|
||||
neatly on a single line. Modules with extremely long names will
|
||||
fall on multiple lines.</p>
|
||||
<h3 id="registry">registry</h3>
|
||||
<ul>
|
||||
<li>Default: <a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a></li>
|
||||
<li>Type : url</li>
|
||||
</ul>
|
||||
<p>Search the specified registry for modules. If you have configured npm to point to a different default registry,
|
||||
such as your internal private module repository, <code>npm search</code> will default to that registry when searching.
|
||||
Pass a different registry url such as the default above in order to override this setting.</p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../misc/npm-registry.html">npm-registry(7)</a></li>
|
||||
@ -49,5 +57,5 @@ fall on multiple lines.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-search — npm@3.7.3</p>
|
||||
<p id="footer">npm-search — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-shrinkwrap.html
vendored
2
deps/npm/html/doc/cli/npm-shrinkwrap.html
vendored
@ -169,5 +169,5 @@ contents rather than versions.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-shrinkwrap — npm@3.7.3</p>
|
||||
<p id="footer">npm-shrinkwrap — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-star.html
vendored
2
deps/npm/html/doc/cli/npm-star.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-star — npm@3.7.3</p>
|
||||
<p id="footer">npm-star — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-stars.html
vendored
2
deps/npm/html/doc/cli/npm-stars.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-stars — npm@3.7.3</p>
|
||||
<p id="footer">npm-stars — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-start.html
vendored
2
deps/npm/html/doc/cli/npm-start.html
vendored
@ -39,5 +39,5 @@ more details.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-start — npm@3.7.3</p>
|
||||
<p id="footer">npm-start — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-stop.html
vendored
2
deps/npm/html/doc/cli/npm-stop.html
vendored
@ -34,5 +34,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-stop — npm@3.7.3</p>
|
||||
<p id="footer">npm-stop — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-tag.html
vendored
2
deps/npm/html/doc/cli/npm-tag.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-tag — npm@3.7.3</p>
|
||||
<p id="footer">npm-tag — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-team.html
vendored
2
deps/npm/html/doc/cli/npm-team.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-team — npm@3.7.3</p>
|
||||
<p id="footer">npm-team — npm@3.8.3</p>
|
||||
|
||||
5
deps/npm/html/doc/cli/npm-test.html
vendored
5
deps/npm/html/doc/cli/npm-test.html
vendored
@ -12,7 +12,8 @@
|
||||
<h1><a href="../cli/npm-test.html">npm-test</a></h1> <p>Test a package</p>
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code> npm test [-- <args>]
|
||||
npm tst [-- <args>]
|
||||
|
||||
aliases: t, tst
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>This runs a package's "test" script, if one was provided.</p>
|
||||
<p>To run tests as a condition of installation, set the <code>npat</code> config to
|
||||
@ -37,5 +38,5 @@ true.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-test — npm@3.7.3</p>
|
||||
<p id="footer">npm-test — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-uninstall.html
vendored
2
deps/npm/html/doc/cli/npm-uninstall.html
vendored
@ -60,5 +60,5 @@ npm uninstall dtrace-provider --save-optional
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-uninstall — npm@3.7.3</p>
|
||||
<p id="footer">npm-uninstall — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-unpublish.html
vendored
2
deps/npm/html/doc/cli/npm-unpublish.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-unpublish — npm@3.7.3</p>
|
||||
<p id="footer">npm-unpublish — npm@3.8.3</p>
|
||||
|
||||
|
||||
10
deps/npm/html/doc/cli/npm-update.html
vendored
10
deps/npm/html/doc/cli/npm-update.html
vendored
@ -12,6 +12,8 @@
|
||||
<h1><a href="../cli/npm-update.html">npm-update</a></h1> <p>Update a package</p>
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm update [-g] [<pkg>...]
|
||||
|
||||
aliases: up, upgrade
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
<p>This command will update all the packages listed to the latest version
|
||||
(specified by the <code>tag</code> config), respecting semver.</p>
|
||||
@ -24,7 +26,7 @@ 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>.</p>
|
||||
To get the old behavior, use <code>npm --depth 9999 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
|
||||
@ -33,7 +35,7 @@ described below.</p>
|
||||
on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published versions of <code>dep1</code> are:</p>
|
||||
<pre><code>{
|
||||
"dist-tags": { "latest": "1.2.2" },
|
||||
"versions": {
|
||||
"versions": [
|
||||
"1.2.2",
|
||||
"1.2.1",
|
||||
"1.2.0",
|
||||
@ -43,7 +45,7 @@ on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published
|
||||
"0.4.1",
|
||||
"0.4.0",
|
||||
"0.2.0"
|
||||
}
|
||||
]
|
||||
}
|
||||
</code></pre><h3 id="caret-dependencies">Caret Dependencies</h3>
|
||||
<p>If <code>app</code>'s <code>package.json</code> contains:</p>
|
||||
@ -116,5 +118,5 @@ be <em>downgraded</em>.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-update — npm@3.7.3</p>
|
||||
<p id="footer">npm-update — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-version.html
vendored
2
deps/npm/html/doc/cli/npm-version.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-version — npm@3.7.3</p>
|
||||
<p id="footer">npm-version — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-view.html
vendored
2
deps/npm/html/doc/cli/npm-view.html
vendored
@ -86,5 +86,5 @@ the field name.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-view — npm@3.7.3</p>
|
||||
<p id="footer">npm-view — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-whoami.html
vendored
2
deps/npm/html/doc/cli/npm-whoami.html
vendored
@ -33,5 +33,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-whoami — npm@3.7.3</p>
|
||||
<p id="footer">npm-whoami — npm@3.8.3</p>
|
||||
|
||||
|
||||
14
deps/npm/html/doc/cli/npm.html
vendored
14
deps/npm/html/doc/cli/npm.html
vendored
@ -13,7 +13,7 @@
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm <command> [args]
|
||||
</code></pre><h2 id="version">VERSION</h2>
|
||||
<p>3.7.3</p>
|
||||
<p>3.8.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
|
||||
@ -106,19 +106,17 @@ file in the "doc" folder. (Don't worry about generating the man p
|
||||
</ul>
|
||||
<p>Contributors are listed in npm's <code>package.json</code> file. You can view them
|
||||
easily by doing <code>npm view npm contributors</code>.</p>
|
||||
<p>If you would like to contribute, but don't know what to work on, check
|
||||
the issues list or ask on the mailing list.</p>
|
||||
<p>If you would like to contribute, but don't know what to work on, read
|
||||
the contributing guidelines and check the issues list.</p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/npm/npm/wiki/Contributing-Guidelines">https://github.com/npm/npm/wiki/Contributing-Guidelines</a></li>
|
||||
<li><a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li>
|
||||
<li><a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li>
|
||||
</ul>
|
||||
<h2 id="bugs">BUGS</h2>
|
||||
<p>When you find issues, please report them:</p>
|
||||
<ul>
|
||||
<li>web:
|
||||
<a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li>
|
||||
<li>email:
|
||||
<a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li>
|
||||
</ul>
|
||||
<p>Be sure to include <em>all</em> of the output from the npm command that didn't work
|
||||
as expected. The <code>npm-debug.log</code> file is also helpful to provide.</p>
|
||||
@ -128,7 +126,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="mailto:i@izs.me">i@izs.me</a></p>
|
||||
<a href="mailto:i@izs.me">i@izs.me</a></p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../cli/npm-help.html">npm-help(1)</a></li>
|
||||
@ -153,5 +151,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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm — npm@3.7.3</p>
|
||||
<p id="footer">npm — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/files/npm-folders.html
vendored
2
deps/npm/html/doc/files/npm-folders.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-folders — npm@3.7.3</p>
|
||||
<p id="footer">npm-folders — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/files/npm-global.html
vendored
2
deps/npm/html/doc/files/npm-global.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-folders — npm@3.7.3</p>
|
||||
<p id="footer">npm-folders — npm@3.8.3</p>
|
||||
|
||||
|
||||
25
deps/npm/html/doc/files/npm-json.html
vendored
25
deps/npm/html/doc/files/npm-json.html
vendored
@ -245,6 +245,9 @@ walking the folder.</p>
|
||||
maybe, someday.</p>
|
||||
<h3 id="directories-example">directories.example</h3>
|
||||
<p>Put example scripts in here. Someday, it might be exposed in some clever way.</p>
|
||||
<h3 id="directories-test">directories.test</h3>
|
||||
<p>Put your tests in here. It is currently not exposed, but it might be in the
|
||||
future.</p>
|
||||
<h2 id="repository">repository</h2>
|
||||
<p>Specify the place where your code lives. This is helpful for people who
|
||||
want to contribute. If the git repo is on GitHub, then the <code>npm docs</code>
|
||||
@ -435,7 +438,25 @@ the host package's major version will break your plugin. Thus, if you've
|
||||
with every 1.x version of the host package, use <code>"^1.0"</code> or <code>"1.x"</code> to express
|
||||
this. If you depend on features introduced in 1.5.2, use <code>">= 1.5.2 < 2"</code>.</p>
|
||||
<h2 id="bundleddependencies">bundledDependencies</h2>
|
||||
<p>Array of package names that will be bundled when publishing the package.</p>
|
||||
<p>This defines an array of package names that will be bundled when publishing
|
||||
the package.</p>
|
||||
<p>In cases where you need to preserve npm packages locally or have them
|
||||
available through a single file download, you can bundle the packages in a
|
||||
tarball file by specifying the package names in the <code>bundledDependencies</code>
|
||||
array and executing <code>npm pack</code>.</p>
|
||||
<p>For example:</p>
|
||||
<p>If we define a package.json like this:</p>
|
||||
<pre><code>{
|
||||
"name": "awesome-web-framework",
|
||||
"version": "1.0.0",
|
||||
"bundledDependencies": [
|
||||
'renderized', 'super-streams'
|
||||
]
|
||||
}
|
||||
</code></pre><p>we can obtain <code>awesome-web-framework-1.0.0.tgz</code> file by running <code>npm pack</code>.
|
||||
This file contains the dependencies <code>renderized</code> and <code>super-streams</code> which
|
||||
can be installed in a new project by executing <code>npm install
|
||||
awesome-web-framework-1.0.0.tgz</code>.</p>
|
||||
<p>If this is spelled <code>"bundleDependencies"</code>, then that is also honored.</p>
|
||||
<h2 id="optionaldependencies">optionalDependencies</h2>
|
||||
<p>If a dependency can be used, but you would like npm to proceed if it cannot be
|
||||
@ -562,5 +583,5 @@ ignored.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">package.json — npm@3.7.3</p>
|
||||
<p id="footer">package.json — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/files/npmrc.html
vendored
2
deps/npm/html/doc/files/npmrc.html
vendored
@ -83,5 +83,5 @@ manner.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npmrc — npm@3.7.3</p>
|
||||
<p id="footer">npmrc — npm@3.8.3</p>
|
||||
|
||||
|
||||
25
deps/npm/html/doc/files/package.json.html
vendored
25
deps/npm/html/doc/files/package.json.html
vendored
@ -245,6 +245,9 @@ walking the folder.</p>
|
||||
maybe, someday.</p>
|
||||
<h3 id="directories-example">directories.example</h3>
|
||||
<p>Put example scripts in here. Someday, it might be exposed in some clever way.</p>
|
||||
<h3 id="directories-test">directories.test</h3>
|
||||
<p>Put your tests in here. It is currently not exposed, but it might be in the
|
||||
future.</p>
|
||||
<h2 id="repository">repository</h2>
|
||||
<p>Specify the place where your code lives. This is helpful for people who
|
||||
want to contribute. If the git repo is on GitHub, then the <code>npm docs</code>
|
||||
@ -435,7 +438,25 @@ the host package's major version will break your plugin. Thus, if you've
|
||||
with every 1.x version of the host package, use <code>"^1.0"</code> or <code>"1.x"</code> to express
|
||||
this. If you depend on features introduced in 1.5.2, use <code>">= 1.5.2 < 2"</code>.</p>
|
||||
<h2 id="bundleddependencies">bundledDependencies</h2>
|
||||
<p>Array of package names that will be bundled when publishing the package.</p>
|
||||
<p>This defines an array of package names that will be bundled when publishing
|
||||
the package.</p>
|
||||
<p>In cases where you need to preserve npm packages locally or have them
|
||||
available through a single file download, you can bundle the packages in a
|
||||
tarball file by specifying the package names in the <code>bundledDependencies</code>
|
||||
array and executing <code>npm pack</code>.</p>
|
||||
<p>For example:</p>
|
||||
<p>If we define a package.json like this:</p>
|
||||
<pre><code>{
|
||||
"name": "awesome-web-framework",
|
||||
"version": "1.0.0",
|
||||
"bundledDependencies": [
|
||||
'renderized', 'super-streams'
|
||||
]
|
||||
}
|
||||
</code></pre><p>we can obtain <code>awesome-web-framework-1.0.0.tgz</code> file by running <code>npm pack</code>.
|
||||
This file contains the dependencies <code>renderized</code> and <code>super-streams</code> which
|
||||
can be installed in a new project by executing <code>npm install
|
||||
awesome-web-framework-1.0.0.tgz</code>.</p>
|
||||
<p>If this is spelled <code>"bundleDependencies"</code>, then that is also honored.</p>
|
||||
<h2 id="optionaldependencies">optionalDependencies</h2>
|
||||
<p>If a dependency can be used, but you would like npm to proceed if it cannot be
|
||||
@ -562,5 +583,5 @@ ignored.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">package.json — npm@3.7.3</p>
|
||||
<p id="footer">package.json — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/index.html
vendored
2
deps/npm/html/doc/index.html
vendored
@ -162,5 +162,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-index — npm@3.7.3</p>
|
||||
<p id="footer">npm-index — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-coding-style.html
vendored
2
deps/npm/html/doc/misc/npm-coding-style.html
vendored
@ -154,5 +154,5 @@ set to anything."</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-coding-style — npm@3.7.3</p>
|
||||
<p id="footer">npm-coding-style — npm@3.8.3</p>
|
||||
|
||||
|
||||
9
deps/npm/html/doc/misc/npm-config.html
vendored
9
deps/npm/html/doc/misc/npm-config.html
vendored
@ -494,6 +494,13 @@ colored output if it is a TTY.</p>
|
||||
<li>Type: Boolean</li>
|
||||
</ul>
|
||||
<p>Show extended information in <code>npm ls</code> and <code>npm search</code>.</p>
|
||||
<h3 id="maxsockets">maxsockets</h3>
|
||||
<ul>
|
||||
<li>Default: 50</li>
|
||||
<li>Type: Number</li>
|
||||
</ul>
|
||||
<p>The maximum number of connections to use per origin (protocol/host/port
|
||||
combination). Passed to the <code>http</code> <code>Agent</code> used to make the request.</p>
|
||||
<h3 id="message">message</h3>
|
||||
<ul>
|
||||
<li>Default: "%s"</li>
|
||||
@ -849,5 +856,5 @@ exit successfully.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-config — npm@3.7.3</p>
|
||||
<p id="footer">npm-config — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-developers.html
vendored
2
deps/npm/html/doc/misc/npm-developers.html
vendored
@ -195,5 +195,5 @@ from a fresh checkout.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-developers — npm@3.7.3</p>
|
||||
<p id="footer">npm-developers — npm@3.8.3</p>
|
||||
|
||||
|
||||
8
deps/npm/html/doc/misc/npm-disputes.html
vendored
8
deps/npm/html/doc/misc/npm-disputes.html
vendored
@ -13,7 +13,7 @@
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<ol>
|
||||
<li>Get the author email with <code>npm owner ls <pkgname></code></li>
|
||||
<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li>
|
||||
<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li>
|
||||
<li>After a few weeks, if there's no resolution, we'll sort it out.</li>
|
||||
</ol>
|
||||
<p>Don't squat on package names. Publish code or move out of the way.</p>
|
||||
@ -51,12 +51,12 @@ Joe'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="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of
|
||||
adds the npm support staff <a href="mailto:support@npmjs.com">support@npmjs.com</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't come to any sort of resolution, email support
|
||||
<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is
|
||||
<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" 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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-disputes — npm@3.7.3</p>
|
||||
<p id="footer">npm-disputes — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-index.html
vendored
2
deps/npm/html/doc/misc/npm-index.html
vendored
@ -162,4 +162,4 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-index — npm@3.7.3</p>
|
||||
<p id="footer">npm-index — npm@3.8.3</p>
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-orgs.html
vendored
2
deps/npm/html/doc/misc/npm-orgs.html
vendored
@ -86,4 +86,4 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-orgs — npm@3.7.3</p>
|
||||
<p id="footer">npm-orgs — npm@3.8.3</p>
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-registry.html
vendored
2
deps/npm/html/doc/misc/npm-registry.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-registry — npm@3.7.3</p>
|
||||
<p id="footer">npm-registry — npm@3.8.3</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/misc/npm-scope.html
vendored
4
deps/npm/html/doc/misc/npm-scope.html
vendored
@ -45,7 +45,7 @@ just specifying to require the module <code>mypackage</code> in the folder calle
|
||||
<h2 id="publishing-scoped-packages">Publishing scoped packages</h2>
|
||||
<p>Scoped packages can be published to any registry that supports them, including
|
||||
the public npm registry.</p>
|
||||
<p>(As of 2015-04-19, the public npm registry <strong>does</strong> support scoped packages)</p>
|
||||
<p>(As of 2015-04-19, and with npm 2.0 or better, the public npm registry <strong>does</strong> support scoped packages)</p>
|
||||
<p>If you wish, you may associate a scope with a registry; see below.</p>
|
||||
<h3 id="publishing-public-scoped-packages-to-the-public-npm-registry">Publishing public scoped packages to the public npm registry</h3>
|
||||
<p>To publish a public scoped package, you must specify <code>--access public</code> with
|
||||
@ -91,5 +91,5 @@ that registry instead.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-scope — npm@3.7.3</p>
|
||||
<p id="footer">npm-scope — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-scripts.html
vendored
2
deps/npm/html/doc/misc/npm-scripts.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-scripts — npm@3.7.3</p>
|
||||
<p id="footer">npm-scripts — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/removing-npm.html
vendored
2
deps/npm/html/doc/misc/removing-npm.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">removing-npm — npm@3.7.3</p>
|
||||
<p id="footer">removing-npm — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/semver.html
vendored
2
deps/npm/html/doc/misc/semver.html
vendored
@ -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> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">semver — npm@3.7.3</p>
|
||||
<p id="footer">semver — npm@3.8.3</p>
|
||||
|
||||
|
||||
2
deps/npm/lib/cache.js
vendored
2
deps/npm/lib/cache.js
vendored
@ -285,7 +285,7 @@ function add (args, where, cb) {
|
||||
break
|
||||
case 'remote':
|
||||
// get auth, if possible
|
||||
mapToRegistry(spec, npm.config, function (err, uri, auth) {
|
||||
mapToRegistry(p.raw, npm.config, function (err, uri, auth) {
|
||||
if (err) return cb(err)
|
||||
|
||||
addRemoteTarball(p.spec, { name: p.name }, null, auth, cb)
|
||||
|
||||
3
deps/npm/lib/cache/caching-client.js
vendored
3
deps/npm/lib/cache/caching-client.js
vendored
@ -207,6 +207,7 @@ function adaptConfig (config) {
|
||||
userAgent: config.get('user-agent'),
|
||||
log: log,
|
||||
defaultTag: config.get('tag'),
|
||||
couchToken: config.get('_token')
|
||||
couchToken: config.get('_token'),
|
||||
maxSockets: config.get('maxsockets')
|
||||
}
|
||||
}
|
||||
|
||||
19
deps/npm/lib/config.js
vendored
19
deps/npm/lib/config.js
vendored
@ -195,6 +195,25 @@ function list (cb) {
|
||||
msg += '\n'
|
||||
}
|
||||
|
||||
// project config file
|
||||
var project = npm.config.sources.project
|
||||
var pconf = project.data
|
||||
var ppath = project.path
|
||||
var pconfKeys = getKeys(pconf)
|
||||
if (pconfKeys.length) {
|
||||
msg += '; project config ' + ppath + '\n'
|
||||
pconfKeys.forEach(function (k) {
|
||||
var val = (k.charAt(0) === '_')
|
||||
? '---sekretz---'
|
||||
: JSON.stringify(pconf[k])
|
||||
if (pconf[k] !== npm.config.get(k)) {
|
||||
if (!long) return
|
||||
msg += '; ' + k + ' = ' + val + ' (overridden)\n'
|
||||
} else msg += k + ' = ' + val + '\n'
|
||||
})
|
||||
msg += '\n'
|
||||
}
|
||||
|
||||
// user config file
|
||||
var uconf = npm.config.sources.user.data
|
||||
var uconfKeys = getKeys(uconf)
|
||||
|
||||
115
deps/npm/lib/config/cmd-list.js
vendored
Normal file
115
deps/npm/lib/config/cmd-list.js
vendored
Normal file
@ -0,0 +1,115 @@
|
||||
var extend = Object.assign || require('util')._extend
|
||||
|
||||
// short names for common things
|
||||
var shorthands = {
|
||||
'un': 'uninstall',
|
||||
'rb': 'rebuild',
|
||||
'list': 'ls',
|
||||
'ln': 'link',
|
||||
'i': 'install',
|
||||
'it': 'install-test',
|
||||
'up': 'update',
|
||||
'c': 'config',
|
||||
's': 'search',
|
||||
'se': 'search',
|
||||
'unstar': 'star', // same function
|
||||
'tst': 'test',
|
||||
't': 'test',
|
||||
'ddp': 'dedupe',
|
||||
'v': 'view'
|
||||
}
|
||||
|
||||
var affordances = {
|
||||
'la': 'ls',
|
||||
'll': 'ls',
|
||||
'verison': 'version',
|
||||
'isntall': 'install',
|
||||
'dist-tags': 'dist-tag',
|
||||
'apihelp': 'help',
|
||||
'find-dupes': 'dedupe',
|
||||
'upgrade': 'update',
|
||||
'login': 'adduser',
|
||||
'add-user': 'adduser',
|
||||
'author': 'owner',
|
||||
'home': 'docs',
|
||||
'issues': 'bugs',
|
||||
'info': 'view',
|
||||
'show': 'view',
|
||||
'find': 'search',
|
||||
'unlink': 'uninstall',
|
||||
'remove': 'uninstall',
|
||||
'rm': 'uninstall',
|
||||
'r': 'uninstall'
|
||||
}
|
||||
|
||||
// these are filenames in .
|
||||
var cmdList = [
|
||||
'install',
|
||||
'install-test',
|
||||
'uninstall',
|
||||
'cache',
|
||||
'config',
|
||||
'set',
|
||||
'get',
|
||||
'update',
|
||||
'outdated',
|
||||
'prune',
|
||||
'pack',
|
||||
'dedupe',
|
||||
|
||||
'rebuild',
|
||||
'link',
|
||||
|
||||
'publish',
|
||||
'star',
|
||||
'stars',
|
||||
'tag',
|
||||
'adduser',
|
||||
'logout',
|
||||
'unpublish',
|
||||
'owner',
|
||||
'access',
|
||||
'team',
|
||||
'deprecate',
|
||||
'shrinkwrap',
|
||||
|
||||
'help',
|
||||
'help-search',
|
||||
'ls',
|
||||
'search',
|
||||
'view',
|
||||
'init',
|
||||
'version',
|
||||
'edit',
|
||||
'explore',
|
||||
'docs',
|
||||
'repo',
|
||||
'bugs',
|
||||
'faq',
|
||||
'root',
|
||||
'prefix',
|
||||
'bin',
|
||||
'whoami',
|
||||
'dist-tag',
|
||||
'ping',
|
||||
|
||||
'test',
|
||||
'stop',
|
||||
'start',
|
||||
'restart',
|
||||
'run-script',
|
||||
'completion'
|
||||
]
|
||||
|
||||
var plumbing = [
|
||||
'build',
|
||||
'unbuild',
|
||||
'xmas',
|
||||
'substack',
|
||||
'visnup'
|
||||
]
|
||||
module.exports.aliases = extend(extend({}, shorthands), affordances)
|
||||
module.exports.shorthands = shorthands
|
||||
module.exports.affordances = affordances
|
||||
module.exports.cmdList = cmdList
|
||||
module.exports.plumbing = plumbing
|
||||
2
deps/npm/lib/config/defaults.js
vendored
2
deps/npm/lib/config/defaults.js
vendored
@ -165,6 +165,7 @@ Object.defineProperty(exports, 'defaults', {get: function () {
|
||||
loglevel: 'warn',
|
||||
logstream: process.stderr,
|
||||
long: false,
|
||||
maxsockets: 50,
|
||||
message: '%s',
|
||||
'node-version': process.version,
|
||||
npat: false,
|
||||
@ -276,6 +277,7 @@ exports.types = {
|
||||
loglevel: ['silent', 'error', 'warn', 'http', 'info', 'verbose', 'silly'],
|
||||
logstream: Stream,
|
||||
long: Boolean,
|
||||
maxsockets: Number,
|
||||
message: String,
|
||||
'node-version': [null, semver],
|
||||
npat: Boolean,
|
||||
|
||||
15
deps/npm/lib/config/get-credentials-by-uri.js
vendored
15
deps/npm/lib/config/get-credentials-by-uri.js
vendored
@ -20,6 +20,14 @@ function getCredentialsByURI (uri) {
|
||||
alwaysAuth: undefined
|
||||
}
|
||||
|
||||
// used to override scope matching for tokens as well as legacy auth
|
||||
if (this.get(nerfed + ':always-auth') !== undefined) {
|
||||
var val = this.get(nerfed + ':always-auth')
|
||||
c.alwaysAuth = val === 'false' ? false : !!val
|
||||
} else if (this.get('always-auth') !== undefined) {
|
||||
c.alwaysAuth = this.get('always-auth')
|
||||
}
|
||||
|
||||
if (this.get(nerfed + ':_authToken')) {
|
||||
c.token = this.get(nerfed + ':_authToken')
|
||||
// the bearer token is enough, don't confuse things
|
||||
@ -58,13 +66,6 @@ function getCredentialsByURI (uri) {
|
||||
c.email = this.get('email')
|
||||
}
|
||||
|
||||
if (this.get(nerfed + ':always-auth') !== undefined) {
|
||||
var val = this.get(nerfed + ':always-auth')
|
||||
c.alwaysAuth = val === 'false' ? false : !!val
|
||||
} else if (this.get('always-auth') !== undefined) {
|
||||
c.alwaysAuth = this.get('always-auth')
|
||||
}
|
||||
|
||||
if (c.username && c.password) {
|
||||
c.auth = new Buffer(c.username + ':' + c.password).toString('base64')
|
||||
}
|
||||
|
||||
5
deps/npm/lib/help.js
vendored
5
deps/npm/lib/help.js
vendored
@ -12,6 +12,9 @@ var npm = require('./npm.js')
|
||||
var log = require('npmlog')
|
||||
var opener = require('opener')
|
||||
var glob = require('glob')
|
||||
var cmdList = require('./config/cmd-list').cmdList
|
||||
var shorthands = require('./config/cmd-list').shorthands
|
||||
var commands = cmdList.concat(Object.keys(shorthands))
|
||||
|
||||
function help (args, cb) {
|
||||
var argv = npm.config.get('argv').cooked
|
||||
@ -163,7 +166,7 @@ function npmUsage (valid, cb) {
|
||||
'',
|
||||
'where <command> is one of:',
|
||||
npm.config.get('long') ? usages()
|
||||
: ' ' + wrap(Object.keys(npm.commands)),
|
||||
: ' ' + wrap(commands),
|
||||
'',
|
||||
'npm <cmd> -h quick help on <cmd>',
|
||||
'npm -l display full usage info',
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user