60 deps/npm/man/man1/npm-README.1
View file
@@ -234,64 +234,68 @@ command line arguments using nopt\. You may also want to check out \fBnpm
help config\fR to learn about all the options you can set there\.
.
.SH "More Docs"
Check out the docs \fIhttps://npmjs\.org/doc/\fR,
especially the faq \fIhttps://npmjs\.org/doc/faq\.html\fR\|\.
Check out the docs \fIhttps://www\.npmjs\.org/doc/\fR,
especially the faq \fIhttps://www\.npmjs\.org/doc/faq\.html\fR\|\.
.
.P
You can use the \fBnpm help\fR command to read any of them\.
.
.P
If you\'re a developer, and you want to use npm to publish your program,
you should read this \fIhttps://npmjs\.org/doc/developers\.html\fR
you should read this \fIhttps://www\.npmjs\.org/doc/developers\.html\fR
.
.SH "Legal Stuff"
"npm" and "the npm registry" are owned by Isaac Z\. Schlueter\.
"npm" and "The npm Registry" are owned by npm, Inc\.
All rights reserved\. See the included LICENSE file for more details\.
.
.P
"Node\.js" and "node" are trademarks owned by Joyent, Inc\. npm is not
officially part of the Node\.js project, and is neither owned by nor
officially affiliated with Joyent, Inc\.
"Node\.js" and "node" are trademarks owned by Joyent, Inc\.
.
.P
The packages in the npm registry are not part of npm itself, and are the
sole property of their respective maintainers\. While every effort is
made to ensure accountability, there is absolutely no guarantee,
warrantee, or assertion made as to the quality, fitness for a specific
purpose, or lack of malice in any given npm package\. Modules
published on the npm registry are not affiliated with or endorsed by
Joyent, Inc\., Isaac Z\. Schlueter, Ryan Dahl, or the Node\.js project\.
Modules published on the npm registry are not officially endorsed by
npm, Inc\. or the Node\.js project\.
.
.P
If you have a complaint about a package in the npm registry, and cannot
resolve it with the package owner, please express your concerns to
Isaac Z\. Schlueter at \fIi@izs\.me\fR\|\.
Data published to the npm registry is not part of npm itself, and is
the sole property of the publisher\. While every effort is made to
ensure accountability, there is absolutely no guarantee, warrantee, or
assertion expressed or implied as to the quality, fitness for a
specific purpose, or lack of malice in any given npm package\.
.
.SS "In plain english"
This is mine; not my employer\'s, not Node\'s, not Joyent\'s, not Ryan
Dahl\'s\.
.P
If you have a complaint about a package in the public npm registry,
and cannot resolve it with the package
owner \fIhttps://www\.npmjs\.org/doc/misc/npm\-disputes\.html\fR, please email \fIsupport@npmjs\.com\fR and explain the situation\.
.
.P
Any data published to The npm Registry (including user account
information) may be removed or modified at the sole discretion of the
npm server administrators\.
.
.SS "In plainer english"
npm is the property of npm, Inc\.
.
.P
If you publish something, it\'s yours, and you are solely accountable
for it\. Not me, not Node, not Joyent, not Ryan Dahl\.
for it\.
.
.P
If other people publish something, it\'s theirs\. Not mine, not Node\'s,
not Joyent\'s, not Ryan Dahl\'s\.
If other people publish something, it\'s theirs\.
.
.P
Yes, you can publish something evil\. It will be removed promptly if
reported, and we\'ll lose respect for you\. But there is no vetting
process for published modules\.
Users can publish Bad Stuff\. It will be removed promptly if reported\.
But there is no vetting process for published modules, and you use
them at your own risk\. Please inspect the source\.
.
.P
If this concerns you, inspect the source before using packages\.
If you publish Bad Stuff, we may delete it from the registry, or even
ban your account in extreme cases\. So don\'t do that\.
.
.SH "BUGS"
When you find issues, please report them:
.
.IP "\(bu" 4
web: \fIhttps://github\.com/isaacs/npm/issues\fR
web: \fIhttps://github\.com/npm/npm/issues\fR
.
.IP "\(bu" 4
email: \fInpm\-@googlegroups\.com\fR
6 deps/npm/man/man1/npm-install.1
View file
@@ -244,9 +244,9 @@ Examples:
.IP "" 4
.
.nf
git+ssh://git@github\.com:isaacs/npm\.git#v1\.0\.27
git+https://isaacs@github\.com/isaacs/npm\.git
git://github\.com/isaacs/npm\.git#v1\.0\.27
git+ssh://git@github\.com:npm/npm\.git#v1\.0\.27
git+https://isaacs@github\.com/npm/npm\.git
git://github\.com/npm/npm\.git#v1\.0\.27
.
.fi
.
12 deps/npm/man/man1/npm-ls.1
View file
@@ -29,7 +29,7 @@ For example, running \fBnpm ls promzard\fR in npm\'s source tree will show:
.IP "" 4
.
.nf
npm@1.3.26 /path/to/npm
npm@1.4.3 /path/to/npm
└─┬ init\-package\-json@0\.0\.4
└── promzard@0\.1\.5
.
@@ -103,6 +103,16 @@ Type: Boolean
List packages in the global install prefix instead of in the current
project\.
.
.SS "depth"
.
.IP "\(bu" 4
Type: Int
.
.IP "" 0
.
.P
Max display depth of the dependency tree\.
.
.SH "SEE ALSO"
.
.IP "\(bu" 4
65 deps/npm/man/man1/npm-outdated.1
View file
@@ -22,6 +22,71 @@ The resulting field \'wanted\' shows the latest version according to the
version specified in the package\.json, the field \'latest\' the very latest
version of the package\.
.
.SH "CONFIGURATION"
.
.SS "json"
.
.IP "\(bu" 4
Default: false
.
.IP "\(bu" 4
Type: Boolean
.
.IP "" 0
.
.P
Show information in JSON format\.
.
.SS "long"
.
.IP "\(bu" 4
Default: false
.
.IP "\(bu" 4
Type: Boolean
.
.IP "" 0
.
.P
Show extended information\.
.
.SS "parseable"
.
.IP "\(bu" 4
Default: false
.
.IP "\(bu" 4
Type: Boolean
.
.IP "" 0
.
.P
Show parseable output instead of tree view\.
.
.SS "global"
.
.IP "\(bu" 4
Default: false
.
.IP "\(bu" 4
Type: Boolean
.
.IP "" 0
.
.P
Check packages in the global install prefix instead of in the current
project\.
.
.SS "depth"
.
.IP "\(bu" 4
Type: Int
.
.IP "" 0
.
.P
Max depth for checking dependency tree\.
.
.SH "SEE ALSO"
.
.IP "\(bu" 4
6 deps/npm/man/man1/npm.1
View file
@@ -14,7 +14,7 @@ npm <command> [args]
.fi
.
.SH "VERSION"
1.3.26
1.4.3
.
.SH "DESCRIPTION"
npm is the package manager for the Node JavaScript platform\. It puts
@@ -165,7 +165,7 @@ If you would like to contribute, but don\'t know what to work on, check
the issues list or ask on the mailing list\.
.
.IP "\(bu" 4
\fIhttp://github\.com/isaacs/npm/issues\fR
\fIhttp://github\.com/npm/npm/issues\fR
.
.IP "\(bu" 4
\fInpm\-@googlegroups\.com\fR
@@ -176,7 +176,7 @@ the issues list or ask on the mailing list\.
When you find issues, please report them:
.
.IP "\(bu" 4
web: \fIhttp://github\.com/isaacs/npm/issues\fR
web: \fIhttp://github\.com/npm/npm/issues\fR
.
.IP "\(bu" 4
email: \fInpm\-@googlegroups\.com\fR
2 deps/npm/man/man3/npm.3
View file
@@ -21,7 +21,7 @@ npm\.load([configObject], function (er, npm) {
.fi
.
.SH "VERSION"
1.3.26
1.4.3
.
.SH "DESCRIPTION"
This is the API documentation for npm\.
2 deps/npm/man/man5/npm-json.5
View file
@@ -349,7 +349,7 @@ Do it like this:
.nf
"repository" :
{ "type" : "git"
, "url" : "http://github\.com/isaacs/npm\.git"
, "url" : "http://github\.com/npm/npm\.git"
}
"repository" :
{ "type" : "svn"
2 deps/npm/man/man5/package.json.5
View file
@@ -349,7 +349,7 @@ Do it like this:
.nf
"repository" :
{ "type" : "git"
, "url" : "http://github\.com/isaacs/npm\.git"
, "url" : "http://github\.com/npm/npm\.git"
}
"repository" :
{ "type" : "svn"
2 deps/npm/man/man7/npm-coding-style.7
View file
@@ -191,7 +191,7 @@ Always create a new Error object with your message\. Don\'t just return a
string message to the callback\. Stack traces are handy\.
.
.SH "Logging"
Logging is done using the npmlog \fIhttps://github\.com/isaacs/npmlog\fR
Logging is done using the npmlog \fIhttps://github\.com/npm/npmlog\fR
utility\.
.
.P
4 deps/npm/man/man7/npm-config.7
View file
@@ -712,7 +712,7 @@ The value \fBnpm init\fR should use by default for the package author\'s homepag
.SS "init\.license"
.
.IP "\(bu" 4
Default: "BSD\-2\-Clause"
Default: "ISC"
.
.IP "\(bu" 4
Type: String
@@ -826,7 +826,7 @@ Type: Stream
.IP "" 0
.
.P
This is the stream that is passed to the npmlog \fIhttps://github\.com/isaacs/npmlog\fR module at run time\.
This is the stream that is passed to the npmlog \fIhttps://github\.com/npm/npmlog\fR module at run time\.
.
.P
It cannot be set from the command line, but if you are using npm
17 deps/npm/man/man7/npm-disputes.7
View file
@@ -12,7 +12,7 @@
Get the author email with \fBnpm owner ls <pkgname>\fR
.
.IP "2" 4
Email the author, CC \fIi@izs\.me\fR\|\.
Email the author, CC \fIsupport@npmjs\.com\fR
.
.IP "3" 4
After a few weeks, if there\'s no resolution, we\'ll sort it out\.
@@ -67,16 +67,17 @@ Joe\'s appropriate course of action in each case is the same\.
owner (Bob)\.
.
.IP "2" 4
Joe emails Bob, explaining the situation \fBas respectfully as possible\fR,
and what he would like to do with the module name\. He adds
isaacs \fIi@izs\.me\fR to the CC list of the email\. Mention in the email
that Bob can run \fBnpm owner add joe foo\fR to add Joe as an owner of
the \fBfoo\fR package\.
Joe emails Bob, explaining the situation \fBas respectfully as
possible\fR, and what he would like to do with the module name\. He
adds the npm support staff \fIsupport@npmjs\.com\fR to the CC list of
the email\. Mention in the email that Bob can run \fBnpm owner add
joe foo\fR to add Joe as an owner of the \fBfoo\fR package\.
.
.IP "3" 4
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 isaacs \fIi@izs\.me\fR and we\'ll sort it out\. ("Reasonable" is usually about 4
weeks, but extra time is allowed around common holidays\.)
Bob and Joe can\'t come to any sort of resolution, email support \fIsupport@npmjs\.com\fR and we\'ll sort it out\. ("Reasonable" is
usually at least 4 weeks, but extra time is allowed around common
holidays\.)
.
.IP "" 0
.
32 deps/npm/man/man7/npm-faq.7
View file
@@ -7,7 +7,7 @@
\fBnpm-faq\fR \-\- Frequently Asked Questions
.
.SH "Where can I find these docs in HTML?"
\fIhttps://npmjs\.org/doc/\fR, or run:
\fIhttps://www\.npmjs\.org/doc/\fR, or run:
.
.IP "" 4
.
@@ -84,7 +84,8 @@ That\'s what it\'s for\. Install it globally, then link it into each
program that uses it\.
.
.SH "Whatever, I really want the old style &#39;everything global&#39; style\."
Write your own package manager, then\. It\'s not that hard\.
Write your own package manager\. You could probably even wrap up \fBnpm\fR
in a shell script if you really wanted to\.
.
.P
npm will not help you do something that is known to be a bad idea\.
@@ -405,17 +406,21 @@ Go to \fIhttps://npmjs\.org/forgot\fR\|\.
Either the registry is down, or node\'s DNS isn\'t able to reach out\.
.
.P
To check if the registry is down, open up \fIhttp://registry\.npmjs\.org/\fR
in a web browser\. This will also tell you if you are just unable to
access the internet for some reason\.
To check if the registry is down, open up \fIhttps://registry\.npmjs\.org/\fR in a web browser\. This will also tell
you if you are just unable to access the internet for some reason\.
.
.P
If the registry IS down, let me know by emailing \fIi@izs\.me\fR or posting
an issue at \fIhttps://github\.com/isaacs/npm/issues\fR\|\. We\'ll have
someone kick it or something\.
If the registry IS down, let us know by emailing \fIsupport@npmjs\.com\fR
or posting an issue at \fIhttps://github\.com/npm/npm/issues\fR\|\. If it\'s
down for the world (and not just on your local network) then we\'re
probably already being pinged about it\.
.
.P
You can also often get a faster response by visiting the #npm channel
on Freenode IRC\.
.
.SH "Why no namespaces?"
Please see this discussion: \fIhttps://github\.com/isaacs/npm/issues/798\fR
Please see this discussion: \fIhttps://github\.com/npm/npm/issues/798\fR
.
.P
tl;dr \- It doesn\'t actually make things better, and can make them worse\.
@@ -425,16 +430,19 @@ If you want to namespace your own packages, you may: simply use the \fB\-\fR cha
There is not sufficient need to impose namespace rules on everyone\.
.
.SH "Who does npm?"
\fBnpm view npm author\fR
npm was originally written by Isaac Z\. Schlueter, and many others have
contributed to it, some of them quite substantially\.
.
.P
\fBnpm view npm contributors\fR
The npm open source project, The npm Registry, and the community
website \fIhttps://www\.npmjs\.org\fR are maintained and operated by the
good folks at npm, Inc\. \fIhttps://www\.npmjs\.com\fR
.
.SH "I have a question or request not addressed here\. Where should I put it?"
Post an issue on the github project:
.
.IP "\(bu" 4
\fIhttps://github\.com/isaacs/npm/issues\fR
\fIhttps://github\.com/npm/npm/issues\fR
.
.IP "" 0
.
2 deps/npm/man/man7/npm-registry.7
View file
@@ -19,7 +19,7 @@ account information\.
.P
The official public npm registry is at \fIhttp://registry\.npmjs\.org/\fR\|\. It
is powered by a CouchDB database at \fIhttp://isaacs\.iriscouch\.com/registry\fR\|\. The code for the couchapp is
available at \fIhttp://github\.com/isaacs/npmjs\.org\fR\|\. npm user accounts
available at \fIhttp://github\.com/npm/npmjs\.org\fR\|\. npm user accounts
are CouchDB users, stored in the \fIhttp://isaacs\.iriscouch\.com/_users\fR
database\.
.
2 deps/npm/node_modules/glob/package.json
View file
2 deps/npm/node_modules/graceful-fs/graceful-fs.js
View file
10 deps/npm/node_modules/graceful-fs/package.json
View file
21 deps/npm/node_modules/graceful-fs/test/readdir-sort.js
View file
8 deps/npm/node_modules/nopt/README.md
View file
213 deps/npm/node_modules/nopt/lib/nopt.js
View file
12 deps/npm/node_modules/nopt/package.json
View file

Large diffs are not rendered by default.

235 deps/npm/node_modules/nopt/test/basic.js
View file
234 deps/npm/node_modules/npm-install-checks/LICENSE
View file
25 deps/npm/node_modules/npm-install-checks/README.md
View file
146 deps/npm/node_modules/npm-install-checks/index.js
View file
43 deps/npm/node_modules/npm-install-checks/package.json
View file
35 deps/npm/node_modules/npm-install-checks/test/check-engine.js
View file
31 deps/npm/node_modules/npm-install-checks/test/check-git.js
View file
44 deps/npm/node_modules/npm-install-checks/test/check-platform.js
View file
17 deps/npm/node_modules/npm-registry-client/index.js
View file
3 deps/npm/node_modules/npm-registry-client/lib/adduser.js
View file
2 deps/npm/node_modules/npm-registry-client/lib/deprecate.js
View file
8 deps/npm/node_modules/npm-registry-client/lib/get.js
View file
27 deps/npm/node_modules/npm-registry-client/lib/publish.js
View file
65 deps/npm/node_modules/npm-registry-client/lib/request.js
View file
2 deps/npm/node_modules/npm-registry-client/lib/star.js
View file
3 deps/npm/node_modules/npm-registry-client/lib/unpublish.js
View file
4 deps/npm/node_modules/npm-registry-client/node_modules/couch-login/.npmignore
View file

This file was deleted.

15 deps/npm/node_modules/npm-registry-client/node_modules/couch-login/LICENSE
View file

This file was deleted.

278 deps/npm/node_modules/npm-registry-client/node_modules/couch-login/README.md
View file

This file was deleted.

399 deps/npm/node_modules/npm-registry-client/node_modules/couch-login/couch-login.js
View file

This file was deleted.

33 deps/npm/node_modules/npm-registry-client/node_modules/couch-login/package.json
View file

This file was deleted.

100 deps/npm/node_modules/npm-registry-client/node_modules/couch-login/test/00-setup.js
View file

This file was deleted.

298 deps/npm/node_modules/npm-registry-client/node_modules/couch-login/test/basic.js
View file

This file was deleted.

BIN -4.1 KB ...node_modules/npm-registry-client/node_modules/couch-login/test/fixtures/_replicator.couch
View file
Binary file not shown.