1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge remote branch 'origin/v0.6'

Browse Source 
Conflicts:
	Makefile
	configure
	src/node_version.h
This commit is contained in:
Ryan Dahl 2012-01-09 11:20:22 -08:00
commit 8b28d599a7
229 changed files with 1132 additions and 472 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
AUTHORS
View File

@ -244,3 +244,12 @@ Kyle Robinson Young <kyle@dontkry.com>
Tim Oxley <secoif@gmail.com>
Ingmar Runge <ingmar@irsoft.de>
Russ Bradberry <rbradberry@gmail.com>
Andreas Madsen <amwebdk@gmail.com>
Adam Malcontenti-Wilson <adman.com@gmail.com>
James Hartig <james.hartig@grooveshark.com>
Shannen Saez <shannenlaptop@gmail.com>
Seong-Rak Choi <ragiragi@hanmail.net>
Dave Irvine <davman99@gmail.com>
Ju-yeong Park <interruptz@gmail.com>
Phil Sung <psung@dnanexus.com>
Damon Oehlman <damon.oehlman@sidelab.com>

42
ChangeLog
View File

@ -1,4 +1,44 @@
2011.12.14, Version 0.6.6 (stable)
2012.01.06, Version 0.6.7 (stable)
* V8 hash collision fix (Breaks MIPS) (Bert Belder, Erik Corry)
* Upgrade V8 to 3.6.6.15
* Upgrade npm to 1.1.0-beta-10 (isaacs)
* many doc updates (Ben Noordhuis, Jeremy Martin, koichik, Dave Irvine,
Seong-Rak Choi, Shannen, Adam Malcontenti-Wilson, koichik)
* Fix segfault in node_http_parser.cc
* dgram, timers: fix memory leaks (Ben Noordhuis, Yoshihiro Kikuchi)
* repl: fix repl.start not passing the `ignoreUndefined` arg (Damon Oehlman)
* #1980: Socket.pause null reference when called on a closed Stream (koichik)
* #2263: XMLHttpRequest piped in a writable file stream hang (koichik)
* #2069: http resource leak (koichik)
* buffer.readInt global pollution fix (Phil Sung)
* timers: fix performance regression (Ben Noordhuis)
* #2308, #2246: node swallows openssl error on request (koichik)
* #2114: timers: remove _idleTimeout from item in .unenroll() (James Hartig)
* #2379: debugger: Request backtrace w/o refs (Fedor Indutny)
* simple DTrace ustack helper (Dave Pacheco)
* crypto: rewrite HexDecode without snprintf (Roman Shtylman)
* crypto: don't ignore DH init errors (Ben Noordhuis)
2011.12.14, Version 0.6.6
* npm update to 1.1.0-beta-4 (Isaac Z. Schlueter)

47
Makefile
View File

