diff --git a/deps/npm/doc/cli/config.md b/deps/npm/doc/cli/config.md index 3deafce5f2..e48957ba82 100644 --- a/deps/npm/doc/cli/config.md +++ b/deps/npm/doc/cli/config.md @@ -36,11 +36,15 @@ work the same. `$HOME/.npmrc` (or the `userconfig` param, if set above) This file is an ini-file formatted list of `key = value` parameters. +Environment variables can be replaced using `${VARIABLE_NAME}`. For example: + + prefix = ${HOME}/.npm-packages ### Global config file `$PREFIX/etc/npmrc` (or the `globalconfig` param, if set above): -This file is an ini-file formatted list of `key = value` parameters +This file is an ini-file formatted list of `key = value` parameters. +Environment variables can be replaced as above. ### Built-in config file diff --git a/deps/npm/doc/cli/faq.md b/deps/npm/doc/cli/faq.md index 4c8367137d..d6cc041e4c 100644 --- a/deps/npm/doc/cli/faq.md +++ b/deps/npm/doc/cli/faq.md @@ -72,6 +72,52 @@ Write your own package manager, then. It's not that hard. npm will not help you do something that is known to be a bad idea. +## `"node_modules"` is the name of my deity's arch-rival, and a Forbidden Word in my religion. Can I configure npm to use a different folder? + +No. This will never happen. This question comes up sometimes, +because it seems silly from the outside that npm couldn't just be +configured to put stuff somewhere else, and then npm could load them +from there. It's an arbitrary spelling choice, right? What's the bg +deal? + +At the time of this writing, the string `'node_modules'` appears 151 +times in 53 separate files in npm and node core (excluding tests and +documentation). + +Some of these references are in node's built-in module loader. Since +npm is not involved **at all** at run-time, node itself would have to +be configured to know where you've decided to stick stuff. Complexity +hurdle #1. Since the Node module system is locked, this cannot be +changed, and is enough to kill this request. But I'll continue, in +deference to your deity's delicate feelings regarding spelling. + +Many of the others are in dependencies that npm uses, which are not +necessarily tightly coupled to npm (in the sense that they do not read +npm's configuration files, etc.) Each of these would have to be +configured to take the name of the `node_modules` folder as a +parameter. Complexity hurdle #2. + +Furthermore, npm has the ability to "bundle" dependencies by adding +the dep names to the `"bundledDependencies"` list in package.json, +which causes the folder to be included in the package tarball. What +if the author of a module bundles its dependencies, and they use a +different spelling for `node_modules`? npm would have to rename the +folder at publish time, and then be smart enough to unpack it using +your locally configured name. Complexity hurdle #3. + +Furthermore, what happens when you *change* this name? Fine, it's +easy enough the first time, just rename the `node_modules` folders to +`./blergyblerp/` or whatever name you choose. But what about when you +change it again? npm doesn't currently track any state about past +configuration settings, so this would be rather difficult to do +properly. It would have to track every previous value for this +config, and always accept any of them, or else yesterday's install may +be broken tomorrow. Complexity hurdle #5. + +Never going to happen. The folder is named `node_modules`. It is +written indelibly in the Node Way, handed down from the ancient times +of Node 0.3. + ## Should I check my `node_modules` folder into git? Mikeal Rogers answered this question very well: diff --git a/deps/npm/doc/cli/index.md b/deps/npm/doc/cli/index.md index 04852ce496..903812dc21 100644 --- a/deps/npm/doc/cli/index.md +++ b/deps/npm/doc/cli/index.md @@ -190,6 +190,10 @@ npm-index(1) -- Index of all npm documentation Mark your favorite packages +## npm-stars(1) + + View packages marked as favorites + ## npm-start(1) Start a package diff --git a/deps/npm/doc/cli/stars.md b/deps/npm/doc/cli/stars.md new file mode 100644 index 0000000000..7c28f5b2a5 --- /dev/null +++ b/deps/npm/doc/cli/stars.md @@ -0,0 +1,22 @@ +npm-stars(1) -- View packages marked as favorites +================================================= + +## SYNOPSIS + + npm stars + npm stars [username] + +## DESCRIPTION + +If you have starred a lot of neat things and want to find them again +quickly this command lets you do just that. + +You may also want to see your friend's favorite packages, in this case +you will most certainly enjoy this command. + +## SEE ALSO + +* npm-star(1) +* npm-view(1) +* npm-whoami(1) +* npm-adduser(1) diff --git a/deps/npm/doc/cli/update.md b/deps/npm/doc/cli/update.md index 1de49f2e2f..302e2efff8 100644 --- a/deps/npm/doc/cli/update.md +++ b/deps/npm/doc/cli/update.md @@ -3,7 +3,7 @@ npm-update(1) -- Update a package ## SYNOPSIS - npm update [ [ ...]] + npm update [-g] [ [ ...]] ## DESCRIPTION @@ -12,6 +12,9 @@ This command will update all the packages listed to the latest version It will also install missing packages. +If the `-g` flag is specified, this command will update globally installed packages. +If no package name is specified, all packages in the specified location (global or local) will be updated. + ## SEE ALSO * npm-install(1) diff --git a/deps/npm/doc/cli/version.md b/deps/npm/doc/cli/version.md index ca9b5fbfaa..74d938d6ba 100644 --- a/deps/npm/doc/cli/version.md +++ b/deps/npm/doc/cli/version.md @@ -27,7 +27,16 @@ resulting version number. For example: If the `sign-git-tag` config is set, then the tag will be signed using the `-s` flag to git. Note that you must have a default GPG key set up -in your git config for this to work properly. +in your git config for this to work properly. For example: + + $ npm config set sign-git-tag true + $ npm version patch + + You need a passphrase to unlock the secret key for + user: "isaacs (http://blog.izs.me/) " + 2048-bit RSA key, ID 6C481CF6, created 2010-08-31 + + Enter passphrase: ## SEE ALSO diff --git a/deps/npm/html/api/bin.html b/deps/npm/html/api/bin.html index 53761a1e83..762ed898d6 100644 --- a/deps/npm/html/api/bin.html +++ b/deps/npm/html/api/bin.html @@ -19,7 +19,7 @@

This function should not be used programmatically. Instead, just refer to the npm.bin member.

- + + diff --git a/deps/npm/html/doc/start.html b/deps/npm/html/doc/start.html index 3e6aa1ca64..4a42ee1e1a 100644 --- a/deps/npm/html/doc/start.html +++ b/deps/npm/html/doc/start.html @@ -20,7 +20,7 @@ - +