Skip to content
This repository has been archived by the owner. It is now read-only.
Browse files

npm: Upgrade to 1.1.37

  • Loading branch information...
isaacs committed Jul 10, 2012
1 parent 8a946c2 commit ae5a209b114508ec4290ab31b37ef3a34bdab15a
Showing 396 changed files with 8,641 additions and 4,122 deletions.
@@ -1,16 +1,16 @@

# don't need these in the npm package.
@@ -66,3 +66,8 @@ Joost-Wim Boekesteijn <>
Dalmais Maxence <>
Marcus Ekwall <>
Aaron Stacy <>
Phillip Howell <>
Domenic Denicola <>
James Halliday <>
Jeremy Cantrell <>
Ribettes <>
@@ -49,6 +49,11 @@ and are not covered by this license.
"npm Logo" created by Mathias Pettersson and Brian Hammond,
used with permission.

"Gubblebum Blocky" font
Copyright (c) 2007 by Tjarda Koster,
included for use in the npm website and documentation,
used with permission.

This program uses "node-uuid", Copyright (c) 2010 Robert Kieffer,
according to the terms of the MIT license.

@@ -89,21 +89,15 @@ To install the latest **unstable** development version from git:

git clone
cd npm
git submodule update --init --recursive
sudo make install # (or: `node cli.js install -gf`)

If you're sitting in the code folder reading this document in your
terminal, then you've already got the code. Just do:

git submodule update --init --recursive
sudo make install

and npm will install itself.

Note that github tarballs **do not contain submodules**, so
those won't work. You'll have to also fetch the appropriate submodules
listed in the .gitmodules file.

## Permissions when Using npm to Install Other Stuff

@@ -1,6 +1,13 @@
if [ -x "`dirname "$0"`/node.exe" ]; then
"`dirname "$0"`/node.exe" "`dirname "$0"`/node_modules/npm/bin/npm-cli.js" "$@"

basedir=`dirname "$0"`

case `uname` in
*CYGWIN*) basedir=`cygpath -w "$basedir"`;;

if [ -x "$basedir/node.exe" ]; then
"$basedir/node.exe" "$basedir/node_modules/npm/bin/npm-cli.js" "$@"
node "`dirname "$0"`/node_modules/npm/bin/npm-cli.js" "$@"
node "$basedir/node_modules/npm/bin/npm-cli.js" "$@"
@@ -15,9 +15,9 @@ if (typeof WScript !== "undefined") {

process.title = "npm"

var log = require("../lib/utils/log.js")
log.waitForConfig()"ok", "it worked if it ends with")
var log = require("npmlog")
log.pause() // will be unpaused when config is loaded."it worked if it ends with", "ok")

var fs = require("graceful-fs")
, path = require("path")
@@ -36,7 +36,7 @@ if (path.basename(process.argv[1]).slice(-1) === "g") {
process.argv.splice(1, 1, "npm", "-g")

log.verbose(process.argv, "cli")
log.verbose("cli", process.argv)

var conf = nopt(types, shorthands)
npm.argv = conf.argv.remain
@@ -56,8 +56,8 @@ if (conf.versions) {
}"npm@"+npm.version, "using")"node@"+process.version, "using")"using", "npm@%s", npm.version)"using", "node@%s", process.version)

// make sure that this version of node works with this version of npm.
var semver = require("semver")
@@ -6,7 +6,7 @@ if (argv.length < 3) {

var fs = require("fs")
, file = argv[2]
, readJson = require("../lib/utils/read-json")
, readJson = require("read-package-json")

readJson(file, function (er, data) {
if (er) throw er
@@ -129,29 +129,18 @@ Just send the error message back as the first argument to the callback.
Always create a new Error object with your message. Don't just return a
string message to the callback. Stack traces are handy.

Use the `require("./utils/log").er` function. It takes a callback and an
error message, and returns an object that will report the message in the
event of a failure. It's quite handy.

function myThing (args, cb) {
getData(args, function (er, data) {
if (er) return, "Couldn't get data")(er)
doSomethingElse(data, cb)
function justHasToWork (cb) {
doSomething(, "the doSomething failed."))

## Logging

Logging is done using the [npmlog](

Please clean up logs when they are no longer helpful. In particular,
logging the same object over and over again is not helpful. Logs should
report what's happening so that it's easier to track down where a fault

Use appropriate log levels. The default log() function logs at the
"info" level. See `npm-config(1)` and search for "loglevel".
Use appropriate log levels. See `npm-config(1)` and search for

## Case, naming, etc.

0 comments on commit ae5a209

Please sign in to comment.
You can’t perform that action at this time.