@ -1,4 +1,5 @@
BUILDTYPE ?= Release
PYTHON ?= python
ifeq ($(BUILDTYPE),Release)
all: out/Makefile node
@ -38,41 +39,41 @@ distclean:
-rm config.gypi
test: all
python tools/test.py --mode=release simple message
$(PYTHON) tools/test.py --mode=release simple message
test-http1: all
python tools/test.py --mode=release --use-http1 simple message
$(PYTHON) tools/test.py --mode=release --use-http1 simple message
test-valgrind: all
python tools/test.py --mode=release --valgrind simple message
$(PYTHON) tools/test.py --mode=release --valgrind simple message
test-all: all
python tools/test.py --mode=debug,release
$(MAKE) test-npm
test-all-http1: all
python tools/test.py --mode=debug,release --use-http1
$(PYTHON) tools/test.py --mode=debug,release --use-http1
test-all-valgrind: all
python tools/test.py --mode=debug,release --valgrind
$(PYTHON) tools/test.py --mode=debug,release --valgrind
test-release: all
python tools/test.py --mode=release
$(PYTHON) tools/test.py --mode=release
test-debug: all
python tools/test.py --mode=debug
$(PYTHON) tools/test.py --mode=debug
test-message: all
python tools/test.py message
$(PYTHON) tools/test.py message
test-simple: all
python tools/test.py simple
$(PYTHON) tools/test.py simple
test-pummel: all
python tools/test.py pummel
$(PYTHON) tools/test.py pummel
test-internet: all
python tools/test.py internet
$(PYTHON) tools/test.py internet
test-npm: node
./node deps/npm/test/run.js
@ -138,11 +139,25 @@ docopen: out/doc/api/all.html
docclean:
-rm -rf out/doc
VERSION=$(shell git describe)
VERSION=v$(shell $(PYTHON) tools/getnodeversion.py)
TARNAME=node-$(VERSION)
#dist: doc/node.1 doc/api
dist: doc
dist: $(TARBALL) $(PKG)
PKGDIR=out/dist-osx
pkg: $(PKG)
$(PKG):
-rm -rf $(PKGDIR)
$(WAF) configure --prefix=/usr/local --without-snapshot
DESTDIR=$(PKGDIR) $(WAF) install
$(packagemaker) \
--id "org.nodejs.NodeJS-$(VERSION)" \
--doc tools/osx-pkg.pmdoc \
--out $(PKG)
$(TARBALL): out/doc
git archive --format=tar --prefix=$(TARNAME)/ HEAD | tar xf -
mkdir -p $(TARNAME)/doc
cp doc/node.1 $(TARNAME)/doc/node.1
@ -162,10 +177,10 @@ bench-idle:
./node benchmark/idle_clients.js &
jslint:
PYTHONPATH=tools/closure_linter/ python tools/closure_linter/closure_linter/gjslint.py --unix_mode --strict --nojsdoc -r lib/ -r src/ -r test/
PYTHONPATH=tools/closure_linter/ $(PYTHON) tools/closure_linter/closure_linter/gjslint.py --unix_mode --strict --nojsdoc -r lib/ -r src/ -r test/
cpplint:
@python tools/cpplint.py $(wildcard src/*.cc src/*.h src/*.c)
@$(PYTHON) tools/cpplint.py $(wildcard src/*.cc src/*.h src/*.c)
lint: jslint cpplint

2
README.md
View File

@ -3,7 +3,7 @@ Evented I/O for V8 javascript. [![Build Status](https://secure.travis-ci.org/joy
### To build:
Unix/Macintosh (requires python >= 2.5.2):
Unix/Macintosh (requires python 2.6 or 2.7):
./configure
make

17
deps/npm/Makefile vendored
View File

@ -108,18 +108,29 @@ version: link
git add package.json &&\
git ci -m v$(shell npm -v)
publish: link
publish: link doc
git tag -d v$(shell npm -v) || true
git push origin :v$(shell npm -v) || true
npm unpublish npm@$(shell npm -v) || true
git tag -s -m v$(shell npm -v) v$(shell npm -v) &&\
git push origin --tags &&\
npm publish &&\
make doc-publish
npm tag npm@$(shell npm -v) $(shell npm -v | awk -F. '{print $$1 "." $$2}') &&\
make doc-publish &&\
make zip-publish
docpublish: doc-publish
doc-publish: doc
rsync -vazu --stats --no-implied-dirs --delete html/doc/ npmjs.org:/var/www/npmjs.org/public/doc
rsync -vazu --stats --no-implied-dirs --delete html/api/ npmjs.org:/var/www/npmjs.org/public/api
zip-publish: release
scp release/*.zip npmjs.org:/var/www/npmjs.org/public/dist/
release:
@bash scripts/release.sh
sandwich:
@[ $$(whoami) = "root" ] && (echo "ok"; echo "ham" > sandwich) || echo "make it yourself"
.PHONY: all latest install dev link doc clean uninstall test man doc-publish doc-clean docclean docpublish
.PHONY: all latest install dev link doc clean uninstall test man doc-publish doc-clean docclean docpublish release zip-publish

84
deps/npm/doc/cli/disputes.md vendored Normal file
View File

@ -0,0 +1,84 @@
npm-disputes(1) -- Handling Module Name Disputes
================================================
## SYNOPSIS
1. Get the author email with `npm owner ls <pkgname>`
1. Email the author, CC <i@izs.me>.
2. After a few weeks, if there's no resolution, we'll sort it out.
## DESCRIPTION
There sometimes arise cases where a user publishes a module, and then
later, some other user wants to use that name. Here are some common
ways that happens (each of these is based on actual events.)
1. Bob writes a JavaScript module `foo`, which is not node-specific.
Bob doesn't use node at all. Joe wants to use `foo` in node, so he
wraps it in an npm module. Some time later, Bob starts using node,
and wants to take over management of his program.
2. Bob writes an npm module `foo`, and publishes it. Perhaps much
later, Joe finds a bug in `foo`, and fixes it. He sends a pull
request to Bob, but Bob doesn't have the time to deal with it,
because he has a new job and a new baby and is focused on his new
erlang project, and kind of not involved with node any more. Joe
would like to publish a new `foo`, but can't, because the name is
taken.
3. Bob writes a 10-line flow-control library, and calls it `foo`, and
publishes it to the npm registry. Being a simple little thing, it
never really has to be updated. Joe works for Foo Inc, the makers
of the critically acclaimed and widely-marketed `foo` JavaScript
toolkit framework. They publish it to npm as `foojs`, but people are
routinely confused when `npm install foo` is some different thing.
4. Bob writes a parser for the widely-known `foo` file format, because
he needs it for work. Then, he gets a new job, and never updates the
prototype. Later on, Joe writes a much more complete `foo` parser,
but can't publish, because Bob's `foo` is in the way.
The validity of Joe's claim in each situation can be debated. However,
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 respecfully as possible**,
and what he would like to do with the module name. He adds
isaacs <i@izs.me> 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
<i@izs.me> and we'll sort it out.
## REASONING
In almost every case so far, the parties involved have been able to reach
an amicable resolution without any major intervention. Most people
really do want to be reasonable, and are probably not even aware that
they're in your way.
Module ecosystems are most vibrant and powerful when they are as
self-directed as possible. If an admin one day deletes something you
had worked on, then that is going to make most people quite upset,
regardless of the justification. When humans solve their problems by
talking to other humans with respect, everyone has the chance to end up
feeling good about the interaction.
## EXCEPTIONS
Some things are not allowed, and will be removed without discussion if
they are brought to the attention of the npm registry admins, including
but not limited to:
1. Malware (that is, a module designed to exploit or harm the machine on
which it is installed)
2. Violations of copyright or licenses (for example, cloning an
MIT-licensed program, and then removing or changing the copyright and
license statement)
3. Illegal content.
If you see bad behavior like this, please report it right away.
## SEE ALSO
* npm-registry(1)
* npm-owner(1)

66
deps/npm/doc/cli/faq.md vendored
View File

@ -32,35 +32,65 @@ tl;dr:
something with the `-g` flag, then its executables go in `npm bin -g`
and its modules go in `npm root -g`.
## How do I install something everywhere?
## How do I install something on my computer in a central location?
Install it globally by tacking `-g` or `--global` to the command.
Install it globally by tacking `-g` or `--global` to the command. (This
is especially important for command line utilities that need to add
their bins to the global system `PATH`.)
## I installed something globally, but I can't `require()` it
Install it locally.
## I don't wanna.
The global install location is a place for command-line utilities
to put their bins in the system `PATH`. It's not for use with `require()`.
Check out `npm link`. You might like it.
If you `require()` a module in your code, then that means it's a
dependency, and a part of your program. You need to install it locally
in your program.
## No, I really want 0.x style 'everything global' style.
## Why can't npm just put everything in one place, like other package managers?
Ok, fine. Do this:
Not every change is an improvement, but every improvement is a change.
This would be like asking git to do network IO for every commit. It's
not going to happen, because it's a terrible idea that causes more
problems than it solves.
echo 'export NODE_PATH="'$(npm root -g)'"' >> ~/.bashrc
. ~/.bashrc
npm config set global true
It is much harder to avoid dependency conflicts without nesting
dependencies. This is fundamental to the way that npm works, and has
proven to be an extremely successful approach. See `npm-folders(1)` for
more details.
This is not recommended.
If you want a package to be installed in one place, and have all your
programs reference the same copy of it, then use the `npm link` command.
That's what it's for. Install it globally, then link it into each
program that uses it.
Many things **will not work** if you do this. Make sure you read and
understand `npm-config(1)` and `npm-global(1)` before you complain
about things being broken.
## Whatever, I really want the old style 'everything global' style.
When you realize what a mistake it was, do this to switch back:
Write your own package manager, then. It's not that hard.
npm config delete global --local
npm will not help you do something that is known to be a bad idea.
## Should I check my `node_modules` folder into git?
Mikeal Rogers answered this question very well:
<http://www.mikealrogers.com/posts/nodemodules-in-git.html>
tl;dr
* Check `node_modules` into git for things you **deploy**, such as
websites and apps.
* Do not check `node_modules` into git for libraries and modules
intended to be reused.
* Use npm to manage dependencies in your dev environment, but not in
your deployment scripts.
## Is it 'npm' or 'NPM' or 'Npm'?
npm should never be capitalized unless it is being displayed in a
location that is customarily all-caps (such as the title of man pages.)
## If 'npm' is an acronym, why is it never capitalized?
@ -73,7 +103,7 @@ acronym, and thus incorrectly named.)
National Association of Pastoral Musicians. You can learn more
about them at <http://npm.org/>.
In software, "NPM" is a non-parametric mapping utility written by
In software, "NPM" is a Non-Parametric Mapping utility written by
Chris Rorden. You can analyze pictures of brains with it. Learn more
about the (capitalized) NPM program at <http://www.cabiatl.com/mricro/npm/>.
@ -186,11 +216,9 @@ Go to <http://admin.npmjs.org/reset>.
## I get ECONNREFUSED a lot. What's up?
Either the registry is down, or node's DNS isn't able to reach out.
This happens a lot if you don't follow *all* the steps in the Cygwin
setup doc.
To check if the registry is down, open up
<http://registry.npmjs.org/-/short>
<http://registry.npmjs.org/>
in a web browser. This will also tell you if you are just unable to
access the internet for some reason.

4
deps/npm/doc/cli/index.md vendored
View File

@ -54,6 +54,10 @@ npm-index(1) -- Index of all npm documentation
Developer Guide
## npm-disputes(1)
Handling Module Name Disputes
## npm-docs(1)
Docs for a package in a web browser maybe

1
deps/npm/doc/cli/owner.md vendored
View File

@ -30,3 +30,4 @@ that is not implemented at this time.
* npm-publish(1)
* npm-registry(1)
* npm-adduser(1)
* npm-disputes(1)

1
deps/npm/doc/cli/registry.md vendored
View File

@ -90,3 +90,4 @@ Stay tuned!
* npm-config(1)
* npm-developers(1)
* npm-disputes(1)

2
deps/npm/html/api/bin.html vendored
View File

@ -19,7 +19,7 @@
<p>This function should not be used programmatically. Instead, just refer
to the <code>npm.bin</code> member.</p>
</div>
<p id="footer">bin &mdash; npm@1.1.0-beta-7</p>
<p id="footer">bin &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/bugs.html vendored
View File

@ -25,7 +25,7 @@ optional version number.</p>
<p>This command will launch a browser, so this command may not be the most
friendly for programmatic use.</p>
</div>
<p id="footer">bugs &mdash; npm@1.1.0-beta-7</p>
<p id="footer">bugs &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/commands.html vendored
View File

@ -28,7 +28,7 @@ usage, or <code>man 3 npm-&lt;command&gt;</code> for programmatic usage.</p>
<ul><li><a href="../doc/index.html">index(1)</a></li></ul>
</div>
<p id="footer">commands &mdash; npm@1.1.0-beta-7</p>
<p id="footer">commands &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/config.html vendored
View File

@ -33,7 +33,7 @@ functions instead.</p>
<ul><li><a href="../api/npm.html">npm(3)</a></li></ul>
</div>
<p id="footer">config &mdash; npm@1.1.0-beta-7</p>
<p id="footer">config &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/deprecate.html vendored
View File

@ -30,7 +30,7 @@ install the package.</p></li></ul>
<ul><li><a href="../api/publish.html">publish(3)</a></li><li><a href="../api/unpublish.html">unpublish(3)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">deprecate &mdash; npm@1.1.0-beta-7</p>
<p id="footer">deprecate &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/docs.html vendored
View File

@ -25,7 +25,7 @@ optional version number.</p>
<p>This command will launch a browser, so this command may not be the most
friendly for programmatic use.</p>
</div>
<p id="footer">docs &mdash; npm@1.1.0-beta-7</p>
<p id="footer">docs &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/edit.html vendored
View File

@ -30,7 +30,7 @@ to open. The package can optionally have a version number attached.</p>
<p>Since this command opens an editor in a new process, be careful about where
and how this is used.</p>
</div>
<p id="footer">edit &mdash; npm@1.1.0-beta-7</p>
<p id="footer">edit &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/explore.html vendored
View File

@ -24,7 +24,7 @@ sure to use <code>npm rebuild &lt;pkg&gt;</code> if you make any changes.</p>
<p>The first element in the 'args' parameter must be a package name. After that is the optional command, which can be any number of strings. All of the strings will be combined into one, space-delimited command.</p>
</div>
<p id="footer">explore &mdash; npm@1.1.0-beta-7</p>
<p id="footer">explore &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/help-search.html vendored
View File

@ -32,7 +32,7 @@ Name of the file that matched</li></ul>
<p>The silent parameter is not neccessary not used, but it may in the future.</p>
</div>
<p id="footer">help-search &mdash; npm@1.1.0-beta-7</p>
<p id="footer">help-search &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/init.html vendored
View File

@ -35,7 +35,7 @@ then go ahead and use this programmatically.</p>
<p><a href="../doc/json.html">json(1)</a></p>
</div>
<p id="footer">init &mdash; npm@1.1.0-beta-7</p>
<p id="footer">init &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/install.html vendored
View File

@ -25,7 +25,7 @@ the name of a package to be installed.</p>
<p>Finally, 'callback' is a function that will be called when all packages have been
installed or when an error has been encountered.</p>
</div>
<p id="footer">install &mdash; npm@1.1.0-beta-7</p>
<p id="footer">install &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/link.html vendored
View File

@ -39,7 +39,7 @@ npm.commands.link('redis', cb) # link-install the package</code></pre>
<p>Now, any changes to the redis package will be reflected in
the package in the current working directory</p>
</div>
<p id="footer">link &mdash; npm@1.1.0-beta-7</p>
<p id="footer">link &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/load.html vendored
View File

@ -32,7 +32,7 @@ config object.</p>
<p>For a list of all the available command-line configs, see <code>npm help config</code></p>
</div>
<p id="footer">load &mdash; npm@1.1.0-beta-7</p>
<p id="footer">load &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/ls.html vendored
View File

@ -53,7 +53,7 @@ project.</p>
This means that if a submodule a same dependency as a parent module, then the
dependency will only be output once.</p>
</div>
<p id="footer">ls &mdash; npm@1.1.0-beta-7</p>
<p id="footer">ls &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/api/npm.html vendored
View File

@ -24,7 +24,7 @@ npm.load(configObject, function (er, npm) {
<h2 id="VERSION">VERSION</h2>
<p>1.1.0-beta-7</p>
<p>1.1.0-beta-10</p>
<h2 id="DESCRIPTION">DESCRIPTION</h2>
@ -91,7 +91,7 @@ method names. Use the <code>npm.deref</code> method to find the real name.</p>
<pre><code>var cmd = npm.deref("unp") // cmd === "unpublish"</code></pre>
</div>
<p id="footer">npm &mdash; npm@1.1.0-beta-7</p>
<p id="footer">npm &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/outdated.html vendored
View File

@ -19,7 +19,7 @@ currently outdated.</p>
<p>If the 'packages' parameter is left out, npm will check all packages.</p>
</div>
<p id="footer">outdated &mdash; npm@1.1.0-beta-7</p>
<p id="footer">outdated &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/owner.html vendored
View File

@ -34,7 +34,7 @@ that is not implemented at this time.</p>
<ul><li><a href="../api/publish.html">publish(3)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">owner &mdash; npm@1.1.0-beta-7</p>
<p id="footer">owner &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/pack.html vendored
View File

@ -25,7 +25,7 @@ overwritten the second time.</p>
<p>If no arguments are supplied, then npm packs the current package folder.</p>
</div>
<p id="footer">pack &mdash; npm@1.1.0-beta-7</p>
<p id="footer">pack &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/prefix.html vendored
View File

@ -21,7 +21,7 @@
<p>This function is not useful programmatically</p>
</div>
<p id="footer">prefix &mdash; npm@1.1.0-beta-7</p>
<p id="footer">prefix &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/prune.html vendored
View File

@ -23,7 +23,7 @@
<p>Extraneous packages are packages that are not listed on the parent
package's dependencies list.</p>
</div>
<p id="footer">prune &mdash; npm@1.1.0-beta-7</p>
<p id="footer">prune &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/publish.html vendored
View File

@ -32,7 +32,7 @@ the registry. Overwrites when the "force" environment variable is set.</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../api/owner.html">owner(3)</a></li></ul>
</div>
<p id="footer">publish &mdash; npm@1.1.0-beta-7</p>
<p id="footer">publish &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/rebuild.html vendored
View File

@ -22,7 +22,7 @@ the new binary. If no 'packages' parameter is specify, every package will be reb
<p>See <code>npm help build</code></p>
</div>
<p id="footer">rebuild &mdash; npm@1.1.0-beta-7</p>
<p id="footer">rebuild &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/restart.html vendored
View File

@ -27,7 +27,7 @@ in the <code>packages</code> parameter.</p>
<ul><li><a href="../api/start.html">start(3)</a></li><li><a href="../api/stop.html">stop(3)</a></li></ul>
</div>
<p id="footer">restart &mdash; npm@1.1.0-beta-7</p>
<p id="footer">restart &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/root.html vendored
View File

@ -21,7 +21,7 @@
<p>This function is not useful programmatically.</p>
</div>
<p id="footer">root &mdash; npm@1.1.0-beta-7</p>
<p id="footer">root &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/run-script.html vendored
View File

@ -29,7 +29,7 @@ assumed to be the command to run. All other elements are ignored.</p>
<ul><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../api/test.html">test(3)</a></li><li><a href="../api/start.html">start(3)</a></li><li><a href="../api/restart.html">restart(3)</a></li><li><a href="../api/stop.html">stop(3)</a></li></ul>
</div>
<p id="footer">run-script &mdash; npm@1.1.0-beta-7</p>
<p id="footer">run-script &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/search.html vendored
View File

@ -32,7 +32,7 @@ excluded term (the "searchexclude" config). The search is case insensitive
and doesn't try to read your mind (it doesn't do any verb tense matching or the
like).</p>
</div>
<p id="footer">search &mdash; npm@1.1.0-beta-7</p>
<p id="footer">search &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/start.html vendored
View File

@ -19,7 +19,7 @@
<p>npm can run tests on multiple packages. Just specify multiple packages
in the <code>packages</code> parameter.</p>
</div>
<p id="footer">start &mdash; npm@1.1.0-beta-7</p>
<p id="footer">start &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/stop.html vendored
View File

@ -19,7 +19,7 @@
<p>npm can run stop on multiple packages. Just specify multiple packages
in the <code>packages</code> parameter.</p>
</div>
<p id="footer">stop &mdash; npm@1.1.0-beta-7</p>
<p id="footer">stop &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/submodule.html vendored
View File

@ -33,7 +33,7 @@ dependencies into the submodule folder.</p>
<ul><li>npm help json</li><li>git help submodule</li></ul>
</div>
<p id="footer">submodule &mdash; npm@1.1.0-beta-7</p>
<p id="footer">submodule &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/tag.html vendored
View File

@ -29,7 +29,7 @@ parameter is missing or falsey (empty), the default froom the config will be
used. For more information about how to set this config, check
<code>man 3 npm-config</code> for programmatic usage or <code>man npm-config</code> for cli usage.</p>
</div>
<p id="footer">tag &mdash; npm@1.1.0-beta-7</p>
<p id="footer">tag &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/test.html vendored
View File

@ -22,7 +22,7 @@ true.</p>
<p>npm can run tests on multiple packages. Just specify multiple packages
in the <code>packages</code> parameter.</p>
</div>
<p id="footer">test &mdash; npm@1.1.0-beta-7</p>
<p id="footer">test &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/uninstall.html vendored
View File

@ -22,7 +22,7 @@ the name of a package to be uninstalled.</p>
<p>Finally, 'callback' is a function that will be called when all packages have been
uninstalled or when an error has been encountered.</p>
</div>
<p id="footer">uninstall &mdash; npm@1.1.0-beta-7</p>
<p id="footer">uninstall &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/unpublish.html vendored
View File

@ -26,7 +26,7 @@ is what is meant.</p>
<p>If no version is specified, or if all versions are removed then
the root package entry is removed from the registry entirely.</p>
</div>
<p id="footer">unpublish &mdash; npm@1.1.0-beta-7</p>
<p id="footer">unpublish &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/update.html vendored
View File

@ -18,7 +18,7 @@
<p>The 'packages' argument is an array of packages to update. The 'callback' parameter will be called when done or when an error occurs.</p>
</div>
<p id="footer">update &mdash; npm@1.1.0-beta-7</p>
<p id="footer">update &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/version.html vendored
View File

@ -24,7 +24,7 @@ fail if the repo is not clean.</p>
parameter. The difference, however, is this function will fail if it does
not have exactly one element. The only element should be a version number.</p>
</div>
<p id="footer">version &mdash; npm@1.1.0-beta-7</p>
<p id="footer">version &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/view.html vendored
View File

@ -99,7 +99,7 @@ the field name.</p>
<p>corresponding to the list of fields selected.</p>
</div>
<p id="footer">view &mdash; npm@1.1.0-beta-7</p>
<p id="footer">view &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/api/whoami.html vendored
View File

@ -21,7 +21,7 @@
<p>This function is not useful programmatically</p>
</div>
<p id="footer">whoami &mdash; npm@1.1.0-beta-7</p>
<p id="footer">whoami &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/README.html vendored
View File

@ -267,7 +267,7 @@ will no doubt tell you to put the output in a gist or email.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/index.html">index(1)</a></li></ul>
</div>
<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.1.0-beta-7</p>
<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/adduser.html vendored
View File

@ -39,7 +39,7 @@ authorize on a new machine.</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li><li><a href="../doc/whoami.html">whoami(1)</a></li></ul>
</div>
<p id="footer">adduser &mdash; npm@1.1.0-beta-7</p>
<p id="footer">adduser &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/bin.html vendored
View File

@ -20,7 +20,7 @@
<ul><li><a href="../doc/prefix.html">prefix(1)</a></li><li><a href="../doc/root.html">root(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">bin &mdash; npm@1.1.0-beta-7</p>
<p id="footer">bin &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/bugs.html vendored
View File

@ -36,7 +36,7 @@ config param.</p>
<ul><li><a href="../doc/docs.html">docs(1)</a></li><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">bugs &mdash; npm@1.1.0-beta-7</p>
<p id="footer">bugs &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/build.html vendored
View File

@ -25,7 +25,7 @@ A folder containing a <code>package.json</code> file in its root.</li></ul>
<ul><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">build &mdash; npm@1.1.0-beta-7</p>
<p id="footer">build &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/bundle.html vendored
View File

@ -20,7 +20,7 @@ install packages into the local space.</p>
<ul><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">bundle &mdash; npm@1.1.0-beta-7</p>
<p id="footer">bundle &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/cache.html vendored
View File

@ -66,7 +66,7 @@ they do not make an HTTP request to the registry.</p>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/pack.html">pack(1)</a></li></ul>
</div>
<p id="footer">cache &mdash; npm@1.1.0-beta-7</p>
<p id="footer">cache &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/changelog.html vendored
View File

@ -34,7 +34,7 @@
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li></ul>
</div>
<p id="footer">changelog &mdash; npm@1.1.0-beta-7</p>
<p id="footer">changelog &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/coding-style.html vendored
View File

@ -191,7 +191,7 @@ set to anything."</p>
<ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
</div>
<p id="footer">coding-style &mdash; npm@1.1.0-beta-7</p>
<p id="footer">coding-style &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/completion.html vendored
View File

@ -33,7 +33,7 @@ completions based on the arguments.</p>
<ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
</div>
<p id="footer">completion &mdash; npm@1.1.0-beta-7</p>
<p id="footer">completion &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/config.html vendored
View File

@ -615,7 +615,7 @@ then answer "no" to any prompt.</p>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li></ul>
</div>
<p id="footer">config &mdash; npm@1.1.0-beta-7</p>
<p id="footer">config &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/deprecate.html vendored
View File

@ -29,7 +29,7 @@ something like this:</p>
<ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">deprecate &mdash; npm@1.1.0-beta-7</p>
<p id="footer">deprecate &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/developers.html vendored
View File

@ -150,7 +150,7 @@ from a fresh checkout.</p>
<ul><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li></ul>
</div>
<p id="footer">developers &mdash; npm@1.1.0-beta-7</p>
<p id="footer">developers &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

115
deps/npm/html/doc/disputes.html vendored Normal file
View File

@ -0,0 +1,115 @@
<!doctype html>
<html>
<title>disputes</title>
<meta http-equiv="content-type" value="text/html;utf-8">
<link rel="stylesheet" type="text/css" href="./style.css">
<body>
<div id="wrapper">
<h1><a href="../doc/disputes.html">disputes</a></h1> <p>Handling Module Name Disputes</p>
<h2 id="SYNOPSIS">SYNOPSIS</h2>
<ol><li>Get the author email with <code>npm owner ls &lt;pkgname&gt;</code></li><li>Email the author, CC <a href="mailto:i@izs.me">i@izs.me</a>.</li><li>After a few weeks, if there's no resolution, we'll sort it out.</li></ol>
<h2 id="DESCRIPTION">DESCRIPTION</h2>
<p>There sometimes arise cases where a user publishes a module, and then
later, some other user wants to use that name. Here are some common
ways that happens (each of these is based on actual events.)</p>
<ol><li>Bob writes a JavaScript module <code>foo</code>, which is not node-specific.
Bob doesn't use node at all. Joe wants to use <code>foo</code> in node, so he
wraps it in an npm module. Some time later, Bob starts using node,
and wants to take over management of his program.</li><li>Bob writes an npm module <code>foo</code>, and publishes it. Perhaps much
later, Joe finds a bug in <code>foo</code>, and fixes it. He sends a pull
request to Bob, but Bob doesn't have the time to deal with it,
because he has a new job and a new baby and is focused on his new
erlang project, and kind of not involved with node any more. Joe
would like to publish a new <code>foo</code>, but can't, because the name is
taken.</li><li>Bob writes a 10-line flow-control library, and calls it <code>foo</code>, and
publishes it to the npm registry. Being a simple little thing, it
never really has to be updated. Joe works for Foo Inc, the makers
of the critically acclaimed and widely-marketed <code>foo</code> JavaScript
toolkit framework. They publish it to npm as <code>foojs</code>, but people are
routinely confused when <code>npm install foo</code> is some different thing.</li><li>Bob writes a parser for the widely-known <code>foo</code> file format, because
he needs it for work. Then, he gets a new job, and never updates the
prototype. Later on, Joe writes a much more complete <code>foo</code> parser,
but can't publish, because Bob's <code>foo</code> is in the way.</li></ol>
<p>The validity of Joe's claim in each situation can be debated. However,
Joe's appropriate course of action in each case is the same.</p>
<ol><li><code>npm owner ls foo</code>. This will tell Joe the email address of the
owner (Bob).</li><li>Joe emails Bob, explaining the situation <strong>as respecfully as possible</strong>,
and what he would like to do with the module name. He adds
isaacs <a href="mailto:i@izs.me">i@izs.me</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 isaacs
<a href="mailto:i@izs.me">i@izs.me</a> and we'll sort it out.</li></ol>
<h2 id="REASONING">REASONING</h2>
<p>In almost every case so far, the parties involved have been able to reach
an amicable resolution without any major intervention. Most people
really do want to be reasonable, and are probably not even aware that
they're in your way.</p>
<p>Module ecosystems are most vibrant and powerful when they are as
self-directed as possible. If an admin one day deletes something you
had worked on, then that is going to make most people quite upset,
regardless of the justification. When humans solve their problems by
talking to other humans with respect, everyone has the chance to end up
feeling good about the interaction.</p>
<h2 id="EXCEPTIONS">EXCEPTIONS</h2>
<p>Some things are not allowed, and will be removed without discussion if
they are brought to the attention of the npm registry admins, including
but not limited to:</p>
<ol><li>Malware (that is, a module designed to exploit or harm the machine on
which it is installed)</li><li>Violations of copyright or licenses (for example, cloning an
MIT-licensed program, and then removing or changing the copyright and
license statement)</li><li>Illegal content.</li></ol>
<p>If you see bad behavior like this, please report it right away.</p>
<h2 id="SEE-ALSO">SEE ALSO</h2>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li></ul>
</div>
<p id="footer">disputes &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")
var els = Array.prototype.slice.call(wrapper.getElementsByTagName("*"), 0)
.filter(function (el) {
return el.parentNode === wrapper
&& el.tagName.match(/H[1-6]/)
&& el.id
})
var l = 2
, toc = document.createElement("ul")
toc.innerHTML = els.map(function (el) {
var i = el.tagName.charAt(1)
, out = ""
while (i > l) {
out += "<ul>"
l ++
}
while (i < l) {
out += "</ul>"
l --
}
out += "<li><a href='#" + el.id + "'>" +
( el.innerText || el.text || el.innerHTML)
+ "</a>"
return out
}).join("\n")
toc.id = "toc"
document.body.appendChild(toc)
})()
</script>
</body></html>

2
deps/npm/html/doc/docs.html vendored
View File

@ -37,7 +37,7 @@ config param.</p>
<ul><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">docs &mdash; npm@1.1.0-beta-7</p>
<p id="footer">docs &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/edit.html vendored
View File

@ -37,7 +37,7 @@ or <code>"notepad"</code> on Windows.</li><li>Type: path</li></ul>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/explore.html">explore(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">edit &mdash; npm@1.1.0-beta-7</p>
<p id="footer">edit &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/explore.html vendored
View File

@ -40,7 +40,7 @@ Windows</li><li>Type: path</li></ul>
<ul><li><a href="../doc/submodule.html">submodule(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/edit.html">edit(1)</a></li><li><a href="../doc/rebuild.html">rebuild(1)</a></li><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">explore &mdash; npm@1.1.0-beta-7</p>
<p id="footer">explore &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

68
deps/npm/html/doc/faq.html vendored
View File

@ -38,35 +38,63 @@ command to see where executables go</li><li>Global installs are different from l
something with the <code>-g</code> flag, then its executables go in <code>npm bin -g</code>
and its modules go in <code>npm root -g</code>.</li></ul>
<h2 id="How-do-I-install-something-everywhere">How do I install something everywhere?</h2>
<h2 id="How-do-I-install-something-on-my-computer-in-a-central-location">How do I install something on my computer in a central location?</h2>
<p>Install it globally by tacking <code>-g</code> or <code>--global</code> to the command.</p>
<p>Install it globally by tacking <code>-g</code> or <code>--global</code> to the command. (This
is especially important for command line utilities that need to add
their bins to the global system <code>PATH</code>.)</p>
<h2 id="I-installed-something-globally-but-I-can-t-require-it">I installed something globally, but I can't `require()` it</h2>
<p>Install it locally.</p>
<h2 id="I-don-t-wanna">I don't wanna.</h2>
<p>The global install location is a place for command-line utilities
to put their bins in the system <code>PATH</code>. It's not for use with <code>require()</code>.</p>
<p>Check out <code>npm link</code>. You might like it.</p>
<p>If you <code>require()</code> a module in your code, then that means it's a
dependency, and a part of your program. You need to install it locally
in your program.</p>
<h2 id="No-I-really-want-0-x-style-everything-global-style">No, I really want 0.x style 'everything global' style.</h2>
<h2 id="Why-can-t-npm-just-put-everything-in-one-place-like-other-package-managers">Why can't npm just put everything in one place, like other package managers?</h2>
<p>Ok, fine. Do this:</p>
<p>Not every change is an improvement, but every improvement is a change.
This would be like asking git to do network IO for every commit. It's
not going to happen, because it's a terrible idea that causes more
problems than it solves.</p>
<pre><code>echo 'export NODE_PATH="'$(npm root -g)'"' &gt;&gt; ~/.bashrc
. ~/.bashrc
npm config set global true</code></pre>
<p>It is much harder to avoid dependency conflicts without nesting
dependencies. This is fundamental to the way that npm works, and has
proven to be an extremely successful approach. See <code><a href="../doc/folders.html">folders(1)</a></code> for
more details.</p>
<p>This is not recommended.</p>
<p>If you want a package to be installed in one place, and have all your
programs reference the same copy of it, then use the <code>npm link</code> command.
That's what it's for. Install it globally, then link it into each
program that uses it.</p>
<p>Many things <strong>will not work</strong> if you do this. Make sure you read and
understand <code><a href="../doc/config.html">config(1)</a></code> and <code><a href="../doc/global.html">global(1)</a></code> before you complain
about things being broken.</p>
<h2 id="Whatever-I-really-want-the-old-style-everything-global-style">Whatever, I really want the old style 'everything global' style.</h2>
<p>When you realize what a mistake it was, do this to switch back:</p>
<p>Write your own package manager, then. It's not that hard.</p>
<pre><code>npm config delete global --local</code></pre>
<p>npm will not help you do something that is known to be a bad idea.</p>
<h2 id="Should-I-check-my-node_modules-folder-into-git">Should I check my `node_modules` folder into git?</h2>
<p>Mikeal Rogers answered this question very well:</p>
<p><a href="http://www.mikealrogers.com/posts/nodemodules-in-git.html">http://www.mikealrogers.com/posts/nodemodules-in-git.html</a></p>
<p>tl;dr</p>
<ul><li>Check <code>node_modules</code> into git for things you <strong>deploy</strong>, such as
websites and apps.</li><li>Do not check <code>node_modules</code> into git for libraries and modules
intended to be reused.</li><li>Use npm to manage dependencies in your dev environment, but not in
your deployment scripts.</li></ul>
<h2 id="Is-it-npm-or-NPM-or-Npm">Is it 'npm' or 'NPM' or 'Npm'?</h2>
<p>npm should never be capitalized unless it is being displayed in a
location that is customarily all-caps (such as the title of man pages.)</p>
<h2 id="If-npm-is-an-acronym-why-is-it-never-capitalized">If 'npm' is an acronym, why is it never capitalized?</h2>
@ -79,7 +107,7 @@ acronym, and thus incorrectly named.)</p>
National Association of Pastoral Musicians. You can learn more
about them at <a href="http://npm.org/">http://npm.org/</a>.</p>
<p>In software, "NPM" is a non-parametric mapping utility written by
<p>In software, "NPM" is a Non-Parametric Mapping utility written by
Chris Rorden. You can analyze pictures of brains with it. Learn more
about the (capitalized) NPM program at <a href="http://www.cabiatl.com/mricro/npm/">http://www.cabiatl.com/mricro/npm/</a>.</p>
@ -183,12 +211,10 @@ means that publishes go over HTTP by default in those versions of node.</p>
<h2 id="I-get-ECONNREFUSED-a-lot-What-s-up">I get ECONNREFUSED a lot. What's up?</h2>
<p>Either the registry is down, or node's DNS isn't able to reach out.
This happens a lot if you don't follow <em>all</em> the steps in the Cygwin
setup doc.</p>
<p>Either the registry is down, or node's DNS isn't able to reach out.</p>
<p>To check if the registry is down, open up
<a href="http://registry.npmjs.org/-/short">http://registry.npmjs.org/-/short</a>
<a href="http://registry.npmjs.org/">http://registry.npmjs.org/</a>
in a web browser. This will also tell you if you are just unable to
access the internet for some reason.</p>
@ -215,7 +241,7 @@ We'll have someone kick it or something.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li></ul>
</div>
<p id="footer">faq &mdash; npm@1.1.0-beta-7</p>
<p id="footer">faq &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/folders.html vendored
View File

@ -205,7 +205,7 @@ cannot be found elsewhere. See <code><a href="../doc/json.html">json(1)</a></co
<ul><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/pack.html">pack(1)</a></li><li><a href="../doc/cache.html">cache(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li></ul>
</div>
<p id="footer">folders &mdash; npm@1.1.0-beta-7</p>
<p id="footer">folders &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/help-search.html vendored
View File

@ -38,7 +38,7 @@ where the terms were found in the documentation.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/help.html">help(1)</a></li></ul>
</div>
<p id="footer">help-search &mdash; npm@1.1.0-beta-7</p>
<p id="footer">help-search &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/help.html vendored
View File

@ -36,7 +36,7 @@ matches are equivalent to specifying a topic name.</p>
<ul><li><a href="../doc/npm.html">npm(1)</a></li><li><a href="../doc/README.html">README</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/help-search.html">help-search(1)</a></li><li><a href="../doc/index.html">index(1)</a></li></ul>
</div>
<p id="footer">help &mdash; npm@1.1.0-beta-7</p>
<p id="footer">help &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

6
deps/npm/html/doc/index.html vendored
View File

@ -62,6 +62,10 @@
<p> Developer Guide</p>
<h2 id="npm-disputes-1"><a href="../doc/disputes.html">disputes(1)</a></h2>
<p> Handling Module Name Disputes</p>
<h2 id="npm-docs-1"><a href="../doc/docs.html">docs(1)</a></h2>
<p> Docs for a package in a web browser maybe</p>
@ -372,7 +376,7 @@
<p> Display npm username</p>
</div>
<p id="footer">index &mdash; npm@1.1.0-beta-7</p>
<p id="footer">index &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/init.html vendored
View File

@ -29,7 +29,7 @@ without a really good reason to do so.</p>
<ul><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/version.html">version(1)</a></li></ul>
</div>
<p id="footer">init &mdash; npm@1.1.0-beta-7</p>
<p id="footer">init &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/install.html vendored
View File

@ -134,7 +134,7 @@ affects a real use-case, it will be investigated.</p>
<ul><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/rebuild.html">rebuild(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/tag.html">tag(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li></ul>
</div>
<p id="footer">install &mdash; npm@1.1.0-beta-7</p>
<p id="footer">install &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/json.html vendored
View File

@ -436,7 +436,7 @@ overridden.</p>
<ul><li><a href="../doc/semver.html">semver(1)</a></li><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/version.html">version(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li></ul>
</div>
<p id="footer">json &mdash; npm@1.1.0-beta-7</p>
<p id="footer">json &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/link.html vendored
View File

@ -58,7 +58,7 @@ installation target into your project's <code>node_modules</code> folder.</p>
<ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">link &mdash; npm@1.1.0-beta-7</p>
<p id="footer">link &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/list.html vendored
View File

@ -52,7 +52,7 @@ project.</p>
<ul><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/link.html">link(1)</a></li><li><a href="../doc/prune.html">prune(1)</a></li><li><a href="../doc/outdated.html">outdated(1)</a></li><li><a href="../doc/update.html">update(1)</a></li></ul>
</div>
<p id="footer">list &mdash; npm@1.1.0-beta-7</p>
<p id="footer">list &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/doc/npm.html vendored
View File

@ -14,7 +14,7 @@
<h2 id="VERSION">VERSION</h2>
<p>1.1.0-beta-7</p>
<p>1.1.0-beta-10</p>
<h2 id="DESCRIPTION">DESCRIPTION</h2>
@ -135,7 +135,7 @@ will no doubt tell you to put the output in a gist or email.</p>
<ul><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/README.html">README</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/index.html">index(1)</a></li><li><a href="../api/npm.html">npm(3)</a></li></ul>
</div>
<p id="footer">npm &mdash; npm@1.1.0-beta-7</p>
<p id="footer">npm &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/outdated.html vendored
View File

@ -21,7 +21,7 @@ packages are currently outdated.</p>
<ul><li><a href="../doc/update.html">update(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li></ul>
</div>
<p id="footer">outdated &mdash; npm@1.1.0-beta-7</p>
<p id="footer">outdated &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/doc/owner.html vendored
View File

@ -32,9 +32,9 @@ that is not implemented at this time.</p>
<h2 id="SEE-ALSO">SEE ALSO</h2>
<ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li></ul>
<ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/disputes.html">disputes(1)</a></li></ul>
</div>
<p id="footer">owner &mdash; npm@1.1.0-beta-7</p>
<p id="footer">owner &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/pack.html vendored
View File

@ -29,7 +29,7 @@ overwritten the second time.</p>
<ul><li><a href="../doc/cache.html">cache(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">pack &mdash; npm@1.1.0-beta-7</p>
<p id="footer">pack &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/prefix.html vendored
View File

@ -20,7 +20,7 @@
<ul><li><a href="../doc/root.html">root(1)</a></li><li><a href="../doc/bin.html">bin(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">prefix &mdash; npm@1.1.0-beta-7</p>
<p id="footer">prefix &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/prune.html vendored
View File

@ -25,7 +25,7 @@ package's dependencies list.</p>
<ul><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/list.html">list(1)</a></li></ul>
</div>
<p id="footer">prune &mdash; npm@1.1.0-beta-7</p>
<p id="footer">prune &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/publish.html vendored
View File

@ -29,7 +29,7 @@ the registry. Overwrites when the "--force" flag is set.</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li><li><a href="../doc/deprecate.html">deprecate(1)</a></li><li><a href="../doc/tag.html">tag(1)</a></li></ul>
</div>
<p id="footer">publish &mdash; npm@1.1.0-beta-7</p>
<p id="footer">publish &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/rebuild.html vendored
View File

@ -25,7 +25,7 @@ the new binary.</p>
<ul><li><a href="../doc/build.html">build(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">rebuild &mdash; npm@1.1.0-beta-7</p>
<p id="footer">rebuild &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

4
deps/npm/html/doc/registry.html vendored
View File

@ -95,9 +95,9 @@ ask for help on the <a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com
<h2 id="SEE-ALSO">SEE ALSO</h2>
<ul><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li></ul>
<ul><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/disputes.html">disputes(1)</a></li></ul>
</div>
<p id="footer">registry &mdash; npm@1.1.0-beta-7</p>
<p id="footer">registry &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/removing-npm.html vendored
View File

@ -58,7 +58,7 @@ modules. To track those down, you can do the following:</p>
<ul><li><a href="../doc/README.html">README</a></li><li><a href="../doc/rm.html">rm(1)</a></li><li><a href="../doc/prune.html">prune(1)</a></li></ul>
</div>
<p id="footer">removing-npm &mdash; npm@1.1.0-beta-7</p>
<p id="footer">removing-npm &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/restart.html vendored
View File

@ -24,7 +24,7 @@ the "start" script.</p>
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
</div>
<p id="footer">restart &mdash; npm@1.1.0-beta-7</p>
<p id="footer">restart &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/root.html vendored
View File

@ -20,7 +20,7 @@
<ul><li><a href="../doc/prefix.html">prefix(1)</a></li><li><a href="../doc/bin.html">bin(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">root &mdash; npm@1.1.0-beta-7</p>
<p id="footer">root &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/run-script.html vendored
View File

@ -23,7 +23,7 @@ called directly, as well.</p>
<ul><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
</div>
<p id="footer">run-script &mdash; npm@1.1.0-beta-7</p>
<p id="footer">run-script &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/scripts.html vendored
View File

@ -164,7 +164,7 @@ will sudo the npm command in question.</li></ul>
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/install.html">install(1)</a></li></ul>
</div>
<p id="footer">scripts &mdash; npm@1.1.0-beta-7</p>
<p id="footer">scripts &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/search.html vendored
View File

@ -24,7 +24,7 @@ expression characters must be escaped or quoted in most shells.)</p>
<ul><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/view.html">view(1)</a></li></ul>
</div>
<p id="footer">search &mdash; npm@1.1.0-beta-7</p>
<p id="footer">search &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/semver.html vendored
View File

@ -104,7 +104,7 @@ that satisfies the range, or null if none of them do.</li></ul>
<ul><li><a href="../doc/json.html">json(1)</a></li></ul>
</div>
<p id="footer">semver &mdash; npm@1.1.0-beta-7</p>
<p id="footer">semver &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/star.html vendored
View File

@ -26,7 +26,7 @@ a vaguely positive way to show that you care.</p>
<ul><li><a href="../doc/view.html">view(1)</a></li><li><a href="../doc/whoami.html">whoami(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li></ul>
</div>
<p id="footer">star &mdash; npm@1.1.0-beta-7</p>
<p id="footer">star &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/start.html vendored
View File

@ -20,7 +20,7 @@
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
</div>
<p id="footer">start &mdash; npm@1.1.0-beta-7</p>
<p id="footer">start &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/stop.html vendored
View File

@ -20,7 +20,7 @@
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/test.html">test(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li></ul>
</div>
<p id="footer">stop &mdash; npm@1.1.0-beta-7</p>
<p id="footer">stop &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/submodule.html vendored
View File

@ -33,7 +33,7 @@ dependencies into the submodule folder.</p>
<ul><li><a href="../doc/json.html">json(1)</a></li><li>git help submodule</li></ul>
</div>
<p id="footer">submodule &mdash; npm@1.1.0-beta-7</p>
<p id="footer">submodule &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/tag.html vendored
View File

@ -21,7 +21,7 @@
<ul><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">tag &mdash; npm@1.1.0-beta-7</p>
<p id="footer">tag &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/test.html vendored
View File

@ -23,7 +23,7 @@ true.</p>
<ul><li><a href="../doc/run-script.html">run-script(1)</a></li><li><a href="../doc/scripts.html">scripts(1)</a></li><li><a href="../doc/start.html">start(1)</a></li><li><a href="../doc/restart.html">restart(1)</a></li><li><a href="../doc/stop.html">stop(1)</a></li></ul>
</div>
<p id="footer">test &mdash; npm@1.1.0-beta-7</p>
<p id="footer">test &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/uninstall.html vendored
View File

@ -22,7 +22,7 @@ on its behalf.</p>
<ul><li><a href="../doc/prune.html">prune(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
<p id="footer">uninstall &mdash; npm@1.1.0-beta-7</p>
<p id="footer">uninstall &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/unpublish.html vendored
View File

@ -34,7 +34,7 @@ the root package entry is removed from the registry entirely.</p>
<ul><li><a href="../doc/deprecate.html">deprecate(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/adduser.html">adduser(1)</a></li><li><a href="../doc/owner.html">owner(1)</a></li></ul>
</div>
<p id="footer">unpublish &mdash; npm@1.1.0-beta-7</p>
<p id="footer">unpublish &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/update.html vendored
View File

@ -23,7 +23,7 @@
<ul><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/outdated.html">outdated(1)</a></li><li><a href="../doc/registry.html">registry(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/list.html">list(1)</a></li></ul>
</div>
<p id="footer">update &mdash; npm@1.1.0-beta-7</p>
<p id="footer">update &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

2
deps/npm/html/doc/version.html vendored
View File

@ -31,7 +31,7 @@ will use it as a commit message when creating a version commit.</p>
<ul><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/semver.html">semver(1)</a></li></ul>
</div>
<p id="footer">version &mdash; npm@1.1.0-beta-7</p>
<p id="footer">version &mdash; npm@1.1.0-beta-10</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")

Some files were not shown because too many files have changed in this diff Show More