diff --git a/deps/npm/AUTHORS b/deps/npm/AUTHORS index 890b29f085..3c0c0b0ba8 100644 --- a/deps/npm/AUTHORS +++ b/deps/npm/AUTHORS @@ -115,3 +115,44 @@ Vaz Allen elisee Evan You Wil Moore III +Dylan Greene +zeke +Andrew Horton +Denis Gladkikh +Daniel Santiago +Alex Kocharin +Evan Lucas +Steve Mason +Quinn Slack +Sébastien Santoro +CamilleM +Tom Huang +Sergey Belov +Younghoon Park +Yazhong Liu +Mikola Lysenko +Rafael de Oleza +Yeonghoon Park +Franck Cuny +Alan Shaw +Alex Rodionov +Alexej Yaroshevich +Elan Shanker +François Frisch +Gabriel Falkenberg +Jason Diamond +Jess Martin +Jon Spencer +Matt Colyer +Matt McClure +Maximilian Antoni +Nicholas Kinsey +Paulo Cesar +Quim Calpe +Robert Gieseke +Spain Train +TJ Holowaychuk +Thom Blake +Trevor Burnham +bitspill +Neil Gentleman diff --git a/deps/npm/CONTRIBUTING.md b/deps/npm/CONTRIBUTING.md index 7a60ed2a2b..0a5b53a125 100644 --- a/deps/npm/CONTRIBUTING.md +++ b/deps/npm/CONTRIBUTING.md @@ -1,5 +1,9 @@ ## Before you submit a new issue -* Check if there's a simple solution in the [Troubleshooting](https://github.com/npm/npm/wiki/Troubleshooting) wiki. -* [Search for similar issues](https://github.com/npm/npm/search?q=Similar%20issues&type=Issues). -* Ensure your new issue conforms to the [Contributing Guidelines](https://github.com/npm/npm/wiki/Contributing-Guidelines). +* Check if there's a simple solution in the + [Troubleshooting](https://github.com/npm/npm/wiki/Troubleshooting) + wiki. +* [Search for similar + issues](https://github.com/npm/npm/search?q=Similar%20issues&type=Issues). +* Ensure your new issue conforms to the [Contributing + Guidelines](https://github.com/npm/npm/wiki/Contributing-Guidelines). diff --git a/deps/npm/README.md b/deps/npm/README.md index e2f0f79b5b..ceea97e8ba 100644 --- a/deps/npm/README.md +++ b/deps/npm/README.md @@ -169,51 +169,54 @@ help config` to learn about all the options you can set there. ## More Docs -Check out the [docs](https://npmjs.org/doc/), -especially the [faq](https://npmjs.org/doc/faq.html). +Check out the [docs](https://www.npmjs.org/doc/), +especially the [faq](https://www.npmjs.org/doc/faq.html). You can use the `npm help` command to read any of them. If you're a developer, and you want to use npm to publish your program, -you should [read this](https://npmjs.org/doc/developers.html) +you should [read this](https://www.npmjs.org/doc/developers.html) ## 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. -"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. -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. -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 . +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. -### In plain english +If you have a complaint about a package in the public npm registry, +and cannot [resolve it with the package +owner](https://www.npmjs.org/doc/misc/npm-disputes.html), please email + and explain the situation. -This is mine; not my employer's, not Node's, not Joyent's, not Ryan -Dahl's. +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. + +### In plainer english + +npm is the property of npm, Inc. 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. -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. -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. -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. ## BUGS diff --git a/deps/npm/doc/misc/npm-disputes.md b/deps/npm/doc/misc/npm-disputes.md index 6e9f4bfcd5..9fb1eaab45 100644 --- a/deps/npm/doc/misc/npm-disputes.md +++ b/deps/npm/doc/misc/npm-disputes.md @@ -4,7 +4,7 @@ npm-disputes(7) -- Handling Module Name Disputes ## SYNOPSIS 1. Get the author email with `npm owner ls ` -2. Email the author, CC . +2. Email the author, CC 3. After a few weeks, if there's no resolution, we'll sort it out. Don't squat on package names. Publish code or move out of the way. @@ -42,15 +42,16 @@ Joe's appropriate course of action in each case is the same. 1. `npm owner ls foo`. This will tell Joe the email address of the owner (Bob). -2. Joe emails Bob, explaining the situation **as respectfully as possible**, - and what he would like to do with the module name. He adds - isaacs to the CC list of the email. Mention in the email - that Bob can run `npm owner add joe foo` to add Joe as an owner of - the `foo` package. +2. Joe emails Bob, explaining the situation **as respectfully as + possible**, and what he would like to do with the module name. He + adds the npm support staff to the CC list of + the email. Mention in the email that Bob can run `npm owner add + joe foo` to add Joe as an owner of the `foo` package. 3. 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 - 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 + and we'll sort it out. ("Reasonable" is + usually at least 4 weeks, but extra time is allowed around common + holidays.) ## REASONING diff --git a/deps/npm/doc/misc/npm-faq.md b/deps/npm/doc/misc/npm-faq.md index c2288389c5..80e3d1ad4b 100644 --- a/deps/npm/doc/misc/npm-faq.md +++ b/deps/npm/doc/misc/npm-faq.md @@ -3,7 +3,7 @@ npm-faq(7) -- Frequently Asked Questions ## Where can I find these docs in HTML? -, or run: +, or run: npm config set viewer browser @@ -68,7 +68,8 @@ program that uses it. ## Whatever, I really want the old style 'everything global' style. -Write your own package manager, then. It's not that hard. +Write your own package manager. You could probably even wrap up `npm` +in a shell script if you really wanted to. npm will not help you do something that is known to be a bad idea. @@ -310,13 +311,17 @@ Go to . Either the registry is down, or node's DNS isn't able to reach out. -To check if the registry is down, open up -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 + in a web browser. This will also tell +you if you are just unable to access the internet for some reason. -If the registry IS down, let me know by emailing or posting -an issue at . We'll have -someone kick it or something. +If the registry IS down, let us know by emailing +or posting an issue at . If it's +down for the world (and not just on your local network) then we're +probably already being pinged about it. + +You can also often get a faster response by visiting the #npm channel +on Freenode IRC. ## Why no namespaces? @@ -330,9 +335,12 @@ There is not sufficient need to impose namespace rules on everyone. ## Who does npm? -`npm view npm author` +npm was originally written by Isaac Z. Schlueter, and many others have +contributed to it, some of them quite substantially. -`npm view npm contributors` +The npm open source project, The npm Registry, and [the community +website](https://www.npmjs.org) are maintained and operated by the +good folks at [npm, Inc.](https://www.npmjs.com) ## I have a question or request not addressed here. Where should I put it? diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index d457ec95eb..747c1c2e75 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -175,51 +175,54 @@ help config to learn about all the options you can set there.

More Docs

-

Check out the docs, -especially the faq.

+

Check out the docs, +especially the faq.

You can use the npm help command to read any of them.

If you're a developer, and you want to use npm to publish your program, -you should read this

+you should read this

-

"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.

-

"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.

-

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.

-

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 i@izs.me.

+

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.

-

In plain english

+

If you have a complaint about a package in the public npm registry, +and cannot resolve it with the package +owner, please email +support@npmjs.com and explain the situation.

-

This is mine; not my employer's, not Node's, not Joyent's, not Ryan -Dahl's.

+

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.

+ +

In plainer english

+ +

npm is the property of npm, Inc.

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.

-

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.

-

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.

-

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.

BUGS

@@ -239,7 +242,7 @@ will no doubt tell you to put the output in a gist or email.

- +