From 28ae70ebad8debd8aa7b521a693aa3de89ad84d6 Mon Sep 17 00:00:00 2001
From: Timothy J Fontaine
Date: Tue, 4 Nov 2014 15:08:12 -0800
Subject: [PATCH] npm: Upgrade to v2.1.6
---
deps/npm/.eslintrc | 17 +
deps/npm/.npmignore | 2 +
deps/npm/CHANGELOG.md | 315 +++++
deps/npm/Makefile | 86 +-
deps/npm/README.md | 2 +-
deps/npm/bin/npm-cli.js | 2 +-
deps/npm/doc/api/npm-bin.md | 2 +-
deps/npm/doc/api/npm-help-search.md | 2 +-
deps/npm/doc/api/npm-load.md | 6 +-
deps/npm/doc/api/npm-submodule.md | 28 -
deps/npm/doc/api/npm.md | 19 +-
deps/npm/doc/cli/npm-adduser.md | 17 +-
deps/npm/doc/cli/npm-explore.md | 1 -
deps/npm/doc/cli/npm-init.md | 5 +-
deps/npm/doc/cli/npm-publish.md | 4 +-
deps/npm/doc/cli/npm-restart.md | 7 +-
deps/npm/doc/cli/npm-run-script.md | 10 +
deps/npm/doc/cli/npm-submodule.md | 28 -
deps/npm/doc/files/package.json.md | 69 +-
deps/npm/doc/misc/npm-coding-style.md | 2 +-
deps/npm/doc/misc/npm-config.md | 32 +-
deps/npm/doc/misc/npm-developers.md | 6 +-
deps/npm/doc/misc/npm-faq.md | 2 +-
deps/npm/doc/misc/npm-index.md | 8 -
deps/npm/doc/misc/npm-scope.md | 4 +-
deps/npm/doc/misc/npm-scripts.md | 11 +-
deps/npm/doc/misc/semver.md | 2 +-
deps/npm/html/doc/README.html | 16 +-
deps/npm/html/doc/api/npm-bin.html | 4 +-
deps/npm/html/doc/api/npm-bugs.html | 2 +-
deps/npm/html/doc/api/npm-cache.html | 4 +-
deps/npm/html/doc/api/npm-commands.html | 4 +-
deps/npm/html/doc/api/npm-config.html | 4 +-
deps/npm/html/doc/api/npm-deprecate.html | 8 +-
deps/npm/html/doc/api/npm-docs.html | 2 +-
deps/npm/html/doc/api/npm-edit.html | 2 +-
deps/npm/html/doc/api/npm-explore.html | 2 +-
deps/npm/html/doc/api/npm-help-search.html | 4 +-
deps/npm/html/doc/api/npm-init.html | 4 +-
deps/npm/html/doc/api/npm-install.html | 2 +-
deps/npm/html/doc/api/npm-link.html | 2 +-
deps/npm/html/doc/api/npm-load.html | 8 +-
deps/npm/html/doc/api/npm-ls.html | 2 +-
deps/npm/html/doc/api/npm-outdated.html | 2 +-
deps/npm/html/doc/api/npm-owner.html | 6 +-
deps/npm/html/doc/api/npm-pack.html | 2 +-
deps/npm/html/doc/api/npm-prefix.html | 2 +-
deps/npm/html/doc/api/npm-prune.html | 2 +-
deps/npm/html/doc/api/npm-publish.html | 8 +-
deps/npm/html/doc/api/npm-rebuild.html | 2 +-
deps/npm/html/doc/api/npm-repo.html | 2 +-
deps/npm/html/doc/api/npm-restart.html | 6 +-
deps/npm/html/doc/api/npm-root.html | 2 +-
deps/npm/html/doc/api/npm-run-script.html | 12 +-
deps/npm/html/doc/api/npm-search.html | 2 +-
deps/npm/html/doc/api/npm-shrinkwrap.html | 2 +-
deps/npm/html/doc/api/npm-start.html | 2 +-
deps/npm/html/doc/api/npm-stop.html | 2 +-
deps/npm/html/doc/api/npm-submodule.html | 2 +-
deps/npm/html/doc/api/npm-tag.html | 2 +-
deps/npm/html/doc/api/npm-test.html | 2 +-
deps/npm/html/doc/api/npm-uninstall.html | 2 +-
deps/npm/html/doc/api/npm-unpublish.html | 2 +-
deps/npm/html/doc/api/npm-update.html | 2 +-
deps/npm/html/doc/api/npm-version.html | 2 +-
deps/npm/html/doc/api/npm-view.html | 2 +-
deps/npm/html/doc/api/npm-whoami.html | 2 +-
deps/npm/html/doc/api/npm.html | 27 +-
deps/npm/html/doc/cli/npm-adduser.html | 32 +-
deps/npm/html/doc/cli/npm-bin.html | 14 +-
deps/npm/html/doc/cli/npm-bugs.html | 18 +-
deps/npm/html/doc/cli/npm-build.html | 10 +-
deps/npm/html/doc/cli/npm-bundle.html | 4 +-
deps/npm/html/doc/cli/npm-cache.html | 16 +-
deps/npm/html/doc/cli/npm-completion.html | 8 +-
deps/npm/html/doc/cli/npm-config.html | 16 +-
deps/npm/html/doc/cli/npm-dedupe.html | 10 +-
deps/npm/html/doc/cli/npm-deprecate.html | 6 +-
deps/npm/html/doc/cli/npm-docs.html | 16 +-
deps/npm/html/doc/cli/npm-edit.html | 16 +-
deps/npm/html/doc/cli/npm-explore.html | 13 +-
deps/npm/html/doc/cli/npm-help-search.html | 8 +-
deps/npm/html/doc/cli/npm-help.html | 22 +-
deps/npm/html/doc/cli/npm-init.html | 10 +-
deps/npm/html/doc/cli/npm-install.html | 44 +-
deps/npm/html/doc/cli/npm-link.html | 24 +-
deps/npm/html/doc/cli/npm-ls.html | 22 +-
deps/npm/html/doc/cli/npm-outdated.html | 8 +-
deps/npm/html/doc/cli/npm-owner.html | 10 +-
deps/npm/html/doc/cli/npm-pack.html | 12 +-
deps/npm/html/doc/cli/npm-prefix.html | 16 +-
deps/npm/html/doc/cli/npm-prune.html | 8 +-
deps/npm/html/doc/cli/npm-publish.html | 22 +-
deps/npm/html/doc/cli/npm-rebuild.html | 6 +-
deps/npm/html/doc/cli/npm-repo.html | 6 +-
deps/npm/html/doc/cli/npm-restart.html | 18 +-
deps/npm/html/doc/cli/npm-rm.html | 14 +-
deps/npm/html/doc/cli/npm-root.html | 14 +-
deps/npm/html/doc/cli/npm-run-script.html | 19 +-
deps/npm/html/doc/cli/npm-search.html | 12 +-
deps/npm/html/doc/cli/npm-shrinkwrap.html | 10 +-
deps/npm/html/doc/cli/npm-star.html | 8 +-
deps/npm/html/doc/cli/npm-stars.html | 10 +-
deps/npm/html/doc/cli/npm-start.html | 12 +-
deps/npm/html/doc/cli/npm-stop.html | 12 +-
deps/npm/html/doc/cli/npm-submodule.html | 4 +-
deps/npm/html/doc/cli/npm-tag.html | 16 +-
deps/npm/html/doc/cli/npm-test.html | 12 +-
deps/npm/html/doc/cli/npm-uninstall.html | 16 +-
deps/npm/html/doc/cli/npm-unpublish.html | 14 +-
deps/npm/html/doc/cli/npm-update.html | 12 +-
deps/npm/html/doc/cli/npm-version.html | 8 +-
deps/npm/html/doc/cli/npm-view.html | 16 +-
deps/npm/html/doc/cli/npm-whoami.html | 10 +-
deps/npm/html/doc/cli/npm.html | 40 +-
deps/npm/html/doc/files/npm-folders.html | 26 +-
deps/npm/html/doc/files/npm-global.html | 30 +-
deps/npm/html/doc/files/npm-json.html | 115 +-
deps/npm/html/doc/files/npmrc.html | 14 +-
deps/npm/html/doc/files/package.json.html | 111 +-
deps/npm/html/doc/index.html | 208 ++-
deps/npm/html/doc/misc/npm-coding-style.html | 12 +-
deps/npm/html/doc/misc/npm-config.html | 62 +-
deps/npm/html/doc/misc/npm-developers.html | 36 +-
deps/npm/html/doc/misc/npm-disputes.html | 12 +-
deps/npm/html/doc/misc/npm-faq.html | 34 +-
deps/npm/html/doc/misc/npm-index.html | 206 ++-
deps/npm/html/doc/misc/npm-registry.html | 20 +-
deps/npm/html/doc/misc/npm-scope.html | 12 +-
deps/npm/html/doc/misc/npm-scripts.html | 23 +-
deps/npm/html/doc/misc/removing-npm.html | 10 +-
deps/npm/html/doc/misc/semver.html | 4 +-
deps/npm/html/partial/doc/README.html | 166 +++
deps/npm/html/partial/doc/api/npm-bin.html | 8 +
deps/npm/html/partial/doc/api/npm-bugs.html | 13 +
deps/npm/html/partial/doc/api/npm-cache.html | 22 +
deps/npm/html/partial/doc/api/npm-commands.html | 16 +
deps/npm/html/partial/doc/api/npm-config.html | 37 +
deps/npm/html/partial/doc/api/npm-deprecate.html | 27 +
deps/npm/html/partial/doc/api/npm-docs.html | 13 +
deps/npm/html/partial/doc/api/npm-edit.html | 16 +
deps/npm/html/partial/doc/api/npm-explore.html | 11 +
deps/npm/html/partial/doc/api/npm-help-search.html | 24 +
deps/npm/html/partial/doc/api/npm-init.html | 19 +
deps/npm/html/partial/doc/api/npm-install.html | 12 +
deps/npm/html/partial/doc/api/npm-link.html | 22 +
deps/npm/html/partial/doc/api/npm-load.html | 17 +
deps/npm/html/partial/doc/api/npm-ls.html | 43 +
deps/npm/html/partial/doc/api/npm-outdated.html | 8 +
deps/npm/html/partial/doc/api/npm-owner.html | 27 +
deps/npm/html/partial/doc/api/npm-pack.html | 13 +
deps/npm/html/partial/doc/api/npm-prefix.html | 9 +
deps/npm/html/partial/doc/api/npm-prune.html | 10 +
deps/npm/html/partial/doc/api/npm-publish.html | 26 +
deps/npm/html/partial/doc/api/npm-rebuild.html | 10 +
deps/npm/html/partial/doc/api/npm-repo.html | 13 +
deps/npm/html/partial/doc/api/npm-restart.html | 16 +
deps/npm/html/partial/doc/api/npm-root.html | 9 +
deps/npm/html/partial/doc/api/npm-run-script.html | 21 +
deps/npm/html/partial/doc/api/npm-search.html | 33 +
deps/npm/html/partial/doc/api/npm-shrinkwrap.html | 13 +
deps/npm/html/partial/doc/api/npm-start.html | 8 +
deps/npm/html/partial/doc/api/npm-stop.html | 8 +
deps/npm/html/partial/doc/api/npm-submodule.html | 22 +
deps/npm/html/partial/doc/api/npm-tag.html | 16 +
deps/npm/html/partial/doc/api/npm-test.html | 10 +
deps/npm/html/partial/doc/api/npm-uninstall.html | 10 +
deps/npm/html/partial/doc/api/npm-unpublish.html | 13 +
deps/npm/html/partial/doc/api/npm-update.html | 7 +
deps/npm/html/partial/doc/api/npm-version.html | 12 +
deps/npm/html/partial/doc/api/npm-view.html | 61 +
deps/npm/html/partial/doc/api/npm-whoami.html | 9 +
deps/npm/html/partial/doc/api/npm.html | 89 ++
deps/npm/html/partial/doc/cli/npm-adduser.html | 47 +
deps/npm/html/partial/doc/cli/npm-bin.html | 15 +
deps/npm/html/partial/doc/cli/npm-bugs.html | 34 +
deps/npm/html/partial/doc/cli/npm-build.html | 18 +
deps/npm/html/partial/doc/cli/npm-bundle.html | 11 +
deps/npm/html/partial/doc/cli/npm-cache.html | 61 +
deps/npm/html/partial/doc/cli/npm-completion.html | 22 +
deps/npm/html/partial/doc/cli/npm-config.html | 46 +
deps/npm/html/partial/doc/cli/npm-dedupe.html | 43 +
deps/npm/html/partial/doc/cli/npm-deprecate.html | 18 +
deps/npm/html/partial/doc/cli/npm-docs.html | 36 +
deps/npm/html/partial/doc/cli/npm-edit.html | 29 +
deps/npm/html/partial/doc/cli/npm-explore.html | 29 +
deps/npm/html/partial/doc/cli/npm-help-search.html | 26 +
deps/npm/html/partial/doc/cli/npm-help.html | 32 +
deps/npm/html/partial/doc/cli/npm-init.html | 20 +
deps/npm/html/partial/doc/cli/npm-install.html | 219 +++
deps/npm/html/partial/doc/cli/npm-link.html | 51 +
deps/npm/html/partial/doc/cli/npm-ls.html | 65 +
deps/npm/html/partial/doc/cli/npm-outdated.html | 47 +
deps/npm/html/partial/doc/cli/npm-owner.html | 29 +
deps/npm/html/partial/doc/cli/npm-pack.html | 21 +
deps/npm/html/partial/doc/cli/npm-prefix.html | 18 +
deps/npm/html/partial/doc/cli/npm-prune.html | 19 +
deps/npm/html/partial/doc/cli/npm-publish.html | 39 +
deps/npm/html/partial/doc/cli/npm-rebuild.html | 18 +
deps/npm/html/partial/doc/cli/npm-repo.html | 22 +
deps/npm/html/partial/doc/cli/npm-restart.html | 15 +
deps/npm/html/partial/doc/cli/npm-rm.html | 19 +
deps/npm/html/partial/doc/cli/npm-root.html | 15 +
deps/npm/html/partial/doc/cli/npm-run-script.html | 27 +
deps/npm/html/partial/doc/cli/npm-search.html | 29 +
deps/npm/html/partial/doc/cli/npm-shrinkwrap.html | 144 ++
deps/npm/html/partial/doc/cli/npm-star.html | 16 +
deps/npm/html/partial/doc/cli/npm-stars.html | 17 +
deps/npm/html/partial/doc/cli/npm-start.html | 14 +
deps/npm/html/partial/doc/cli/npm-stop.html | 14 +
deps/npm/html/partial/doc/cli/npm-submodule.html | 22 +
deps/npm/html/partial/doc/cli/npm-tag.html | 24 +
deps/npm/html/partial/doc/cli/npm-test.html | 17 +
deps/npm/html/partial/doc/cli/npm-uninstall.html | 37 +
deps/npm/html/partial/doc/cli/npm-unpublish.html | 27 +
deps/npm/html/partial/doc/cli/npm-update.html | 20 +
deps/npm/html/partial/doc/cli/npm-version.html | 35 +
deps/npm/html/partial/doc/cli/npm-view.html | 62 +
deps/npm/html/partial/doc/cli/npm-whoami.html | 13 +
deps/npm/html/partial/doc/cli/npm.html | 134 ++
deps/npm/html/partial/doc/files/npm-folders.html | 164 +++
deps/npm/html/partial/doc/files/npm-global.html | 164 +++
deps/npm/html/partial/doc/files/npm-json.html | 465 ++++++
deps/npm/html/partial/doc/files/npmrc.html | 53 +
deps/npm/html/partial/doc/files/package.json.html | 465 ++++++
deps/npm/html/partial/doc/index.html | 210 +++
.../html/partial/doc/misc/npm-coding-style.html | 127 ++
deps/npm/html/partial/doc/misc/npm-config.html | 739 ++++++++++
deps/npm/html/partial/doc/misc/npm-developers.html | 161 +++
deps/npm/html/partial/doc/misc/npm-disputes.html | 92 ++
deps/npm/html/partial/doc/misc/npm-faq.html | 264 ++++
deps/npm/html/partial/doc/misc/npm-index.html | 210 +++
deps/npm/html/partial/doc/misc/npm-registry.html | 50 +
deps/npm/html/partial/doc/misc/npm-scope.html | 58 +
deps/npm/html/partial/doc/misc/npm-scripts.html | 200 +++
deps/npm/html/partial/doc/misc/removing-npm.html | 37 +
deps/npm/html/partial/doc/misc/semver.html | 243 ++++
deps/npm/lib/adduser.js | 7 +-
deps/npm/lib/build.js | 24 +-
deps/npm/lib/cache.js | 112 +-
deps/npm/lib/cache/add-local-tarball.js | 192 +--
deps/npm/lib/cache/add-local.js | 90 +-
deps/npm/lib/cache/add-named.js | 106 +-
deps/npm/lib/cache/add-remote-git.js | 68 +-
deps/npm/lib/cache/add-remote-tarball.js | 34 +-
deps/npm/lib/cache/cached-package-root.js | 14 +
deps/npm/lib/cache/get-stat.js | 7 +-
deps/npm/lib/completion.js | 4 +-
deps/npm/lib/config.js | 14 +-
.../npmconf/npmconf.js => lib/config/core.js} | 165 ++-
.../config-defs.js => lib/config/defaults.js} | 32 +-
.../npmconf/lib => lib/config}/find-prefix.js | 0
.../lib => lib/config}/get-credentials-by-uri.js | 18 +-
.../npmconf/lib => lib/config}/load-cafile.js | 9 +-
.../npmconf/lib => lib/config}/load-prefix.js | 8 +-
.../npmconf/lib => lib/config}/load-uid.js | 0
.../npmconf/lib => lib/config}/nerf-dart.js | 0
.../lib => lib/config}/set-credentials-by-uri.js | 18 +-
.../npmconf/lib => lib/config}/set-user.js | 17 +-
deps/npm/lib/explore.js | 2 +-
deps/npm/lib/help.js | 16 +-
deps/npm/lib/init.js | 40 +-
deps/npm/lib/install.js | 235 ++-
deps/npm/lib/npm.js | 9 +-
deps/npm/lib/pack.js | 13 +-
deps/npm/lib/publish.js | 33 +-
deps/npm/lib/run-script.js | 33 +-
deps/npm/lib/search.js | 2 +-
deps/npm/lib/shrinkwrap.js | 3 +-
deps/npm/lib/submodule.js | 90 --
deps/npm/lib/unbuild.js | 5 +-
deps/npm/lib/uninstall.js | 3 +-
deps/npm/lib/utils/error-handler.js | 16 +-
deps/npm/lib/utils/git.js | 5 +
deps/npm/lib/utils/locker.js | 95 +-
deps/npm/lib/utils/tar.js | 294 ++--
deps/npm/lib/version.js | 12 +-
deps/npm/lib/view.js | 58 +-
deps/npm/man/man1/npm-README.1 | 40 +-
deps/npm/man/man1/npm-adduser.1 | 30 +-
deps/npm/man/man1/npm-bin.1 | 6 +-
deps/npm/man/man1/npm-bugs.1 | 6 +-
deps/npm/man/man1/npm-build.1 | 6 +-
deps/npm/man/man1/npm-bundle.1 | 2 +-
deps/npm/man/man1/npm-cache.1 | 6 +-
deps/npm/man/man1/npm-completion.1 | 6 +-
deps/npm/man/man1/npm-config.1 | 26 +-
deps/npm/man/man1/npm-dedupe.1 | 14 +-
deps/npm/man/man1/npm-deprecate.1 | 10 +-
deps/npm/man/man1/npm-docs.1 | 6 +-
deps/npm/man/man1/npm-edit.1 | 6 +-
deps/npm/man/man1/npm-explore.1 | 12 +-
deps/npm/man/man1/npm-help-search.1 | 6 +-
deps/npm/man/man1/npm-help.1 | 6 +-
deps/npm/man/man1/npm-init.1 | 11 +-
deps/npm/man/man1/npm-install.1 | 70 +-
deps/npm/man/man1/npm-link.1 | 22 +-
deps/npm/man/man1/npm-ls.1 | 12 +-
deps/npm/man/man1/npm-outdated.1 | 6 +-
deps/npm/man/man1/npm-owner.1 | 6 +-
deps/npm/man/man1/npm-pack.1 | 6 +-
deps/npm/man/man1/npm-prefix.1 | 6 +-
deps/npm/man/man1/npm-prune.1 | 6 +-
deps/npm/man/man1/npm-publish.1 | 10 +-
deps/npm/man/man1/npm-rebuild.1 | 6 +-
deps/npm/man/man1/npm-repo.1 | 6 +-
deps/npm/man/man1/npm-restart.1 | 13 +-
deps/npm/man/man1/npm-rm.1 | 6 +-
deps/npm/man/man1/npm-root.1 | 6 +-
deps/npm/man/man1/npm-run-script.1 | 20 +-
deps/npm/man/man1/npm-search.1 | 6 +-
deps/npm/man/man1/npm-shrinkwrap.1 | 34 +-
deps/npm/man/man1/npm-star.1 | 6 +-
deps/npm/man/man1/npm-stars.1 | 6 +-
deps/npm/man/man1/npm-start.1 | 6 +-
deps/npm/man/man1/npm-stop.1 | 6 +-
deps/npm/man/man1/npm-submodule.1 | 6 +-
deps/npm/man/man1/npm-tag.1 | 14 +-
deps/npm/man/man1/npm-test.1 | 6 +-
deps/npm/man/man1/npm-uninstall.1 | 14 +-
deps/npm/man/man1/npm-unpublish.1 | 6 +-
deps/npm/man/man1/npm-update.1 | 6 +-
deps/npm/man/man1/npm-version.1 | 14 +-
deps/npm/man/man1/npm-view.1 | 42 +-
deps/npm/man/man1/npm-whoami.1 | 6 +-
deps/npm/man/man1/npm.1 | 8 +-
deps/npm/man/man3/npm-bin.3 | 8 +-
deps/npm/man/man3/npm-bugs.3 | 6 +-
deps/npm/man/man3/npm-cache.3 | 6 +-
deps/npm/man/man3/npm-commands.3 | 6 +-
deps/npm/man/man3/npm-config.3 | 6 +-
deps/npm/man/man3/npm-deprecate.3 | 6 +-
deps/npm/man/man3/npm-docs.3 | 6 +-
deps/npm/man/man3/npm-edit.3 | 6 +-
deps/npm/man/man3/npm-explore.3 | 6 +-
deps/npm/man/man3/npm-help-search.3 | 8 +-
deps/npm/man/man3/npm-init.3 | 6 +-
deps/npm/man/man3/npm-install.3 | 6 +-
deps/npm/man/man3/npm-link.3 | 10 +-
deps/npm/man/man3/npm-load.3 | 16 +-
deps/npm/man/man3/npm-ls.3 | 6 +-
deps/npm/man/man3/npm-outdated.3 | 6 +-
deps/npm/man/man3/npm-owner.3 | 6 +-
deps/npm/man/man3/npm-pack.3 | 6 +-
deps/npm/man/man3/npm-prefix.3 | 6 +-
deps/npm/man/man3/npm-prune.3 | 6 +-
deps/npm/man/man3/npm-publish.3 | 6 +-
deps/npm/man/man3/npm-rebuild.3 | 6 +-
deps/npm/man/man3/npm-repo.3 | 6 +-
deps/npm/man/man3/npm-restart.3 | 6 +-
deps/npm/man/man3/npm-root.3 | 6 +-
deps/npm/man/man3/npm-run-script.3 | 6 +-
deps/npm/man/man3/npm-search.3 | 6 +-
deps/npm/man/man3/npm-shrinkwrap.3 | 6 +-
deps/npm/man/man3/npm-start.3 | 6 +-
deps/npm/man/man3/npm-stop.3 | 6 +-
deps/npm/man/man3/npm-submodule.3 | 6 +-
deps/npm/man/man3/npm-tag.3 | 6 +-
deps/npm/man/man3/npm-test.3 | 6 +-
deps/npm/man/man3/npm-uninstall.3 | 6 +-
deps/npm/man/man3/npm-unpublish.3 | 6 +-
deps/npm/man/man3/npm-update.3 | 8 +-
deps/npm/man/man3/npm-version.3 | 6 +-
deps/npm/man/man3/npm-view.3 | 42 +-
deps/npm/man/man3/npm-whoami.3 | 6 +-
deps/npm/man/man3/npm.3 | 35 +-
deps/npm/man/man5/npm-folders.5 | 10 +-
deps/npm/man/man5/npm-global.5 | 10 +-
deps/npm/man/man5/npm-json.5 | 179 +--
deps/npm/man/man5/npmrc.5 | 6 +-
deps/npm/man/man5/package.json.5 | 179 +--
deps/npm/man/man7/npm-coding-style.7 | 28 +-
deps/npm/man/man7/npm-config.7 | 54 +-
deps/npm/man/man7/npm-developers.7 | 32 +-
deps/npm/man/man7/npm-disputes.7 | 2 +-
deps/npm/man/man7/npm-faq.7 | 24 +-
deps/npm/man/man7/npm-index.7 | 8 +-
deps/npm/man/man7/npm-registry.7 | 2 +-
deps/npm/man/man7/npm-scope.7 | 30 +-
deps/npm/man/man7/npm-scripts.7 | 42 +-
deps/npm/man/man7/removing-npm.7 | 22 +-
deps/npm/man/man7/semver.7 | 12 +-
deps/npm/node_modules/archy/LICENSE | 18 +
deps/npm/node_modules/archy/README.markdown | 22 +-
deps/npm/node_modules/archy/examples/beep.js | 24 +
deps/npm/node_modules/archy/examples/multi_line.js | 25 +
deps/npm/node_modules/archy/package.json | 77 +-
deps/npm/node_modules/archy/test/beep.js | 40 +
deps/npm/node_modules/archy/test/multi_line.js | 45 +
deps/npm/node_modules/archy/test/non_unicode.js | 40 +
.../node_modules => }/config-chain/.npmignore | 0
.../node_modules => }/config-chain/LICENCE | 0
.../node_modules => }/config-chain/index.js | 0
.../config-chain/node_modules/proto-list/LICENSE | 0
.../config-chain/node_modules/proto-list/README.md | 0
.../node_modules/proto-list/package.json | 5 +-
.../node_modules/proto-list/proto-list.js | 0
.../node_modules/proto-list/test/basic.js | 0
.../node_modules => }/config-chain/package.json | 2 +-
.../node_modules => }/config-chain/readme.markdown | 0
.../node_modules => }/config-chain/test/broken.js | 0
.../config-chain/test/broken.json | 0
.../config-chain/test/chain-class.js | 0
.../node_modules => }/config-chain/test/env.js | 0
.../config-chain/test/find-file.js | 0
.../node_modules => }/config-chain/test/get.js | 0
.../config-chain/test/ignore-unfound-file.js | 0
.../node_modules => }/config-chain/test/ini.js | 0
.../node_modules => }/config-chain/test/save.js | 0
deps/npm/node_modules/dezalgo/dezalgo.js | 3 +-
.../dezalgo/node_modules/asap/package.json | 2 +-
deps/npm/node_modules/dezalgo/package.json | 23 +-
deps/npm/node_modules/dezalgo/test/basic.js | 12 +-
.../node_modules/fs-write-stream-atomic/LICENSE | 15 +
.../node_modules/fs-write-stream-atomic/README.md | 35 +
.../node_modules/fs-write-stream-atomic/index.js | 96 ++
.../fs-write-stream-atomic/package.json | 53 +
.../fs-write-stream-atomic/test/basic.js | 89 ++
deps/npm/node_modules/fstream-npm/fstream-npm.js | 6 +
.../node_modules/fstream-ignore/package.json | 22 +-
deps/npm/node_modules/fstream-npm/package.json | 30 +-
deps/npm/node_modules/glob/README.md | 11 +-
deps/npm/node_modules/glob/glob.js | 6 +-
deps/npm/node_modules/glob/oh-my-glob.gif | Bin 0 -> 510360 bytes
deps/npm/node_modules/glob/package.json | 27 +-
deps/npm/node_modules/glob/test/negation-test.js | 16 +
deps/npm/node_modules/graceful-fs/package.json | 24 +-
deps/npm/node_modules/graceful-fs/test/max-open.js | 69 +
.../node_modules/graceful-fs/test/readdir-sort.js | 1 -
.../graceful-fs/test/write-then-read.js | 45 +
deps/npm/node_modules/inflight/.eslintrc | 17 +
deps/npm/node_modules/inflight/inflight.js | 39 +-
deps/npm/node_modules/inflight/package.json | 32 +-
deps/npm/node_modules/inflight/test.js | 64 +
deps/npm/node_modules/inherits/package.json | 21 +-
deps/npm/node_modules/ini/README.md | 59 +-
deps/npm/node_modules/ini/ini.js | 28 +-
deps/npm/node_modules/ini/package.json | 19 +-
deps/npm/node_modules/ini/test/foo.js | 26 +
deps/npm/node_modules/init-package-json/.npmignore | 2 +
.../init-package-json/default-input.js | 59 +-
.../init-package-json/init-package-json.js | 23 +-
.../node_modules/promzard/package.json | 5 +-
.../node_modules/init-package-json/package.json | 34 +-
.../init-package-json/test/npm-defaults.js | 49 +
.../node_modules/normalize-package-data/README.md | 6 +-
.../normalize-package-data/lib/fixer.js | 7 +
.../lib/warning_messages.json | 3 +-
.../normalize-package-data/package.json | 19 +-
.../normalize-package-data/test/dependencies.js | 3 +-
deps/npm/node_modules/npm-package-arg/package.json | 12 +-
.../npm/node_modules/npm-package-arg/test/basic.js | 2 +-
.../node_modules/npm-registry-client/lib/fetch.js | 6 +-
.../npm-registry-client/lib/request.js | 5 +-
.../node_modules/npm-registry-client/package.json | 13 +-
.../npm-registry-client/test/fetch-authed.js | 56 +
.../npm-registry-client/test/fetch-not-authed.js | 52 +
.../fixtures/@npm/npm-registry-client/cache.json | 1 +
.../test/fixtures/underscore/1.3.3/cache.json | 1 +
.../test/fixtures/underscore/1.3.3/package.tgz | Bin 0 -> 58692 bytes
.../test/fixtures/underscore/cache.json | 1 +
.../npm-registry-client/test/lib/common.js | 4 +
.../node_modules/npm-user-validate/package.json | 39 +-
deps/npm/node_modules/npmconf/.npmignore | 3 -
deps/npm/node_modules/npmconf/LICENSE | 27 -
deps/npm/node_modules/npmconf/README.md | 33 -
deps/npm/node_modules/npmconf/package.json | 71 -
deps/npm/node_modules/npmconf/test/00-setup.js | 67 -
deps/npm/node_modules/npmconf/test/basic.js | 58 -
deps/npm/node_modules/npmconf/test/builtin.js | 59 -
deps/npm/node_modules/npmconf/test/certfile.js | 17 -
deps/npm/node_modules/npmconf/test/credentials.js | 166 ---
deps/npm/node_modules/npmconf/test/project.js | 60 -
deps/npm/node_modules/npmconf/test/save.js | 84 --
deps/npm/node_modules/npmconf/test/semver-tag.js | 65 -
deps/npm/node_modules/once/once.js | 3 +-
deps/npm/node_modules/once/package.json | 33 +-
deps/npm/node_modules/once/test/once.js | 7 +-
deps/npm/node_modules/opener/LICENSE.txt | 33 +-
deps/npm/node_modules/opener/README.md | 101 +-
deps/npm/node_modules/opener/opener.js | 2 +-
deps/npm/node_modules/opener/package.json | 30 +-
.../node_modules => }/readable-stream/.npmignore | 0
.../bl/node_modules => }/readable-stream/LICENSE | 0
.../bl/node_modules => }/readable-stream/README.md | 0
.../bl/node_modules => }/readable-stream/duplex.js | 0
.../readable-stream/lib/_stream_duplex.js | 0
.../readable-stream/lib/_stream_passthrough.js | 0
.../readable-stream/lib/_stream_readable.js | 0
.../readable-stream/lib/_stream_transform.js | 0
.../readable-stream/lib/_stream_writable.js | 0
.../node_modules/core-util-is/README.md | 0
.../node_modules/core-util-is/float.patch | 0
.../node_modules/core-util-is/lib/util.js | 0
.../node_modules/core-util-is/package.json | 5 +-
.../node_modules/core-util-is/util.js | 0
.../readable-stream/node_modules/isarray/README.md | 0
.../node_modules/isarray/build/build.js | 0
.../node_modules/isarray/component.json | 0
.../readable-stream/node_modules/isarray/index.js | 0
.../node_modules/isarray/package.json | 0
.../node_modules/string_decoder/.npmignore | 0
.../node_modules/string_decoder/LICENSE | 0
.../node_modules/string_decoder/README.md | 0
.../node_modules/string_decoder/index.js | 0
.../node_modules/string_decoder/package.json | 2 +-
.../node_modules => }/readable-stream/package.json | 18 +-
.../readable-stream/passthrough.js | 0
.../node_modules => }/readable-stream/readable.js | 0
.../node_modules => }/readable-stream/transform.js | 0
.../node_modules => }/readable-stream/writable.js | 0
.../realize-package-specifier/.npmignore | 3 +
.../realize-package-specifier/README.md | 58 +
.../realize-package-specifier/index.js | 38 +
.../realize-package-specifier/package.json | 53 +
.../realize-package-specifier/test/basic.js | 121 ++
.../realize-package-specifier/test/npa-basic.js | 207 +++
.../realize-package-specifier/test/npa-windows.js | 42 +
deps/npm/node_modules/request/.eslintrc | 22 +
deps/npm/node_modules/request/.travis.yml | 13 +-
deps/npm/node_modules/request/CONTRIBUTING.md | 25 +-
deps/npm/node_modules/request/README.md | 243 +++-
deps/npm/node_modules/request/index.js | 56 +-
deps/npm/node_modules/request/lib/cookies.js | 48 +-
deps/npm/node_modules/request/lib/copy.js | 4 +-
deps/npm/node_modules/request/lib/debug.js | 4 +-
deps/npm/node_modules/request/lib/helpers.js | 57 +-
deps/npm/node_modules/request/lib/optional.js | 13 -
.../request/node_modules/aws-sign2/package.json | 5 +-
.../node_modules/request/node_modules/bl/.jshintrc | 59 +
.../node_modules/request/node_modules/bl/LICENSE | 39 -
.../request/node_modules/bl/LICENSE.md | 13 +
.../node_modules/request/node_modules/bl/README.md | 7 +-
.../request/node_modules/bl/package.json | 21 +-
.../request/node_modules/caseless/package.json | 2 +-
.../node_modules/forever-agent/package.json | 5 +-
.../form-data/node_modules/async/package.json | 2 +-
.../node_modules/delayed-stream/package.json | 2 +-
.../node_modules/combined-stream/package.json | 2 +-
.../form-data/node_modules/mime/package.json | 5 +-
.../request/node_modules/form-data/package.json | 2 +-
.../hawk/node_modules/boom/package.json | 2 +-
.../hawk/node_modules/cryptiles/package.json | 2 +-
.../hawk/node_modules/hoek/package.json | 2 +-
.../hawk/node_modules/sntp/package.json | 2 +-
.../http-signature/node_modules/asn1/package.json | 2 +-
.../node_modules/assert-plus/package.json | 5 +-
.../http-signature/node_modules/ctype/package.json | 5 +-
.../node_modules/http-signature/package.json | 2 +-
.../node_modules/json-stringify-safe/package.json | 5 +-
.../request/node_modules/mime-types/package.json | 2 +-
.../request/node_modules/node-uuid/package.json | 5 +-
.../request/node_modules/oauth-sign/package.json | 2 +-
.../node_modules/request/node_modules/qs/.jshintrc | 10 +
.../request/node_modules/qs/package.json | 2 +-
.../request/node_modules/stringstream/package.json | 5 +-
.../node_modules/punycode/LICENSE-MIT.txt | 2 +-
.../tough-cookie/node_modules/punycode/README.md | 6 +-
.../node_modules/punycode/package.json | 32 +-
.../tough-cookie/node_modules/punycode/punycode.js | 12 +-
.../request/node_modules/tunnel-agent/.jshintrc | 5 +
.../request/node_modules/tunnel-agent/package.json | 5 +-
deps/npm/node_modules/request/package.json | 52 +-
deps/npm/node_modules/request/release.sh | 3 +
deps/npm/node_modules/request/request.js | 1491 ++++++++++++--------
deps/npm/node_modules/retry/Readme.md | 8 +-
deps/npm/node_modules/retry/package.json | 28 +-
deps/npm/node_modules/semver/README.md | 2 +-
deps/npm/node_modules/semver/bin/semver | 10 +-
deps/npm/node_modules/semver/package.json | 23 +-
deps/npm/node_modules/semver/semver.browser.js | 62 +-
deps/npm/node_modules/semver/semver.browser.js.gz | Bin 7391 -> 7595 bytes
deps/npm/node_modules/semver/semver.js | 62 +-
deps/npm/node_modules/semver/semver.min.js | 2 +-
deps/npm/node_modules/semver/semver.min.js.gz | Bin 3397 -> 3472 bytes
deps/npm/node_modules/semver/test/clean.js | 6 +-
deps/npm/node_modules/semver/test/gtr.js | 2 +-
deps/npm/node_modules/semver/test/index.js | 66 +-
deps/npm/node_modules/sha/.npmignore | 6 +-
deps/npm/node_modules/sha/LICENSE | 90 +-
deps/npm/node_modules/sha/README.md | 96 +-
deps/npm/node_modules/sha/index.js | 238 ++--
.../sha/node_modules/readable-stream/LICENSE | 41 +-
.../sha/node_modules/readable-stream/README.md | 4 +-
.../sha/node_modules/readable-stream/float.patch | 923 ++++++++++++
.../readable-stream/lib/_stream_readable.js | 377 +++--
.../readable-stream/lib/_stream_transform.js | 11 +-
.../readable-stream/lib/_stream_writable.js | 181 ++-
.../node_modules/core-util-is/package.json | 3 +-
.../node_modules/isarray/package.json | 5 +-
.../node_modules/string_decoder/package.json | 3 +-
.../sha/node_modules/readable-stream/package.json | 20 +-
.../sha/node_modules/readable-stream/readable.js | 1 +
deps/npm/node_modules/sha/package.json | 27 +-
deps/npm/node_modules/wrappy/LICENSE | 15 +
deps/npm/node_modules/wrappy/README.md | 36 +
deps/npm/node_modules/wrappy/package.json | 52 +
deps/npm/node_modules/wrappy/test/basic.js | 51 +
deps/npm/node_modules/wrappy/wrappy.js | 33 +
deps/npm/node_modules/write-file-atomic/.npmignore | 4 +
deps/npm/node_modules/write-file-atomic/README.md | 44 +
deps/npm/node_modules/write-file-atomic/index.js | 45 +
.../node_modules/write-file-atomic/package.json | 56 +
.../node_modules/write-file-atomic/test/basic.js | 97 ++
deps/npm/package.json | 64 +-
deps/npm/scripts/doc-build.sh | 69 +-
deps/npm/test/common-tap.js | 35 +
.../test/fixtures => test/fixtures/config}/.npmrc | 0
.../test/fixtures => test/fixtures/config}/builtin | 0
.../fixtures => test/fixtures/config}/globalconfig | 0
deps/npm/test/fixtures/config/malformed | 1 +
.../fixtures => test/fixtures/config}/multi-ca | 0
.../fixtures => test/fixtures/config}/package.json | 0
.../fixtures => test/fixtures/config}/userconfig | 0
deps/npm/test/fixtures/config/userconfig-with-gc | 22 +
deps/npm/test/tap/00-check-mock-dep.js | 4 +-
deps/npm/test/tap/00-config-setup.js | 68 +
deps/npm/test/tap/00-verify-bundle-deps.js | 2 +-
deps/npm/test/tap/00-verify-ls-ok.js | 15 +-
deps/npm/test/tap/404-parent.js | 51 +-
deps/npm/test/tap/builtin-config.js | 125 ++
deps/npm/test/tap/cache-add-localdir-fallback.js | 84 +-
deps/npm/test/tap/cache-add-unpublished.js | 59 +-
deps/npm/test/tap/cache-shasum-fork.js | 83 ++
.../tap/cache-shasum-fork/underscore-1.5.1.tgz | Bin 0 -> 583 bytes
deps/npm/test/tap/cache-shasum.js | 12 +-
deps/npm/test/tap/circular-dep.js | 4 +-
deps/npm/test/tap/config-basic.js | 66 +
deps/npm/test/tap/config-builtin.js | 68 +
deps/npm/test/tap/config-certfile.js | 18 +
deps/npm/test/tap/config-credentials.js | 295 ++++
deps/npm/test/tap/config-malformed.js | 14 +
deps/npm/test/tap/config-meta.js | 50 +-
deps/npm/test/tap/config-project.js | 66 +
deps/npm/test/tap/config-save.js | 88 ++
deps/npm/test/tap/config-semver-tag.js | 27 +
deps/npm/test/tap/dedupe.js | 29 +-
.../tap/dev-dep-duplicate/desired-ls-results.json | 9 +
deps/npm/test/tap/dev-dep-duplicate/package.json | 11 +
deps/npm/test/tap/false_name.js | 54 +-
deps/npm/test/tap/git-cache-locking.js | 32 +-
deps/npm/test/tap/git-cache-no-hooks.js | 63 +
deps/npm/test/tap/git-cache-permissions.js | 80 --
.../test/tap/global-prefix-set-in-userconfig.js | 4 +-
deps/npm/test/tap/ignore-install-link.js | 2 +-
deps/npm/test/tap/ignore-scripts.js | 53 +-
deps/npm/test/tap/ignore-shrinkwrap.js | 18 +-
deps/npm/test/tap/install-at-locally.js | 52 +-
deps/npm/test/tap/install-cli-production.js | 44 +
.../install-cli-production/dependency/package.json | 5 +
.../dev-dependency/package.json | 5 +
.../test/tap/install-cli-production/package.json | 14 +
deps/npm/test/tap/install-cli-unicode.js | 37 +-
deps/npm/test/tap/install-from-local.js | 33 +-
.../package-scoped-dependency/package.json | 5 +
.../package-with-scoped-paths/package.json | 8 +
deps/npm/test/tap/install-save-exact.js | 81 +-
deps/npm/test/tap/install-save-local.js | 59 +-
deps/npm/test/tap/install-save-prefix.js | 122 +-
.../test/tap/install-scoped-already-installed.js | 86 ++
deps/npm/test/tap/install-scoped-link.js | 49 +-
.../npm/test/tap/install-with-dev-dep-duplicate.js | 57 +
deps/npm/test/tap/invalid-cmd-exit-code.js | 7 +-
deps/npm/test/tap/lifecycle-path.js | 4 +-
deps/npm/test/tap/lifecycle.js | 8 +-
deps/npm/test/tap/locker.js | 89 ++
deps/npm/test/tap/login-always-auth.js | 142 ++
deps/npm/test/tap/ls-depth-cli.js | 48 +-
deps/npm/test/tap/ls-depth-unmet.js | 51 +-
deps/npm/test/tap/ls-no-results.js | 12 +-
deps/npm/test/tap/noargs-install-config-save.js | 16 +-
deps/npm/test/tap/npm-api-not-loaded-error.js | 2 +-
.../tap/optional-metadep-rollback-collision.js | 2 +-
deps/npm/test/tap/outdated-color.js | 34 +-
deps/npm/test/tap/outdated-depth.js | 38 +-
deps/npm/test/tap/outdated-git.js | 21 +-
.../test/tap/outdated-include-devdependencies.js | 10 +-
deps/npm/test/tap/outdated-json.js | 41 +-
deps/npm/test/tap/outdated-new-versions.js | 10 +-
deps/npm/test/tap/outdated-notarget.js | 10 +-
deps/npm/test/tap/outdated.js | 18 +-
deps/npm/test/tap/pack-scoped.js | 52 +-
deps/npm/test/tap/peer-deps-invalid.js | 16 +-
deps/npm/test/tap/peer-deps-toplevel.js | 55 +
.../tap/peer-deps-toplevel/desired-ls-results.json | 20 +
deps/npm/test/tap/peer-deps-toplevel/package.json | 11 +
.../npm/test/tap/peer-deps-without-package-json.js | 24 +-
deps/npm/test/tap/peer-deps.js | 4 +-
deps/npm/test/tap/prepublish.js | 52 +-
deps/npm/test/tap/prune.js | 99 +-
deps/npm/test/tap/publish-config.js | 37 +-
deps/npm/test/tap/publish-scoped.js | 34 +-
deps/npm/test/tap/pwd-prefix.js | 8 +-
deps/npm/test/tap/referer.js | 9 +-
deps/npm/test/tap/registry.js | 68 +-
deps/npm/test/tap/repo.js | 12 +-
deps/npm/test/tap/run-script.js | 74 +-
deps/npm/test/tap/run-script/package.json | 9 +-
deps/npm/test/tap/scripts-whitespace-windows.js | 95 +-
deps/npm/test/tap/search.js | 265 ++++
deps/npm/test/tap/semver-doc.js | 4 +-
deps/npm/test/tap/semver-tag.js | 2 +-
deps/npm/test/tap/shrinkwrap-empty-deps.js | 5 +-
deps/npm/test/tap/sorted-package-json.js | 13 +-
deps/npm/test/tap/spawn-enoent.js | 2 +-
deps/npm/test/tap/startstop.js | 52 +-
deps/npm/test/tap/test-run-ls.js | 6 +-
deps/npm/test/tap/uninstall-package.js | 3 +-
deps/npm/test/tap/unpack-foreign-tarball.js | 42 +-
deps/npm/test/tap/update-save.js | 82 +-
deps/npm/test/tap/url-dependencies.js | 52 +-
deps/npm/test/tap/version-no-git.js | 54 +
deps/npm/test/tap/version-no-tags.js | 80 +-
deps/npm/test/tap/view.js | 253 ++++
deps/npm/test/tap/zz-cleanup.js | 15 +
715 files changed, 18443 insertions(+), 6525 deletions(-)
create mode 100644 deps/npm/.eslintrc
delete mode 100644 deps/npm/doc/api/npm-submodule.md
delete mode 100644 deps/npm/doc/cli/npm-submodule.md
create mode 100644 deps/npm/html/partial/doc/README.html
create mode 100644 deps/npm/html/partial/doc/api/npm-bin.html
create mode 100644 deps/npm/html/partial/doc/api/npm-bugs.html
create mode 100644 deps/npm/html/partial/doc/api/npm-cache.html
create mode 100644 deps/npm/html/partial/doc/api/npm-commands.html
create mode 100644 deps/npm/html/partial/doc/api/npm-config.html
create mode 100644 deps/npm/html/partial/doc/api/npm-deprecate.html
create mode 100644 deps/npm/html/partial/doc/api/npm-docs.html
create mode 100644 deps/npm/html/partial/doc/api/npm-edit.html
create mode 100644 deps/npm/html/partial/doc/api/npm-explore.html
create mode 100644 deps/npm/html/partial/doc/api/npm-help-search.html
create mode 100644 deps/npm/html/partial/doc/api/npm-init.html
create mode 100644 deps/npm/html/partial/doc/api/npm-install.html
create mode 100644 deps/npm/html/partial/doc/api/npm-link.html
create mode 100644 deps/npm/html/partial/doc/api/npm-load.html
create mode 100644 deps/npm/html/partial/doc/api/npm-ls.html
create mode 100644 deps/npm/html/partial/doc/api/npm-outdated.html
create mode 100644 deps/npm/html/partial/doc/api/npm-owner.html
create mode 100644 deps/npm/html/partial/doc/api/npm-pack.html
create mode 100644 deps/npm/html/partial/doc/api/npm-prefix.html
create mode 100644 deps/npm/html/partial/doc/api/npm-prune.html
create mode 100644 deps/npm/html/partial/doc/api/npm-publish.html
create mode 100644 deps/npm/html/partial/doc/api/npm-rebuild.html
create mode 100644 deps/npm/html/partial/doc/api/npm-repo.html
create mode 100644 deps/npm/html/partial/doc/api/npm-restart.html
create mode 100644 deps/npm/html/partial/doc/api/npm-root.html
create mode 100644 deps/npm/html/partial/doc/api/npm-run-script.html
create mode 100644 deps/npm/html/partial/doc/api/npm-search.html
create mode 100644 deps/npm/html/partial/doc/api/npm-shrinkwrap.html
create mode 100644 deps/npm/html/partial/doc/api/npm-start.html
create mode 100644 deps/npm/html/partial/doc/api/npm-stop.html
create mode 100644 deps/npm/html/partial/doc/api/npm-submodule.html
create mode 100644 deps/npm/html/partial/doc/api/npm-tag.html
create mode 100644 deps/npm/html/partial/doc/api/npm-test.html
create mode 100644 deps/npm/html/partial/doc/api/npm-uninstall.html
create mode 100644 deps/npm/html/partial/doc/api/npm-unpublish.html
create mode 100644 deps/npm/html/partial/doc/api/npm-update.html
create mode 100644 deps/npm/html/partial/doc/api/npm-version.html
create mode 100644 deps/npm/html/partial/doc/api/npm-view.html
create mode 100644 deps/npm/html/partial/doc/api/npm-whoami.html
create mode 100644 deps/npm/html/partial/doc/api/npm.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-adduser.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-bin.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-bugs.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-build.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-bundle.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-cache.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-completion.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-config.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-dedupe.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-deprecate.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-docs.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-edit.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-explore.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-help-search.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-help.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-init.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-install.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-link.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-ls.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-outdated.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-owner.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-pack.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-prefix.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-prune.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-publish.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-rebuild.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-repo.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-restart.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-rm.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-root.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-run-script.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-search.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-shrinkwrap.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-star.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-stars.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-start.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-stop.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-submodule.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-tag.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-test.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-uninstall.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-unpublish.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-update.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-version.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-view.html
create mode 100644 deps/npm/html/partial/doc/cli/npm-whoami.html
create mode 100644 deps/npm/html/partial/doc/cli/npm.html
create mode 100644 deps/npm/html/partial/doc/files/npm-folders.html
create mode 100644 deps/npm/html/partial/doc/files/npm-global.html
create mode 100644 deps/npm/html/partial/doc/files/npm-json.html
create mode 100644 deps/npm/html/partial/doc/files/npmrc.html
create mode 100644 deps/npm/html/partial/doc/files/package.json.html
create mode 100644 deps/npm/html/partial/doc/index.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-coding-style.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-config.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-developers.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-disputes.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-faq.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-index.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-registry.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-scope.html
create mode 100644 deps/npm/html/partial/doc/misc/npm-scripts.html
create mode 100644 deps/npm/html/partial/doc/misc/removing-npm.html
create mode 100644 deps/npm/html/partial/doc/misc/semver.html
create mode 100644 deps/npm/lib/cache/cached-package-root.js
rename deps/npm/{node_modules/npmconf/npmconf.js => lib/config/core.js} (68%)
rename deps/npm/{node_modules/npmconf/config-defs.js => lib/config/defaults.js} (95%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/find-prefix.js (100%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/get-credentials-by-uri.js (75%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/load-cafile.js (72%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/load-prefix.js (89%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/load-uid.js (100%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/nerf-dart.js (100%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/set-credentials-by-uri.js (62%)
rename deps/npm/{node_modules/npmconf/lib => lib/config}/set-user.js (63%)
delete mode 100644 deps/npm/lib/submodule.js
create mode 100644 deps/npm/node_modules/archy/LICENSE
create mode 100644 deps/npm/node_modules/archy/examples/beep.js
create mode 100644 deps/npm/node_modules/archy/examples/multi_line.js
create mode 100644 deps/npm/node_modules/archy/test/beep.js
create mode 100644 deps/npm/node_modules/archy/test/multi_line.js
create mode 100644 deps/npm/node_modules/archy/test/non_unicode.js
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/.npmignore (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/LICENCE (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/index.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/node_modules/proto-list/LICENSE (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/node_modules/proto-list/README.md (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/node_modules/proto-list/package.json (93%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/node_modules/proto-list/proto-list.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/node_modules/proto-list/test/basic.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/package.json (99%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/readme.markdown (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/broken.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/broken.json (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/chain-class.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/env.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/find-file.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/get.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/ignore-unfound-file.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/ini.js (100%)
rename deps/npm/node_modules/{npmconf/node_modules => }/config-chain/test/save.js (100%)
create mode 100644 deps/npm/node_modules/fs-write-stream-atomic/LICENSE
create mode 100644 deps/npm/node_modules/fs-write-stream-atomic/README.md
create mode 100644 deps/npm/node_modules/fs-write-stream-atomic/index.js
create mode 100644 deps/npm/node_modules/fs-write-stream-atomic/package.json
create mode 100644 deps/npm/node_modules/fs-write-stream-atomic/test/basic.js
create mode 100644 deps/npm/node_modules/glob/oh-my-glob.gif
create mode 100644 deps/npm/node_modules/glob/test/negation-test.js
create mode 100644 deps/npm/node_modules/graceful-fs/test/max-open.js
create mode 100644 deps/npm/node_modules/graceful-fs/test/write-then-read.js
create mode 100644 deps/npm/node_modules/inflight/.eslintrc
create mode 100644 deps/npm/node_modules/init-package-json/.npmignore
create mode 100644 deps/npm/node_modules/init-package-json/test/npm-defaults.js
create mode 100644 deps/npm/node_modules/npm-registry-client/test/fetch-authed.js
create mode 100644 deps/npm/node_modules/npm-registry-client/test/fetch-not-authed.js
create mode 100644 deps/npm/node_modules/npm-registry-client/test/fixtures/@npm/npm-registry-client/cache.json
create mode 100644 deps/npm/node_modules/npm-registry-client/test/fixtures/underscore/1.3.3/cache.json
create mode 100644 deps/npm/node_modules/npm-registry-client/test/fixtures/underscore/1.3.3/package.tgz
create mode 100644 deps/npm/node_modules/npm-registry-client/test/fixtures/underscore/cache.json
delete mode 100644 deps/npm/node_modules/npmconf/.npmignore
delete mode 100644 deps/npm/node_modules/npmconf/LICENSE
delete mode 100644 deps/npm/node_modules/npmconf/README.md
delete mode 100644 deps/npm/node_modules/npmconf/package.json
delete mode 100644 deps/npm/node_modules/npmconf/test/00-setup.js
delete mode 100644 deps/npm/node_modules/npmconf/test/basic.js
delete mode 100644 deps/npm/node_modules/npmconf/test/builtin.js
delete mode 100644 deps/npm/node_modules/npmconf/test/certfile.js
delete mode 100644 deps/npm/node_modules/npmconf/test/credentials.js
delete mode 100644 deps/npm/node_modules/npmconf/test/project.js
delete mode 100644 deps/npm/node_modules/npmconf/test/save.js
delete mode 100644 deps/npm/node_modules/npmconf/test/semver-tag.js
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/.npmignore (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/LICENSE (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/README.md (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/duplex.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/lib/_stream_duplex.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/lib/_stream_passthrough.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/lib/_stream_readable.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/lib/_stream_transform.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/lib/_stream_writable.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/core-util-is/README.md (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/core-util-is/float.patch (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/core-util-is/lib/util.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/core-util-is/package.json (94%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/core-util-is/util.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/isarray/README.md (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/isarray/build/build.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/isarray/component.json (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/isarray/index.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/isarray/package.json (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/string_decoder/.npmignore (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/string_decoder/LICENSE (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/string_decoder/README.md (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/string_decoder/index.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/node_modules/string_decoder/package.json (96%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/package.json (78%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/passthrough.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/readable.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/transform.js (100%)
rename deps/npm/node_modules/{request/node_modules/bl/node_modules => }/readable-stream/writable.js (100%)
create mode 100644 deps/npm/node_modules/realize-package-specifier/.npmignore
create mode 100644 deps/npm/node_modules/realize-package-specifier/README.md
create mode 100644 deps/npm/node_modules/realize-package-specifier/index.js
create mode 100644 deps/npm/node_modules/realize-package-specifier/package.json
create mode 100644 deps/npm/node_modules/realize-package-specifier/test/basic.js
create mode 100644 deps/npm/node_modules/realize-package-specifier/test/npa-basic.js
create mode 100644 deps/npm/node_modules/realize-package-specifier/test/npa-windows.js
create mode 100644 deps/npm/node_modules/request/.eslintrc
delete mode 100644 deps/npm/node_modules/request/lib/optional.js
create mode 100644 deps/npm/node_modules/request/node_modules/bl/.jshintrc
delete mode 100644 deps/npm/node_modules/request/node_modules/bl/LICENSE
create mode 100644 deps/npm/node_modules/request/node_modules/bl/LICENSE.md
create mode 100644 deps/npm/node_modules/request/node_modules/qs/.jshintrc
create mode 100644 deps/npm/node_modules/request/node_modules/tunnel-agent/.jshintrc
create mode 100755 deps/npm/node_modules/request/release.sh
create mode 100644 deps/npm/node_modules/sha/node_modules/readable-stream/float.patch
create mode 100644 deps/npm/node_modules/wrappy/LICENSE
create mode 100644 deps/npm/node_modules/wrappy/README.md
create mode 100644 deps/npm/node_modules/wrappy/package.json
create mode 100644 deps/npm/node_modules/wrappy/test/basic.js
create mode 100644 deps/npm/node_modules/wrappy/wrappy.js
create mode 100644 deps/npm/node_modules/write-file-atomic/.npmignore
create mode 100644 deps/npm/node_modules/write-file-atomic/README.md
create mode 100644 deps/npm/node_modules/write-file-atomic/index.js
create mode 100644 deps/npm/node_modules/write-file-atomic/package.json
create mode 100644 deps/npm/node_modules/write-file-atomic/test/basic.js
rename deps/npm/{node_modules/npmconf/test/fixtures => test/fixtures/config}/.npmrc (100%)
rename deps/npm/{node_modules/npmconf/test/fixtures => test/fixtures/config}/builtin (100%)
rename deps/npm/{node_modules/npmconf/test/fixtures => test/fixtures/config}/globalconfig (100%)
create mode 100644 deps/npm/test/fixtures/config/malformed
rename deps/npm/{node_modules/npmconf/test/fixtures => test/fixtures/config}/multi-ca (100%)
rename deps/npm/{node_modules/npmconf/test/fixtures => test/fixtures/config}/package.json (100%)
rename deps/npm/{node_modules/npmconf/test/fixtures => test/fixtures/config}/userconfig (100%)
create mode 100644 deps/npm/test/fixtures/config/userconfig-with-gc
create mode 100644 deps/npm/test/tap/00-config-setup.js
create mode 100644 deps/npm/test/tap/builtin-config.js
create mode 100644 deps/npm/test/tap/cache-shasum-fork.js
create mode 100644 deps/npm/test/tap/cache-shasum-fork/underscore-1.5.1.tgz
create mode 100644 deps/npm/test/tap/config-basic.js
create mode 100644 deps/npm/test/tap/config-builtin.js
create mode 100644 deps/npm/test/tap/config-certfile.js
create mode 100644 deps/npm/test/tap/config-credentials.js
create mode 100644 deps/npm/test/tap/config-malformed.js
create mode 100644 deps/npm/test/tap/config-project.js
create mode 100644 deps/npm/test/tap/config-save.js
create mode 100644 deps/npm/test/tap/config-semver-tag.js
create mode 100644 deps/npm/test/tap/dev-dep-duplicate/desired-ls-results.json
create mode 100644 deps/npm/test/tap/dev-dep-duplicate/package.json
create mode 100644 deps/npm/test/tap/git-cache-no-hooks.js
delete mode 100644 deps/npm/test/tap/git-cache-permissions.js
create mode 100644 deps/npm/test/tap/install-cli-production.js
create mode 100644 deps/npm/test/tap/install-cli-production/dependency/package.json
create mode 100644 deps/npm/test/tap/install-cli-production/dev-dependency/package.json
create mode 100644 deps/npm/test/tap/install-cli-production/package.json
create mode 100644 deps/npm/test/tap/install-from-local/package-scoped-dependency/package.json
create mode 100644 deps/npm/test/tap/install-from-local/package-with-scoped-paths/package.json
create mode 100644 deps/npm/test/tap/install-scoped-already-installed.js
create mode 100644 deps/npm/test/tap/install-with-dev-dep-duplicate.js
create mode 100644 deps/npm/test/tap/locker.js
create mode 100644 deps/npm/test/tap/login-always-auth.js
create mode 100644 deps/npm/test/tap/peer-deps-toplevel.js
create mode 100644 deps/npm/test/tap/peer-deps-toplevel/desired-ls-results.json
create mode 100644 deps/npm/test/tap/peer-deps-toplevel/package.json
create mode 100644 deps/npm/test/tap/search.js
create mode 100644 deps/npm/test/tap/version-no-git.js
create mode 100644 deps/npm/test/tap/view.js
create mode 100644 deps/npm/test/tap/zz-cleanup.js
diff --git a/deps/npm/.eslintrc b/deps/npm/.eslintrc
new file mode 100644
index 0000000..ba33150
--- /dev/null
+++ b/deps/npm/.eslintrc
@@ -0,0 +1,17 @@
+{
+ "env" : {
+ "node" : true
+ },
+ "rules" : {
+ "semi": [2, "never"],
+ "strict": 0,
+ "quotes": [1, "double", "avoid-escape"],
+ "no-use-before-define": 0,
+ "curly": 0,
+ "no-underscore-dangle": 0,
+ "no-lonely-if": 1,
+ "no-unused-vars": [2, {"vars" : "all", "args" : "after-used"}],
+ "no-mixed-requires": 0,
+ "space-infix-ops": 0
+ }
+}
diff --git a/deps/npm/.npmignore b/deps/npm/.npmignore
index 7232cea..a128c9b 100644
--- a/deps/npm/.npmignore
+++ b/deps/npm/.npmignore
@@ -25,3 +25,5 @@ html/*.png
/npm-*.tgz
*.pyc
+
+/test/tap/builtin-config
diff --git a/deps/npm/CHANGELOG.md b/deps/npm/CHANGELOG.md
index a8afe8a..e67cd29 100644
--- a/deps/npm/CHANGELOG.md
+++ b/deps/npm/CHANGELOG.md
@@ -1,3 +1,318 @@
+### v2.1.6 (2014-10-23):
+
+* [`681b398`](https://github.com/npm/npm/commit/681b3987a18e7aba0aaf78c91a23c7cc0ab82ce8)
+ [#6523](https://github.com/npm/npm/issues/6523) fix default `logelevel` doc
+ ([@KenanY](https://github.com/KenanY))
+* [`80b368f`](https://github.com/npm/npm/commit/80b368ffd786d4d008734b56c4a6fe12d2cb2926)
+ [#6528](https://github.com/npm/npm/issues/6528) `npm version` should work in
+ a git directory without git ([@terinjokes](https://github.com/terinjokes))
+* [`5f5f9e4`](https://github.com/npm/npm/commit/5f5f9e4ddf544c2da6adf3f8c885238b0e745076)
+ [#6483](https://github.com/npm/npm/issues/6483) `init-package-json@1.1.1`:
+ Properly pick up default values from environment variables.
+ ([@othiym23](https://github.com/othiym23))
+* [`a114870`](https://github.com/npm/npm/commit/a1148702f53f82d49606b2e4dac7581261fff442)
+ perl 5.18.x doesn't like -pi without filenames
+ ([@othiym23](https://github.com/othiym23))
+* [`de5ba00`](https://github.com/npm/npm/commit/de5ba007a48db876eb5bfb6156435f3512d58977)
+ `request@2.46.0`: Tests and cleanup.
+ ([@othiym23](https://github.com/othiym23))
+* [`76933f1`](https://github.com/npm/npm/commit/76933f169f17b5273b32e924a7b392d5729931a7)
+ `fstream-npm@1.0.1`: Always include `LICENSE[.*]`, `LICENCE[.*]`,
+ `CHANGES[.*]`, `CHANGELOG[.*]`, and `HISTORY[.*]`.
+ ([@jonathanong](https://github.com/jonathanong))
+
+### v2.1.5 (2014-10-16):
+
+* [`6a14b23`](https://github.com/npm/npm/commit/6a14b232a0e34158bd95bb25c607167be995c204)
+ [#6397](https://github.com/npm/npm/issues/6397) Defactor npmconf back into
+ npm. ([@othiym23](https://github.com/othiym23))
+* [`4000e33`](https://github.com/npm/npm/commit/4000e3333a76ca4844681efa8737cfac24b7c2c8)
+ [#6323](https://github.com/npm/npm/issues/6323) Install `peerDependencies`
+ from top. ([@othiym23](https://github.com/othiym23))
+* [`5d119ae`](https://github.com/npm/npm/commit/5d119ae246f27353b14ff063559d1ba8c616bb89)
+ [#6498](https://github.com/npm/npm/issues/6498) Better error messages on
+ malformed `.npmrc` properties. ([@nicks](https://github.com/nicks))
+* [`ae18efb`](https://github.com/npm/npm/commit/ae18efb65fed427b1ef18e4862885bf60b87b92e)
+ [#6093](https://github.com/npm/npm/issues/6093) Replace instances of 'hash'
+ with 'object' in documentation. ([@zeke](https://github.com/zeke))
+* [`53108b2`](https://github.com/npm/npm/commit/53108b276fec5f97a38250933a2768d58b6928da)
+ [#1558](https://github.com/npm/npm/issues/1558) Clarify how local paths
+ should be used. ([@KenanY](https://github.com/KenanY))
+* [`344fa1a`](https://github.com/npm/npm/commit/344fa1a219ac8867022df3dc58a47636dde8a242)
+ [#6488](https://github.com/npm/npm/issues/6488) Work around bug in marked.
+ ([@othiym23](https://github.com/othiym23))
+
+OUTDATED DEPENDENCY CLEANUP JAMBOREE
+
+* [`60c2942`](https://github.com/npm/npm/commit/60c2942e13655d9ecdf6e0f1f97f10cb71a75255)
+ `realize-package-specifier@1.2.0`: Handle names and rawSpecs more
+ consistently. ([@iarna](https://github.com/iarna))
+* [`1b5c95f`](https://github.com/npm/npm/commit/1b5c95fbda77b87342bd48c5ecac5b1fd571ccfe)
+ `sha@1.3.0`: Change line endings?
+ ([@ForbesLindesay](https://github.com/ForbesLindesay))
+* [`d7dee3f`](https://github.com/npm/npm/commit/d7dee3f3f7d9e7c2061a4ecb4dd93e3e4bfe4f2e)
+ `request@2.45.0`: Dependency updates, better proxy support, better compressed
+ response handling, lots of 'use strict'.
+ ([@mikeal](https://github.com/mikeal))
+* [`3d75180`](https://github.com/npm/npm/commit/3d75180c2cc79fa3adfa0e4cb783a27192189a65)
+ `opener@1.4.0`: Added gratuitous return.
+ ([@Domenic](https://github.com/Domenic))
+* [`8e2703f`](https://github.com/npm/npm/commit/8e2703f78d280d1edeb749e257dda1f288bad6e3)
+ `retry@0.6.1` / `npm-registry-client@3.2.4`: Change of ownership.
+ ([@tim-kos](https://github.com/tim-kos))
+* [`c87b00f`](https://github.com/npm/npm/commit/c87b00f82f92434ee77831915012c77a6c244c39)
+ `once@1.3.1`: Wrap once with wrappy. ([@isaacs](https://github.com/isaacs))
+* [`01ec790`](https://github.com/npm/npm/commit/01ec790fd47def56eda6abb3b8d809093e8f493f)
+ `npm-user-validate@0.1.1`: Correct repository URL.
+ ([@robertkowalski](https://github.com/robertkowalski))
+* [`389e52c`](https://github.com/npm/npm/commit/389e52c2d94c818ca8935ccdcf392994fec564a2)
+ `glob@4.0.6`: Now absolutely requires `graceful-fs`.
+ ([@isaacs](https://github.com/isaacs))
+* [`e15ab15`](https://github.com/npm/npm/commit/e15ab15a27a8f14cf0d9dc6f11dee452080378a0)
+ `ini@1.3.0`: Tighten up whitespace handling.
+ ([@isaacs](https://github.com/isaacs))
+* [`7610f3e`](https://github.com/npm/npm/commit/7610f3e62e699292ece081bfd33084d436e3246d)
+ `archy@1.0.0` ([@substack](https://github.com/substack))
+* [`9c13149`](https://github.com/npm/npm/commit/9c1314985e513e20ffa3ea0ca333ba2ab78299c9)
+ `semver@4.1.0`: Add support for prerelease identifiers.
+ ([@bromanko](https://github.com/bromanko))
+* [`f096c25`](https://github.com/npm/npm/commit/f096c250441b031d758f03afbe8d2321f94c7703)
+ `graceful-fs@3.0.4`: Add a bunch of additional tests, skip the unfortunate
+ complications of `graceful-fs@3.0.3`. ([@isaacs](https://github.com/isaacs))
+
+### v2.1.4 (2014-10-09):
+
+* [`3aeb440`](https://github.com/npm/npm/commit/3aeb4401444fad83cc7a8d11bf2507658afa5248)
+ [#6442](https://github.com/npm/npm/issues/6442) proxying git needs `GIT_SSL_CAINFO`
+ ([@wmertens](https://github.com/wmertens))
+* [`a8da8d6`](https://github.com/npm/npm/commit/a8da8d6e0cd56d97728c0b76b51604ee06ef6264)
+ [#6413](https://github.com/npm/npm/issues/6413) write builtin config on any
+ global npm install ([@isaacs](https://github.com/isaacs))
+* [`9e4d632`](https://github.com/npm/npm/commit/9e4d632c0142ba55df07d624667738b8727336fc)
+ [#6343](https://github.com/npm/npm/issues/6343) don't pass run arguments to
+ pre & post scripts ([@TheLudd](https://github.com/TheLudd))
+* [`d831b1f`](https://github.com/npm/npm/commit/d831b1f7ca1a9921ea5b394e39b7130ecbc6d7b4)
+ [#6399](https://github.com/npm/npm/issues/6399) race condition: inflight
+ installs, prevent `peerDependency` problems
+ ([@othiym23](https://github.com/othiym23))
+* [`82b775d`](https://github.com/npm/npm/commit/82b775d6ff34c4beb6c70b2344d491a9f2026577)
+ [#6384](https://github.com/npm/npm/issues/6384) race condition: inflight
+ caching by URL rather than semver range
+ ([@othiym23](https://github.com/othiym23))
+* [`7bee042`](https://github.com/npm/npm/commit/7bee0429066fedcc9e6e962c043eb740b3792809)
+ `inflight@1.0.4`: callback can take arbitrary number of parameters
+ ([@othiym23](https://github.com/othiym23))
+* [`3bff494`](https://github.com/npm/npm/commit/3bff494f4abf17d6d7e0e4a3a76cf7421ecec35a)
+ [#5195](https://github.com/npm/npm/issues/5195) fixed regex color regression
+ for `npm search` ([@chrismeyersfsu](https://github.com/chrismeyersfsu))
+* [`33ba2d5`](https://github.com/npm/npm/commit/33ba2d585160a0a2a322cb76c4cd989acadcc984)
+ [#6387](https://github.com/npm/npm/issues/6387) allow `npm view global` if
+ package is specified ([@evanlucas](https://github.com/evanlucas))
+* [`99c4cfc`](https://github.com/npm/npm/commit/99c4cfceed413396d952cf05f4e3c710f9682c23)
+ [#6388](https://github.com/npm/npm/issues/6388) npm-publish â
+ npm-developers(7) ([@kennydude](https://github.com/kennydude))
+
+TEST CLEANUP EXTRAVAGANZA:
+
+* [`8d6bfcb`](https://github.com/npm/npm/commit/8d6bfcb88408f5885a2a67409854c43e5c3a23f6)
+ tap tests run with no system-wide side effects
+ ([@chrismeyersfsu](https://github.com/chrismeyersfsu))
+* [`7a1472f`](https://github.com/npm/npm/commit/7a1472fbdbe99956ad19f629e7eb1cc07ba026ef)
+ added npm cache cleanup script
+ ([@chrismeyersfsu](https://github.com/chrismeyersfsu))
+* [`0ce6a37`](https://github.com/npm/npm/commit/0ce6a3752fa9119298df15671254db6bc1d8e64c)
+ stripped out dead test code (othiym23)
+* replace spawn with common.npm (@chrismeyersfsu):
+ * [`0dcd614`](https://github.com/npm/npm/commit/0dcd61446335eaf541bf5f2d5186ec1419f86a42)
+ test/tap/cache-shasum-fork.js
+ * [`97f861c`](https://github.com/npm/npm/commit/97f861c967606a7e51e3d5047cf805d9d1adea5a)
+ test/tap/false_name.js
+ * [`d01b3de`](https://github.com/npm/npm/commit/d01b3de6ce03f25bbf3db97bfcd3cc85830d6801)
+ test/tap/git-cache-locking.js
+ * [`7b63016`](https://github.com/npm/npm/commit/7b63016778124c6728d6bd89a045c841ae3900b6)
+ test/tap/pack-scoped.js
+ * [`c877553`](https://github.com/npm/npm/commit/c877553265c39673e03f0a97972f692af81a595d)
+ test/tap/scripts-whitespace-windows.js
+ * [`df98525`](https://github.com/npm/npm/commit/df98525331e964131299d457173c697cfb3d95b9)
+ test/tap/prepublish.js
+ * [`99c4cfc`](https://github.com/npm/npm/commit/99c4cfceed413396d952cf05f4e3c710f9682c23)
+ test/tap/prune.js
+
+### v2.1.3 (2014-10-02):
+
+BREAKING CHANGE FOR THE SQRT(i) PEOPLE ACTUALLY USING `npm submodule`:
+
+* [`1e64473`](https://github.com/npm/npm/commit/1e6447360207f45ad6188e5780fdf4517de6e23d)
+ `rm -rf npm submodule` command, which has been broken since the Carter
+ Administration ([@isaacs](https://github.com/isaacs))
+
+BREAKING CHANGE IF YOU ARE FOR SOME REASON STILL USING NODE 0.6 AND YOU SHOULD
+NOT BE DOING THAT CAN YOU NOT:
+
+* [`3e431f9`](https://github.com/npm/npm/commit/3e431f9d6884acb4cde8bcb8a0b122a76b33ee1d)
+ [joyent/node#8492](https://github.com/joyent/node/issues/8492) bye bye
+ customFds, hello stdio ([@othiym23](https://github.com/othiym23))
+
+Other changes:
+
+* [`ea607a8`](https://github.com/npm/npm/commit/ea607a8a20e891ad38eed11b5ce2c3c0a65484b9)
+ [#6372](https://github.com/npm/npm/issues/6372) noisily error (without
+ aborting) on multi-{install,build} ([@othiym23](https://github.com/othiym23))
+* [`3ee2799`](https://github.com/npm/npm/commit/3ee2799b629fd079d2db21d7e8f25fa7fa1660d0)
+ [#6372](https://github.com/npm/npm/issues/6372) only make cache creation
+ requests in flight ([@othiym23](https://github.com/othiym23))
+* [`1a90ec2`](https://github.com/npm/npm/commit/1a90ec2f2cfbefc8becc6ef0c480e5edacc8a4cb)
+ [#6372](https://github.com/npm/npm/issues/6372) wait to put Git URLs in
+ flight until normalized ([@othiym23](https://github.com/othiym23))
+* [`664795b`](https://github.com/npm/npm/commit/664795bb7d8da7142417b3f4ef5986db3a394071)
+ [#6372](https://github.com/npm/npm/issues/6372) log what is and isn't in
+ flight ([@othiym23](https://github.com/othiym23))
+* [`00ef580`](https://github.com/npm/npm/commit/00ef58025a1f52dfabf2c4dc3898621d16a6e062)
+ `inflight@1.0.3`: fix largely theoretical race condition, because we really
+ really hate race conditions ([@isaacs](https://github.com/isaacs))
+* [`1cde465`](https://github.com/npm/npm/commit/1cde4658d897ae0f93ff1d65b258e1571b391182)
+ [#6363](https://github.com/npm/npm/issues/6363)
+ `realize-package-specifier@1.1.0`: handle local dependencies better
+ ([@iarna](https://github.com/iarna))
+* [`86f084c`](https://github.com/npm/npm/commit/86f084c6c6d7935cd85d72d9d94b8784c914d51e)
+ `realize-package-specifier@1.0.2`: dependency realization! in its own module!
+ ([@iarna](https://github.com/iarna))
+* [`553d830`](https://github.com/npm/npm/commit/553d830334552b83606b6bebefd821c9ea71e964)
+ `npm-package-arg@2.1.3`: simplified semver, better tests
+ ([@iarna](https://github.com/iarna))
+* [`bec9b61`](https://github.com/npm/npm/commit/bec9b61a316c19f5240657594f0905a92a474352)
+ `readable-stream@1.0.32`: for some reason
+ ([@rvagg](https://github.com/rvagg))
+* [`ff08ec5`](https://github.com/npm/npm/commit/ff08ec5f6d717bdbd559de0b2ede769306a9a763)
+ `dezalgo@1.0.1`: use wrappy for instrumentability
+ ([@isaacs](https://github.com/isaacs))
+
+### v2.1.2 (2014-09-29):
+
+* [`a1aa20e`](https://github.com/npm/npm/commit/a1aa20e44bb8285c6be1e7fa63b9da920e3a70ed)
+ [#6282](https://github.com/npm/npm/issues/6282)
+ `normalize-package-data@1.0.3`: don't prune bundledDependencies
+ ([@isaacs](https://github.com/isaacs))
+* [`a1f5fe1`](https://github.com/npm/npm/commit/a1f5fe1005043ce20a06e8b17a3e201aa3215357)
+ move locks back into cache, now path-aware
+ ([@othiym23](https://github.com/othiym23))
+* [`a432c4b`](https://github.com/npm/npm/commit/a432c4b48c881294d6d79b5f41c2e1c16ad15a8a)
+ convert lib/utils/tar.js to use atomic streams
+ ([@othiym23](https://github.com/othiym23))
+* [`b8c3c74`](https://github.com/npm/npm/commit/b8c3c74a3c963564233204161cc263e0912c930b)
+ `fs-write-stream-atomic@1.0.2`: Now works with streams1 fs.WriteStreams.
+ ([@isaacs](https://github.com/isaacs))
+* [`c7ab76f`](https://github.com/npm/npm/commit/c7ab76f44cce5f42add5e3ba879bd10e7e00c3e6)
+ logging cleanup ([@othiym23](https://github.com/othiym23))
+* [`4b2d95d`](https://github.com/npm/npm/commit/4b2d95d0641435b09d047ae5cb2226f292bf38f0)
+ [#6329](https://github.com/npm/npm/issues/6329) efficiently validate tmp
+ tarballs safely ([@othiym23](https://github.com/othiym23))
+
+### v2.1.1 (2014-09-26):
+
+* [`563225d`](https://github.com/npm/npm/commit/563225d813ea4c12f46d4f7821ac7f76ba8ee2d6)
+ [#6318](https://github.com/npm/npm/issues/6318) clean up locking; prefix
+ lockfile with "." ([@othiym23](https://github.com/othiym23))
+* [`c7f30e4`](https://github.com/npm/npm/commit/c7f30e4550fea882d31fcd4a55b681cd30713c44)
+ [#6318](https://github.com/npm/npm/issues/6318) remove locking code around
+ tarball packing and unpacking ([@othiym23](https://github.com/othiym23))
+
+### v2.1.0 (2014-09-25):
+
+NEW FEATURE:
+
+* [`3635601`](https://github.com/npm/npm/commit/36356011b6f2e6a5a81490e85a0a44eb27199dd7)
+ [#5520](https://github.com/npm/npm/issues/5520) Add `'npm view .'`.
+ ([@evanlucas](https://github.com/evanlucas))
+
+Other changes:
+
+* [`f24b552`](https://github.com/npm/npm/commit/f24b552b596d0627549cdd7c2d68fcf9006ea50a)
+ [#6294](https://github.com/npm/npm/issues/6294) Lock cache â lock cache
+ target. ([@othiym23](https://github.com/othiym23))
+* [`ad54450`](https://github.com/npm/npm/commit/ad54450104f94c82c501138b4eee488ce3a4555e)
+ [#6296](https://github.com/npm/npm/issues/6296) Ensure that npm-debug.log
+ file is created when rollbacks are done.
+ ([@isaacs](https://github.com/isaacs))
+* [`6810071`](https://github.com/npm/npm/commit/681007155a40ac9d165293bd6ec5d8a1423ccfca)
+ docs: Default loglevel "http" â "warn".
+ ([@othiym23](https://github.com/othiym23))
+* [`35ac89a`](https://github.com/npm/npm/commit/35ac89a940f23db875e882ce2888208395130336)
+ Skip installation of installed scoped packages.
+ ([@timoxley](https://github.com/timoxley))
+* [`e468527`](https://github.com/npm/npm/commit/e468527256ec599892b9b88d61205e061d1ab735)
+ Ensure cleanup executes for scripts-whitespace-windows test.
+ ([@timoxley](https://github.com/timoxley))
+* [`ef9101b`](https://github.com/npm/npm/commit/ef9101b7f346797749415086956a0394528a12c4)
+ Ensure cleanup executes for packed-scope test.
+ ([@timoxley](https://github.com/timoxley))
+* [`69b4d18`](https://github.com/npm/npm/commit/69b4d18cdbc2ae04c9afaffbd273b436a394f398)
+ `fs-write-stream-atomic@1.0.1`: Fix a race condition in our race-condition
+ fixer. ([@isaacs](https://github.com/isaacs))
+* [`26b17ff`](https://github.com/npm/npm/commit/26b17ff2e3b21ee26c6fdbecc8273520cff45718)
+ [#6272](https://github.com/npm/npm/issues/6272) `npmconf` decides what the
+ default prefix is. ([@othiym23](https://github.com/othiym23))
+* [`846faca`](https://github.com/npm/npm/commit/846facacc6427dafcf5756dcd36d9036539938de)
+ Fix development dependency is preferred over dependency.
+ ([@andersjanmyr](https://github.com/andersjanmyr))
+* [`9d1a9db`](https://github.com/npm/npm/commit/9d1a9db3af5adc48a7158a5a053eeb89ee41a0e7)
+ [#3265](https://github.com/npm/npm/issues/3265) Re-apply a71615a. Fixes
+ [#3265](https://github.com/npm/npm/issues/3265) again, with a test!
+ ([@glasser](https://github.com/glasser))
+* [`1d41db0`](https://github.com/npm/npm/commit/1d41db0b2744a7bd50971c35cc060ea0600fb4bf)
+ `marked-man@0.1.4`: Fixes formatting of synopsis blocks in man docs.
+ ([@kapouer](https://github.com/kapouer))
+* [`a623da0`](https://github.com/npm/npm/commit/a623da01bea1b2d3f3a18b9117cfd2d8e3cbdd77)
+ [#5867](https://github.com/npm/npm/issues/5867) Specify dummy git template
+ dir when cloning to prevent copying hooks.
+ ([@boneskull](https://github.com/boneskull))
+
+### v2.0.2 (2014-09-19):
+
+* [`42c872b`](https://github.com/npm/npm/commit/42c872b32cadc0e555638fc78eab3a38a04401d8)
+ [#5920](https://github.com/npm/npm/issues/5920)
+ `fs-write-stream-atomic@1.0.0` ([@isaacs](https://github.com/isaacs))
+* [`6784767`](https://github.com/npm/npm/commit/6784767fe15e28b44c81a1d4bb1738c642a65d78)
+ [#5920](https://github.com/npm/npm/issues/5920) make all write streams atomic
+ ([@isaacs](https://github.com/isaacs))
+* [`f6fac00`](https://github.com/npm/npm/commit/f6fac000dd98ebdd5ea1d5921175735d463d328b)
+ [#5920](https://github.com/npm/npm/issues/5920) barf on 0-length cached
+ tarballs ([@isaacs](https://github.com/isaacs))
+* [`3b37592`](https://github.com/npm/npm/commit/3b37592a92ea98336505189ae8ca29248b0589f4)
+ `write-file-atomic@1.1.0`: use graceful-fs
+ ([@iarna](https://github.com/iarna))
+
+### v2.0.1 (2014-09-18):
+
+* [`74c5ab0`](https://github.com/npm/npm/commit/74c5ab0a676793c6dc19a3fd5fe149f85fecb261)
+ [#6201](https://github.com/npm/npm/issues/6201) `npmconf@2.1.0`: scope
+ always-auth to registry URI ([@othiym23](https://github.com/othiym23))
+* [`774b127`](https://github.com/npm/npm/commit/774b127da1dd6fefe2f1299e73505d9146f00294)
+ [#6201](https://github.com/npm/npm/issues/6201) `npm-registry-client@3.2.2`:
+ use scoped always-auth settings ([@othiym23](https://github.com/othiym23))
+* [`f2d2190`](https://github.com/npm/npm/commit/f2d2190aa365d22378d03afab0da13f95614a583)
+ [#6201](https://github.com/npm/npm/issues/6201) support saving
+ `--always-auth` when logging in ([@othiym23](https://github.com/othiym23))
+* [`17c941a`](https://github.com/npm/npm/commit/17c941a2d583210fe97ed47e2968d94ce9f774ba)
+ [#6163](https://github.com/npm/npm/issues/6163) use `write-file-atomic`
+ instead of `fs.writeFile()` ([@fiws](https://github.com/fiws))
+* [`fb5724f`](https://github.com/npm/npm/commit/fb5724fd98e1509c939693568df83d11417ea337)
+ [#5925](https://github.com/npm/npm/issues/5925) `npm init -f`: allow `npm
+ init` to run without prompting
+ ([@michaelnisi](https://github.com/michaelnisi))
+* [`b706d63`](https://github.com/npm/npm/commit/b706d637d5965dbf8f7ce07dc5c4bc80887f30d8)
+ [#3059](https://github.com/npm/npm/issues/3059) disable prepublish when
+ running `npm install --production`
+ ([@jussi](https://github.com/jussi)-kalliokoski)
+* [`119f068`](https://github.com/npm/npm/commit/119f068eae2a36fa8b9c9ca557c70377792243a4)
+ attach the node version used when publishing a package to its registry
+ metadata ([@othiym23](https://github.com/othiym23))
+* [`8fe0081`](https://github.com/npm/npm/commit/8fe008181665519c2ac201ee432a3ece9798c31f)
+ seriously, don't use `npm -g update npm`
+ ([@thomblake](https://github.com/thomblake))
+* [`ea5b3d4`](https://github.com/npm/npm/commit/ea5b3d446b86dcabb0dbc6dba374d3039342ecb3)
+ `request@2.44.0` ([@othiym23](https://github.com/othiym23))
+
### v2.0.0 (2014-09-12):
BREAKING CHANGES:
diff --git a/deps/npm/Makefile b/deps/npm/Makefile
index fe2d963..34d4b62 100644
--- a/deps/npm/Makefile
+++ b/deps/npm/Makefile
@@ -31,6 +31,28 @@ misc_mandocs = $(shell find doc/misc -name '*.md' \
|sed 's|doc/misc/|man/man7/|g' ) \
man/man7/npm-index.7
+
+cli_partdocs = $(shell find doc/cli -name '*.md' \
+ |sed 's|.md|.html|g' \
+ |sed 's|doc/cli/|html/partial/doc/cli/|g' ) \
+ html/partial/doc/README.html
+
+api_partdocs = $(shell find doc/api -name '*.md' \
+ |sed 's|.md|.html|g' \
+ |sed 's|doc/api/|html/partial/doc/api/|g' )
+
+files_partdocs = $(shell find doc/files -name '*.md' \
+ |sed 's|.md|.html|g' \
+ |sed 's|doc/files/|html/partial/doc/files/|g' ) \
+ html/partial/doc/files/npm-json.html \
+ html/partial/doc/files/npm-global.html
+
+misc_partdocs = $(shell find doc/misc -name '*.md' \
+ |sed 's|.md|.html|g' \
+ |sed 's|doc/misc/|html/partial/doc/misc/|g' ) \
+ html/partial/doc/index.html
+
+
cli_htmldocs = $(shell find doc/cli -name '*.md' \
|sed 's|.md|.html|g' \
|sed 's|doc/cli/|html/doc/cli/|g' ) \
@@ -53,6 +75,8 @@ misc_htmldocs = $(shell find doc/misc -name '*.md' \
mandocs = $(api_mandocs) $(cli_mandocs) $(files_mandocs) $(misc_mandocs)
+partdocs = $(api_partdocs) $(cli_partdocs) $(files_partdocs) $(misc_partdocs)
+
htmldocs = $(api_htmldocs) $(cli_htmldocs) $(files_htmldocs) $(misc_htmldocs)
all: doc
@@ -63,7 +87,7 @@ latest:
@echo "in this folder that you're looking at right now."
node cli.js install -g -f npm
-install: docclean all
+install: all
node cli.js install -g -f
# backwards compat
@@ -79,7 +103,7 @@ clean: markedclean marked-manclean doc-clean uninstall
uninstall:
node cli.js rm npm -g -f
-doc: $(mandocs) $(htmldocs)
+doc: $(mandocs) $(htmldocs) $(partdocs)
markedclean:
rm -rf node_modules/marked node_modules/.bin/marked .building_marked
@@ -119,43 +143,73 @@ man/man5/%.5: doc/files/%.md scripts/doc-build.sh package.json
@[ -d man/man5 ] || mkdir -p man/man5
scripts/doc-build.sh $< $@
+man/man7/%.7: doc/misc/%.md scripts/doc-build.sh package.json
+ @[ -d man/man7 ] || mkdir -p man/man7
+ scripts/doc-build.sh $< $@
+
+
doc/misc/npm-index.md: scripts/index-build.js package.json
node scripts/index-build.js > $@
-html/doc/index.html: doc/misc/npm-index.md $(html_docdeps)
- @[ -d html/doc ] || mkdir -p html/doc
- scripts/doc-build.sh $< $@
-man/man7/%.7: doc/misc/%.md scripts/doc-build.sh package.json
- @[ -d man/man7 ] || mkdir -p man/man7
+# html/doc depends on html/partial/doc
+html/doc/%.html: html/partial/doc/%.html
+ @[ -d html/doc ] || mkdir -p html/doc
scripts/doc-build.sh $< $@
-html/doc/README.html: README.md $(html_docdeps)
+html/doc/README.html: html/partial/doc/README.html
@[ -d html/doc ] || mkdir -p html/doc
scripts/doc-build.sh $< $@
-html/doc/cli/%.html: doc/cli/%.md $(html_docdeps)
+html/doc/cli/%.html: html/partial/doc/cli/%.html
@[ -d html/doc/cli ] || mkdir -p html/doc/cli
scripts/doc-build.sh $< $@
-html/doc/api/%.html: doc/api/%.md $(html_docdeps)
+html/doc/misc/%.html: html/partial/doc/misc/%.html
+ @[ -d html/doc/misc ] || mkdir -p html/doc/misc
+ scripts/doc-build.sh $< $@
+
+html/doc/files/%.html: html/partial/doc/files/%.html
+ @[ -d html/doc/files ] || mkdir -p html/doc/files
+ scripts/doc-build.sh $< $@
+
+html/doc/api/%.html: html/partial/doc/api/%.html
@[ -d html/doc/api ] || mkdir -p html/doc/api
scripts/doc-build.sh $< $@
-html/doc/files/npm-json.html: html/doc/files/package.json.html
+
+html/partial/doc/index.html: doc/misc/npm-index.md $(html_docdeps)
+ @[ -d html/partial/doc ] || mkdir -p html/partial/doc
+ scripts/doc-build.sh $< $@
+
+html/partial/doc/README.html: README.md $(html_docdeps)
+ @[ -d html/partial/doc ] || mkdir -p html/partial/doc
+ scripts/doc-build.sh $< $@
+
+html/partial/doc/cli/%.html: doc/cli/%.md $(html_docdeps)
+ @[ -d html/partial/doc/cli ] || mkdir -p html/partial/doc/cli
+ scripts/doc-build.sh $< $@
+
+html/partial/doc/api/%.html: doc/api/%.md $(html_docdeps)
+ @[ -d html/partial/doc/api ] || mkdir -p html/partial/doc/api
+ scripts/doc-build.sh $< $@
+
+html/partial/doc/files/npm-json.html: html/partial/doc/files/package.json.html
cp $< $@
-html/doc/files/npm-global.html: html/doc/files/npm-folders.html
+html/partial/doc/files/npm-global.html: html/partial/doc/files/npm-folders.html
cp $< $@
-html/doc/files/%.html: doc/files/%.md $(html_docdeps)
- @[ -d html/doc/files ] || mkdir -p html/doc/files
+html/partial/doc/files/%.html: doc/files/%.md $(html_docdeps)
+ @[ -d html/partial/doc/files ] || mkdir -p html/partial/doc/files
scripts/doc-build.sh $< $@
-html/doc/misc/%.html: doc/misc/%.md $(html_docdeps)
- @[ -d html/doc/misc ] || mkdir -p html/doc/misc
+html/partial/doc/misc/%.html: doc/misc/%.md $(html_docdeps)
+ @[ -d html/partial/doc/misc ] || mkdir -p html/partial/doc/misc
scripts/doc-build.sh $< $@
+
+
marked: node_modules/.bin/marked
node_modules/.bin/marked:
diff --git a/deps/npm/README.md b/deps/npm/README.md
index 19ced3a..ecb3f29 100644
--- a/deps/npm/README.md
+++ b/deps/npm/README.md
@@ -154,7 +154,7 @@ use npm itself to do.
if (er) return commandFailed(er)
// command succeeded, and data might have some info
})
- npm.on("log", function (message) { .... })
+ npm.registry.log.on("log", function (message) { .... })
})
The `load` function takes an object hash of the command-line configs.
diff --git a/deps/npm/bin/npm-cli.js b/deps/npm/bin/npm-cli.js
index ed81a98..ace40ca 100755
--- a/deps/npm/bin/npm-cli.js
+++ b/deps/npm/bin/npm-cli.js
@@ -21,7 +21,7 @@ log.info("it worked if it ends with", "ok")
var path = require("path")
, npm = require("../lib/npm.js")
- , npmconf = require("npmconf")
+ , npmconf = require("../lib/config/core.js")
, errorHandler = require("../lib/utils/error-handler.js")
, configDefs = npmconf.defs
diff --git a/deps/npm/doc/api/npm-bin.md b/deps/npm/doc/api/npm-bin.md
index f3dc482..bd27af2 100644
--- a/deps/npm/doc/api/npm-bin.md
+++ b/deps/npm/doc/api/npm-bin.md
@@ -10,4 +10,4 @@ npm-bin(3) -- Display npm bin folder
Print the folder where npm will install executables.
This function should not be used programmatically. Instead, just refer
-to the `npm.bin` member.
+to the `npm.bin` property.
diff --git a/deps/npm/doc/api/npm-help-search.md b/deps/npm/doc/api/npm-help-search.md
index 5c00cfc..01b235c 100644
--- a/deps/npm/doc/api/npm-help-search.md
+++ b/deps/npm/doc/api/npm-help-search.md
@@ -27,4 +27,4 @@ array of results is returned. Each result is an object with these properties:
* file:
Name of the file that matched
-The silent parameter is not neccessary not used, but it may in the future.
+The silent parameter is not necessary not used, but it may in the future.
diff --git a/deps/npm/doc/api/npm-load.md b/deps/npm/doc/api/npm-load.md
index a95a6b2..de412af 100644
--- a/deps/npm/doc/api/npm-load.md
+++ b/deps/npm/doc/api/npm-load.md
@@ -10,9 +10,9 @@ npm-load(3) -- Load config settings
npm.load() must be called before any other function call. Both parameters are
optional, but the second is recommended.
-The first parameter is an object hash of command-line config params, and the
-second parameter is a callback that will be called when npm is loaded and
-ready to serve.
+The first parameter is an object containing command-line config params, and the
+second parameter is a callback that will be called when npm is loaded and ready
+to serve.
The first parameter should follow a similar structure as the package.json
config object.
diff --git a/deps/npm/doc/api/npm-submodule.md b/deps/npm/doc/api/npm-submodule.md
deleted file mode 100644
index 2d8bafa..0000000
--- a/deps/npm/doc/api/npm-submodule.md
+++ /dev/null
@@ -1,28 +0,0 @@
-npm-submodule(3) -- Add a package as a git submodule
-====================================================
-
-## SYNOPSIS
-
- npm.commands.submodule(packages, callback)
-
-## DESCRIPTION
-
-For each package specified, npm will check if it has a git repository url
-in its package.json description then add it as a git submodule at
-`node_modules/`.
-
-This is a convenience only. From then on, it's up to you to manage
-updates by using the appropriate git commands. npm will stubbornly
-refuse to update, modify, or remove anything with a `.git` subfolder
-in it.
-
-This command also does not install missing dependencies, if the package
-does not include them in its git repository. If `npm ls` reports that
-things are missing, you can either install, link, or submodule them yourself,
-or you can do `npm explore -- npm install` to install the
-dependencies into the submodule folder.
-
-## SEE ALSO
-
-* npm help json
-* git help submodule
diff --git a/deps/npm/doc/api/npm.md b/deps/npm/doc/api/npm.md
index d05684e..4b4dfca 100644
--- a/deps/npm/doc/api/npm.md
+++ b/deps/npm/doc/api/npm.md
@@ -25,13 +25,12 @@ This is the API documentation for npm.
To find documentation of the command line
client, see `npm(1)`.
-Prior to using npm's commands, `npm.load()` must be called.
-If you provide `configObject` as an object hash of top-level
-configs, they override the values stored in the various config
-locations. In the npm command line client, this set of configs
-is parsed from the command line options. Additional configuration
-params are loaded from two configuration files. See `npm-config(1)`,
-`npm-config(7)`, and `npmrc(5)` for more information.
+Prior to using npm's commands, `npm.load()` must be called. If you provide
+`configObject` as an object map of top-level configs, they override the values
+stored in the various config locations. In the npm command line client, this
+set of configs is parsed from the command line options. Additional
+configuration params are loaded from two configuration files. See
+`npm-config(1)`, `npm-config(7)`, and `npmrc(5)` for more information.
After that, each of the functions are accessible in the
commands object: `npm.commands.`. See `npm-index(7)` for a list of
@@ -88,9 +87,9 @@ command.
## MAGIC
-For each of the methods in the `npm.commands` hash, a method is added to
-the npm object, which takes a set of positional string arguments rather
-than an array and a callback.
+For each of the methods in the `npm.commands` object, a method is added to the
+npm object, which takes a set of positional string arguments rather than an
+array and a callback.
If the last argument is a callback, then it will use the supplied
callback. However, if no callback is provided, then it will print out
diff --git a/deps/npm/doc/cli/npm-adduser.md b/deps/npm/doc/cli/npm-adduser.md
index d60d6e9..54e785b 100644
--- a/deps/npm/doc/cli/npm-adduser.md
+++ b/deps/npm/doc/cli/npm-adduser.md
@@ -3,7 +3,7 @@ npm-adduser(1) -- Add a registry user account
## SYNOPSIS
- npm adduser [--registry=url] [--scope=@orgname]
+ npm adduser [--registry=url] [--scope=@orgname] [--always-auth]
## DESCRIPTION
@@ -45,6 +45,21 @@ e.g.
This will set a registry for the given scope and login or create a user for
that registry at the same time.
+### always-auth
+
+Default: false
+
+If specified, save configuration indicating that all requests to the given
+registry should include authorization information. Useful for private
+registries. Can be used with `--registry` and / or `--scope`, e.g.
+
+ npm adduser --registry=http://private-registry.example.com --always-auth
+
+This will ensure that all requests to that registry (including for tarballs)
+include an authorization header. See `always-auth` in `npm-config(7)` for more
+details on always-auth. Registry-specific configuaration of `always-auth` takes
+precedence over any global configuration.
+
## SEE ALSO
* npm-registry(7)
diff --git a/deps/npm/doc/cli/npm-explore.md b/deps/npm/doc/cli/npm-explore.md
index 3642d73..fded534 100644
--- a/deps/npm/doc/cli/npm-explore.md
+++ b/deps/npm/doc/cli/npm-explore.md
@@ -32,7 +32,6 @@ The shell to run for the `npm explore` command.
## SEE ALSO
-* npm-submodule(1)
* npm-folders(5)
* npm-edit(1)
* npm-rebuild(1)
diff --git a/deps/npm/doc/cli/npm-init.md b/deps/npm/doc/cli/npm-init.md
index bd63a88..08e517d 100644
--- a/deps/npm/doc/cli/npm-init.md
+++ b/deps/npm/doc/cli/npm-init.md
@@ -3,7 +3,7 @@ npm-init(1) -- Interactively create a package.json file
## SYNOPSIS
- npm init
+ npm init [-f|--force|-y|--yes]
## DESCRIPTION
@@ -18,6 +18,9 @@ the options in there.
It is strictly additive, so it does not delete options from your package.json
without a really good reason to do so.
+If you invoke it with `-f`, `--force`, `-y`, or `--yes`, it will use only
+defaults and not prompt you for any options.
+
## SEE ALSO
*
diff --git a/deps/npm/doc/cli/npm-publish.md b/deps/npm/doc/cli/npm-publish.md
index 8860b88..30e816c 100644
--- a/deps/npm/doc/cli/npm-publish.md
+++ b/deps/npm/doc/cli/npm-publish.md
@@ -9,7 +9,9 @@ npm-publish(1) -- Publish a package
## DESCRIPTION
-Publishes a package to the registry so that it can be installed by name.
+Publishes a package to the registry so that it can be installed by name. See
+`npm-developers(7)` for details on what's included in the published package, as
+well as details on how the package is built.
By default npm will publish to the public registry. This can be overridden by
specifying a different default registry or using a `npm-scope(7)` in the name
diff --git a/deps/npm/doc/cli/npm-restart.md b/deps/npm/doc/cli/npm-restart.md
index 7b039a8..6d594a2 100644
--- a/deps/npm/doc/cli/npm-restart.md
+++ b/deps/npm/doc/cli/npm-restart.md
@@ -7,11 +7,8 @@ npm-restart(1) -- Start a package
## DESCRIPTION
-This runs a package's "restart" script, if one was provided.
-Otherwise it runs package's "stop" script, if one was provided, and then
-the "start" script.
-
-If no version is specified, then it restarts the "active" version.
+This runs a package's "restart" script, if one was provided. Otherwise it runs
+package's "stop" script, if one was provided, and then the "start" script.
## SEE ALSO
diff --git a/deps/npm/doc/cli/npm-run-script.md b/deps/npm/doc/cli/npm-run-script.md
index 09a546b..74f416e 100644
--- a/deps/npm/doc/cli/npm-run-script.md
+++ b/deps/npm/doc/cli/npm-run-script.md
@@ -16,6 +16,16 @@ is provided, it will list the available top level scripts.
It is used by the test, start, restart, and stop commands, but can be
called directly, as well.
+As of [`npm@2.0.0`](http://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
+use custom arguments when executing scripts. The special option `--` is used by
+[getopt](http://goo.gl/KxMmtG) to delimit the end of the options. npm will pass
+all the arguments after the `--` directly to your script:
+
+ npm run test -- --grep="pattern"
+
+The arguments will only be passed to the script specified after ```npm run```
+and not to any pre or post script.
+
## SEE ALSO
* npm-scripts(7)
diff --git a/deps/npm/doc/cli/npm-submodule.md b/deps/npm/doc/cli/npm-submodule.md
deleted file mode 100644
index 7f0fbfc..0000000
--- a/deps/npm/doc/cli/npm-submodule.md
+++ /dev/null
@@ -1,28 +0,0 @@
-npm-submodule(1) -- Add a package as a git submodule
-====================================================
-
-## SYNOPSIS
-
- npm submodule
-
-## DESCRIPTION
-
-If the specified package has a git repository url in its package.json
-description, then this command will add it as a git submodule at
-`node_modules/`.
-
-This is a convenience only. From then on, it's up to you to manage
-updates by using the appropriate git commands. npm will stubbornly
-refuse to update, modify, or remove anything with a `.git` subfolder
-in it.
-
-This command also does not install missing dependencies, if the package
-does not include them in its git repository. If `npm ls` reports that
-things are missing, you can either install, link, or submodule them yourself,
-or you can do `npm explore -- npm install` to install the
-dependencies into the submodule folder.
-
-## SEE ALSO
-
-* package.json(5)
-* git help submodule
diff --git a/deps/npm/doc/files/package.json.md b/deps/npm/doc/files/package.json.md
index 82b9405..1138bc2 100644
--- a/deps/npm/doc/files/package.json.md
+++ b/deps/npm/doc/files/package.json.md
@@ -219,7 +219,7 @@ will create entries for `man foo` and `man 2 foo`
The CommonJS [Packages](http://wiki.commonjs.org/wiki/Packages/1.0) spec details a
few ways that you can indicate the structure of your package using a `directories`
-hash. If you look at [npm's package.json](http://registry.npmjs.org/npm/latest),
+object. If you look at [npm's package.json](http://registry.npmjs.org/npm/latest),
you'll see that it has directories for doc, lib, and man.
In the future, this information may be used in other creative ways.
@@ -231,10 +231,10 @@ with the lib folder in any way, but it's useful meta info.
### directories.bin
-If you specify a "bin" directory, then all the files in that folder will
-be used as the "bin" hash.
+If you specify a `bin` directory, then all the files in that folder will
+be added as children of the `bin` path.
-If you have a "bin" hash already, then this has no effect.
+If you have a `bin` path already, then this has no effect.
### directories.man
@@ -274,7 +274,7 @@ html project page that you put in your browser. It's for computers.
## scripts
-The "scripts" member is an object hash of script commands that are run
+The "scripts" property is a dictionary containing script commands that are run
at various times in the lifecycle of your package. The key is the lifecycle
event, and the value is the command to run at that point.
@@ -282,9 +282,9 @@ See `npm-scripts(7)` to find out more about writing package scripts.
## config
-A "config" hash can be used to set configuration
-parameters used in package scripts that persist across upgrades. For
-instance, if a package had the following:
+A "config" object can be used to set configuration parameters used in package
+scripts that persist across upgrades. For instance, if a package had the
+following:
{ "name" : "foo"
, "config" : { "port" : "8080" } }
@@ -298,13 +298,13 @@ configs.
## dependencies
-Dependencies are specified with a simple hash of package name to
+Dependencies are specified in a simple object that maps a package name to a
version range. The version range is a string which has one or more
-space-separated descriptors. Dependencies can also be identified with
-a tarball or git URL.
+space-separated descriptors. Dependencies can also be identified with a
+tarball or git URL.
**Please do not put test harnesses or transpilers in your
-`dependencies` hash.** See `devDependencies`, below.
+`dependencies` object.** See `devDependencies`, below.
See semver(7) for more details about specifying version ranges.
@@ -340,7 +340,7 @@ For example, these are all valid:
, "two" : "2.x"
, "thr" : "3.3.x"
, "lat" : "latest"
- , "dyl" : "~/projects/dyl"
+ , "dyl" : "file:../dyl"
}
}
@@ -378,14 +378,25 @@ As of version 1.1.65, you can refer to GitHub urls as just "foo": "user/foo-proj
## Local Paths
-As of version 2.0.0 you can provide a path to a local directory that
-contains a package. Local paths can be in the form:
+As of version 2.0.0 you can provide a path to a local directory that contains a
+package. Local paths can be saved using `npm install --save`, using any of
+these forms:
../foo/bar
~/foo/bar
./foo/bar
/foo/bar
+in which case they will be normalized to a relative path and added to your
+`package.json`. For example:
+
+ {
+ "name": "baz",
+ "dependencies": {
+ "bar": "file:../foo/bar"
+ }
+ }
+
This feature is helpful for local offline development and creating
tests that require npm installing where you don't want to hit an
external server, but should not be used when publishing packages
@@ -397,8 +408,8 @@ If someone is planning on downloading and using your module in their
program, then they probably don't want or need to download and build
the external test or documentation framework that you use.
-In this case, it's best to list these additional items in a
-`devDependencies` hash.
+In this case, it's best to map these additional items in a `devDependencies`
+object.
These things will be installed when doing `npm link` or `npm install`
from the root of a package, and can be managed like any other npm
@@ -469,11 +480,11 @@ If this is spelled `"bundleDependencies"`, then that is also honorable.
## optionalDependencies
-If a dependency can be used, but you would like npm to proceed if it
-cannot be found or fails to install, then you may put it in the
-`optionalDependencies` hash. This is a map of package name to version
-or url, just like the `dependencies` hash. The difference is that
-failure is tolerated.
+If a dependency can be used, but you would like npm to proceed if it cannot be
+found or fails to install, then you may put it in the `optionalDependencies`
+object. This is a map of package name to version or url, just like the
+`dependencies` object. The difference is that build failures do not cause
+installation to fail.
It is still your program's responsibility to handle the lack of the
dependency. For example, something like this:
@@ -521,12 +532,12 @@ field is advisory only.
## engineStrict
If you are sure that your module will *definitely not* run properly on
-versions of Node/npm other than those specified in the `engines` hash,
+versions of Node/npm other than those specified in the `engines` object,
then you can set `"engineStrict": true` in your package.json file.
This will override the user's `engine-strict` config setting.
Please do not do this unless you are really very very sure. If your
-engines hash is something overly restrictive, you can quite easily and
+engines object is something overly restrictive, you can quite easily and
inadvertently lock yourself into obscurity and prevent your users from
updating to new versions of Node. Consider this choice carefully. If
people abuse it, it will be removed in a future version of npm.
@@ -575,11 +586,11 @@ does help prevent some confusion if it doesn't work as expected.
If you set `"private": true` in your package.json, then npm will refuse
to publish it.
-This is a way to prevent accidental publication of private repositories.
-If you would like to ensure that a given package is only ever published
-to a specific registry (for example, an internal registry),
-then use the `publishConfig` hash described below
-to override the `registry` config param at publish-time.
+This is a way to prevent accidental publication of private repositories. If
+you would like to ensure that a given package is only ever published to a
+specific registry (for example, an internal registry), then use the
+`publishConfig` dictionary described below to override the `registry` config
+param at publish-time.
## publishConfig
diff --git a/deps/npm/doc/misc/npm-coding-style.md b/deps/npm/doc/misc/npm-coding-style.md
index b6a4a62..80609f4 100644
--- a/deps/npm/doc/misc/npm-coding-style.md
+++ b/deps/npm/doc/misc/npm-coding-style.md
@@ -147,7 +147,7 @@ Use appropriate log levels. See `npm-config(7)` and search for
## Case, naming, etc.
Use `lowerCamelCase` for multiword identifiers when they refer to objects,
-functions, methods, members, or anything not specified in this section.
+functions, methods, properties, or anything not specified in this section.
Use `UpperCamelCase` for class names (things that you'd pass to "new").
diff --git a/deps/npm/doc/misc/npm-config.md b/deps/npm/doc/misc/npm-config.md
index 8b5ae12..6e7d995 100644
--- a/deps/npm/doc/misc/npm-config.md
+++ b/deps/npm/doc/misc/npm-config.md
@@ -384,35 +384,35 @@ documentation for the
[init-package-json](https://github.com/isaacs/init-package-json) module
for more information, or npm-init(1).
-### init.author.name
+### init-author-name
* Default: ""
* Type: String
The value `npm init` should use by default for the package author's name.
-### init.author.email
+### init-author-email
* Default: ""
* Type: String
The value `npm init` should use by default for the package author's email.
-### init.author.url
+### init-author-url
* Default: ""
* Type: String
The value `npm init` should use by default for the package author's homepage.
-### init.license
+### init-license
* Default: "ISC"
* Type: String
The value `npm init` should use by default for the package license.
-### init.version
+### init-version
* Default: "0.0.0"
* Type: semver
@@ -464,7 +464,7 @@ to the npm registry. Must be IPv4 in versions of Node prior to 0.12.
### loglevel
-* Default: "http"
+* Default: "warn"
* Type: String
* Values: "silent", "error", "warn", "http", "info", "verbose", "silly"
@@ -472,7 +472,7 @@ What level of logs to report. On failure, *all* logs are written to
`npm-debug.log` in the current working directory.
Any logs of a higher level than the setting are shown.
-The default is "http", which shows http, warn, and error output.
+The default is "warn", which shows warn and error output.
### logstream
@@ -510,7 +510,7 @@ Any "%s" in the message will be replaced with the version number.
* Default: process.version
* Type: semver or false
-The node version to use when checking package's "engines" hash.
+The node version to use when checking a package's `engines` map.
### npat
@@ -532,7 +532,7 @@ usage.
* Default: true
* Type: Boolean
-Attempt to install packages in the `optionalDependencies` hash. Note
+Attempt to install packages in the `optionalDependencies` object. Note
that if these packages fail to install, the overall installation
process is not aborted.
@@ -610,8 +610,8 @@ Remove failed installs.
Save installed packages to a package.json file as dependencies.
-When used with the `npm rm` command, it removes it from the dependencies
-hash.
+When used with the `npm rm` command, it removes it from the `dependencies`
+object.
Only works if there is already a package.json file present.
@@ -632,10 +632,10 @@ bundledDependencies list.
* Default: false
* Type: Boolean
-Save installed packages to a package.json file as devDependencies.
+Save installed packages to a package.json file as `devDependencies`.
When used with the `npm rm` command, it removes it from the
-devDependencies hash.
+`devDependencies` object.
Only works if there is already a package.json file present.
@@ -657,7 +657,7 @@ Save installed packages to a package.json file as
optionalDependencies.
When used with the `npm rm` command, it removes it from the
-devDependencies hash.
+`devDependencies` object.
Only works if there is already a package.json file present.
@@ -848,8 +848,8 @@ Only relevant when specified explicitly on the command line.
* Default: false
* Type: boolean
-If true, output the npm version as well as node's `process.versions`
-hash, and exit successfully.
+If true, output the npm version as well as node's `process.versions` map, and
+exit successfully.
Only relevant when specified explicitly on the command line.
diff --git a/deps/npm/doc/misc/npm-developers.md b/deps/npm/doc/misc/npm-developers.md
index 5e53301..f6ea011 100644
--- a/deps/npm/doc/misc/npm-developers.md
+++ b/deps/npm/doc/misc/npm-developers.md
@@ -76,7 +76,7 @@ least, you need:
* scripts:
If you have a special compilation or installation script, then you
- should put it in the `scripts` hash. You should definitely have at
+ should put it in the `scripts` object. You should definitely have at
least a basic smoke-test command as the "scripts.test" field.
See npm-scripts(7).
@@ -86,8 +86,8 @@ least, you need:
then you need to specify that in the "main" field.
* directories:
- This is a hash of folders. The best ones to include are "lib" and
- "doc", but if you specify a folder full of man pages in "man", then
+ This is an object mapping names to folders. The best ones to include are
+ "lib" and "doc", but if you use "man" to specify a folder full of man pages,
they'll get installed just like these ones.
You can use `npm init` in the root of your package in order to get you
diff --git a/deps/npm/doc/misc/npm-faq.md b/deps/npm/doc/misc/npm-faq.md
index 4dca3cd..7289127 100644
--- a/deps/npm/doc/misc/npm-faq.md
+++ b/deps/npm/doc/misc/npm-faq.md
@@ -135,7 +135,7 @@ Arguments are greps. `npm search jsdom` shows jsdom packages.
## How do I update npm?
- npm update npm -g
+ npm install npm -g
You can also update all outdated local packages by doing `npm update` without
any arguments, or global packages by doing `npm update -g`.
diff --git a/deps/npm/doc/misc/npm-index.md b/deps/npm/doc/misc/npm-index.md
index cf96986..9c804bf 100644
--- a/deps/npm/doc/misc/npm-index.md
+++ b/deps/npm/doc/misc/npm-index.md
@@ -161,10 +161,6 @@ Start a package
Stop a package
-### npm-submodule(1)
-
-Add a package as a git submodule
-
### npm-tag(1)
Tag a published version
@@ -325,10 +321,6 @@ Start a package
Stop a package
-### npm-submodule(3)
-
-Add a package as a git submodule
-
### npm-tag(3)
Tag a published version
diff --git a/deps/npm/doc/misc/npm-scope.md b/deps/npm/doc/misc/npm-scope.md
index a4ee1a0..66a9255 100644
--- a/deps/npm/doc/misc/npm-scope.md
+++ b/deps/npm/doc/misc/npm-scope.md
@@ -25,8 +25,8 @@ scoped modules will be in `node_modules/@myorg/packagename`. The scope folder
(`@myorg`) is simply the name of the scope preceded by an @-symbol, and can
contain any number of scoped packages.
-A scoped package is install by referencing it by name, preceded by an @-symbol,
-in `npm install`:
+A scoped package is installed by referencing it by name, preceded by an
+@-symbol, in `npm install`:
npm install @myorg/mypackage
diff --git a/deps/npm/doc/misc/npm-scripts.md b/deps/npm/doc/misc/npm-scripts.md
index 7ef8fb1..054886b 100644
--- a/deps/npm/doc/misc/npm-scripts.md
+++ b/deps/npm/doc/misc/npm-scripts.md
@@ -3,7 +3,7 @@ npm-scripts(7) -- How npm handles the "scripts" field
## DESCRIPTION
-npm supports the "scripts" member of the package.json script, for the
+npm supports the "scripts" property of the package.json script, for the
following scripts:
* prepublish:
@@ -33,9 +33,10 @@ following scripts:
Run by the `npm restart` command. Note: `npm restart` will run the
stop and start scripts if no `restart` script is provided.
-Additionally, arbitrary scripts can be executed by running `npm run-script
-`. *Pre* and *post* commands with matching names will be run for
-those as well (e.g. `premyscript`, `myscript`, `postmyscript`).
+Additionally, arbitrary scripts can be executed by running `npm
+run-script `. *Pre* and *post* commands with matching
+names will be run for those as well (e.g. `premyscript`, `myscript`,
+`postmyscript`).
## NOTE: INSTALL SCRIPTS ARE AN ANTIPATTERN
@@ -136,7 +137,7 @@ Configuration parameters are put in the environment with the
`npm_config_` prefix. For instance, you can view the effective `root`
config by checking the `npm_config_root` environment variable.
-### Special: package.json "config" hash
+### Special: package.json "config" object
The package.json "config" keys are overwritten in the environment if
there is a config param of `[@]:`. For example,
diff --git a/deps/npm/doc/misc/semver.md b/deps/npm/doc/misc/semver.md
index af83d71..bd697d9 100644
--- a/deps/npm/doc/misc/semver.md
+++ b/deps/npm/doc/misc/semver.md
@@ -140,7 +140,7 @@ numeric values in the `[major, minor, patch]` tuple.
A partial version range is treated as an X-Range, so the special
character is in fact optional.
-* `` (empty string) := `*` := `>=0.0.0`
+* `""` (empty string) := `*` := `>=0.0.0`
* `1` := `1.x.x` := `>=1.0.0 <2.0.0`
* `1.2` := `1.2.x` := `>=1.2.0 <1.3.0`
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html
index 64bb15f..96bc064 100644
--- a/deps/npm/html/doc/README.html
+++ b/deps/npm/html/doc/README.html
@@ -108,7 +108,7 @@ npm.load(myConfigObject, function (er) {
if (er) return commandFailed(er)
// command succeeded, and data might have some info
})
- npm.on("log", function (message) { .... })
+ npm.registry.log.on("log", function (message) { .... })
})
The load function takes an object hash of the command-line configs.
The various npm.commands.<cmd> functions take an array of
@@ -141,7 +141,7 @@ specific purpose, or lack of malice in any given npm package.
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.
@@ -161,7 +161,7 @@ ban your account in extreme cases. So don't do that.
This acts much the same ways as the npm-cache(1) command line
+
This acts much the same ways as the npm-cache(1) command line
functionality.
The callback is called with the package.json data of the thing that is
eventually added to or read from the cache.
@@ -42,5 +42,5 @@ incrementation.
-
npm-cache — npm@2.0.0
+
npm-cache — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-commands.html b/deps/npm/html/doc/api/npm-commands.html
index 577eae8..3f3ae54 100644
--- a/deps/npm/html/doc/api/npm-commands.html
+++ b/deps/npm/html/doc/api/npm-commands.html
@@ -22,7 +22,7 @@ commands are special and take other optional arguments.
usage, or man 3 npm-<command> for programmatic usage.
@@ -36,5 +36,5 @@ usage, or man 3 npm-<command> for programmatic usage.
-
npm-commands — npm@2.0.0
+
npm-commands — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-config.html b/deps/npm/html/doc/api/npm-config.html
index 37313a9..3767a46 100644
--- a/deps/npm/html/doc/api/npm-config.html
+++ b/deps/npm/html/doc/api/npm-config.html
@@ -43,7 +43,7 @@ the duration of a program, use the npm.config.set and npm.con
functions instead.
diff --git a/deps/npm/html/doc/api/npm-deprecate.html b/deps/npm/html/doc/api/npm-deprecate.html
index dda8857..a235c2b 100644
--- a/deps/npm/html/doc/api/npm-deprecate.html
+++ b/deps/npm/html/doc/api/npm-deprecate.html
@@ -31,9 +31,9 @@ a deprecation warning to all who attempt to install it.
To un-deprecate a package, specify an empty string ("") for the message argument.
@@ -47,5 +47,5 @@ a deprecation warning to all who attempt to install it.
-
npm-deprecate — npm@2.0.0
+
npm-deprecate — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-docs.html b/deps/npm/html/doc/api/npm-docs.html
index 076e9b4..222b90e 100644
--- a/deps/npm/html/doc/api/npm-docs.html
+++ b/deps/npm/html/doc/api/npm-docs.html
@@ -33,5 +33,5 @@ friendly for programmatic use.
-
npm-docs — npm@2.0.0
+
npm-docs — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-edit.html b/deps/npm/html/doc/api/npm-edit.html
index c9702a0..aa3d7bd 100644
--- a/deps/npm/html/doc/api/npm-edit.html
+++ b/deps/npm/html/doc/api/npm-edit.html
@@ -36,5 +36,5 @@ and how this is used.
-
npm-edit — npm@2.0.0
+
npm-edit — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-explore.html b/deps/npm/html/doc/api/npm-explore.html
index be85566..fbfd0cc 100644
--- a/deps/npm/html/doc/api/npm-explore.html
+++ b/deps/npm/html/doc/api/npm-explore.html
@@ -31,5 +31,5 @@ sure to use npm rebuild <pkg> if you make any changes.
-
npm-explore — npm@2.0.0
+
npm-explore — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-help-search.html b/deps/npm/html/doc/api/npm-help-search.html
index 852f0bc..886d0c5 100644
--- a/deps/npm/html/doc/api/npm-help-search.html
+++ b/deps/npm/html/doc/api/npm-help-search.html
@@ -31,7 +31,7 @@ An array of all matching lines (and some adjacent lines).
file:
Name of the file that matched
-
The silent parameter is not neccessary not used, but it may in the future.
+
The silent parameter is not necessary not used, but it may in the future.
@@ -44,5 +44,5 @@ Name of the file that matched
-
npm-help-search — npm@2.0.0
+
npm-help-search — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-init.html b/deps/npm/html/doc/api/npm-init.html
index dac576d..80b14a4 100644
--- a/deps/npm/html/doc/api/npm-init.html
+++ b/deps/npm/html/doc/api/npm-init.html
@@ -26,7 +26,7 @@ JavaScript makes it stupid simple to output formatted JSON, that is the
preferred method. If you're sure you want to handle command-line prompting,
then go ahead and use this programmatically.
@@ -39,5 +39,5 @@ then go ahead and use this programmatically.
-
npm-init — npm@2.0.0
+
npm-init — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-install.html b/deps/npm/html/doc/api/npm-install.html
index 204f1df..43cf4f1 100644
--- a/deps/npm/html/doc/api/npm-install.html
+++ b/deps/npm/html/doc/api/npm-install.html
@@ -32,5 +32,5 @@ installed or when an error has been encountered.
-
npm-install — npm@2.0.0
+
npm-install — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-link.html b/deps/npm/html/doc/api/npm-link.html
index 4eef789..c41a31c 100644
--- a/deps/npm/html/doc/api/npm-link.html
+++ b/deps/npm/html/doc/api/npm-link.html
@@ -42,5 +42,5 @@ the package in the current working directory
npm.load() must be called before any other function call. Both parameters are
optional, but the second is recommended.
-
The first parameter is an object hash of command-line config params, and the
-second parameter is a callback that will be called when npm is loaded and
-ready to serve.
+
The first parameter is an object containing command-line config params, and the
+second parameter is a callback that will be called when npm is loaded and ready
+to serve.
The first parameter should follow a similar structure as the package.json
config object.
For example, to emulate the --dev flag, pass an object that looks like this:
@@ -37,5 +37,5 @@ config object.
-
npm-load — npm@2.0.0
+
npm-load — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-ls.html b/deps/npm/html/doc/api/npm-ls.html
index a3807d8..e221bab 100644
--- a/deps/npm/html/doc/api/npm-ls.html
+++ b/deps/npm/html/doc/api/npm-ls.html
@@ -63,5 +63,5 @@ dependency will only be output once.
-
npm-ls — npm@2.0.0
+
npm-ls — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-outdated.html b/deps/npm/html/doc/api/npm-outdated.html
index c566630..91fafce 100644
--- a/deps/npm/html/doc/api/npm-outdated.html
+++ b/deps/npm/html/doc/api/npm-outdated.html
@@ -28,5 +28,5 @@ currently outdated.
-
npm-outdated — npm@2.0.0
+
npm-outdated — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-owner.html b/deps/npm/html/doc/api/npm-owner.html
index d2b336b..878a9e5 100644
--- a/deps/npm/html/doc/api/npm-owner.html
+++ b/deps/npm/html/doc/api/npm-owner.html
@@ -32,8 +32,8 @@ or you can't. Future versions may contain more fine-grained access levels,
that is not implemented at this time.
diff --git a/deps/npm/html/doc/api/npm-publish.html b/deps/npm/html/doc/api/npm-publish.html
index ae352eb..0e41c2a 100644
--- a/deps/npm/html/doc/api/npm-publish.html
+++ b/deps/npm/html/doc/api/npm-publish.html
@@ -30,9 +30,9 @@ current working directory.
the registry. Overwrites when the "force" environment variable is set.
@@ -46,5 +46,5 @@ the registry. Overwrites when the "force" environment variable is set
-
npm-publish — npm@2.0.0
+
npm-publish — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-rebuild.html b/deps/npm/html/doc/api/npm-rebuild.html
index 1cb5fff..f5d2e6a 100644
--- a/deps/npm/html/doc/api/npm-rebuild.html
+++ b/deps/npm/html/doc/api/npm-rebuild.html
@@ -30,5 +30,5 @@ the new binary. If no 'packages' parameter is specify, every package wil
-
npm-rebuild — npm@2.0.0
+
npm-rebuild — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-repo.html b/deps/npm/html/doc/api/npm-repo.html
index 2c40c8e..024e727 100644
--- a/deps/npm/html/doc/api/npm-repo.html
+++ b/deps/npm/html/doc/api/npm-repo.html
@@ -33,5 +33,5 @@ friendly for programmatic use.
-
npm-repo — npm@2.0.0
+
npm-repo — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-restart.html b/deps/npm/html/doc/api/npm-restart.html
index 382d44a..29d1a56 100644
--- a/deps/npm/html/doc/api/npm-restart.html
+++ b/deps/npm/html/doc/api/npm-restart.html
@@ -21,8 +21,8 @@ the "start" script.
in the packages parameter.
diff --git a/deps/npm/html/doc/api/npm-run-script.html b/deps/npm/html/doc/api/npm-run-script.html
index b5ef687..2670780 100644
--- a/deps/npm/html/doc/api/npm-run-script.html
+++ b/deps/npm/html/doc/api/npm-run-script.html
@@ -23,11 +23,11 @@ one element, then the first is assumed to be the package and the second is
assumed to be the command to run. All other elements are ignored.
diff --git a/deps/npm/html/doc/api/npm-shrinkwrap.html b/deps/npm/html/doc/api/npm-shrinkwrap.html
index e5bf33a..eed523c 100644
--- a/deps/npm/html/doc/api/npm-shrinkwrap.html
+++ b/deps/npm/html/doc/api/npm-shrinkwrap.html
@@ -33,5 +33,5 @@ been saved.
-
npm-shrinkwrap — npm@2.0.0
+
npm-shrinkwrap — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-start.html b/deps/npm/html/doc/api/npm-start.html
index fa8a3db..23678bc 100644
--- a/deps/npm/html/doc/api/npm-start.html
+++ b/deps/npm/html/doc/api/npm-start.html
@@ -28,5 +28,5 @@ in the packages parameter.
-
npm-start — npm@2.0.0
+
npm-start — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-stop.html b/deps/npm/html/doc/api/npm-stop.html
index bdcf72b..ed3b714 100644
--- a/deps/npm/html/doc/api/npm-stop.html
+++ b/deps/npm/html/doc/api/npm-stop.html
@@ -28,5 +28,5 @@ in the packages parameter.
-
npm-stop — npm@2.0.0
+
npm-stop — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-submodule.html b/deps/npm/html/doc/api/npm-submodule.html
index f7dfcca..d70ee36 100644
--- a/deps/npm/html/doc/api/npm-submodule.html
+++ b/deps/npm/html/doc/api/npm-submodule.html
@@ -42,5 +42,5 @@ dependencies into the submodule folder.
-
npm-submodule — npm@2.0.0
+
npm-submodule — npm@2.1.2
diff --git a/deps/npm/html/doc/api/npm-tag.html b/deps/npm/html/doc/api/npm-tag.html
index 2f94ed7..b4a3261 100644
--- a/deps/npm/html/doc/api/npm-tag.html
+++ b/deps/npm/html/doc/api/npm-tag.html
@@ -36,5 +36,5 @@ used. For more information about how to set this config, check
-
npm-tag — npm@2.0.0
+
npm-tag — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-test.html b/deps/npm/html/doc/api/npm-test.html
index 3247238..7816808 100644
--- a/deps/npm/html/doc/api/npm-test.html
+++ b/deps/npm/html/doc/api/npm-test.html
@@ -30,5 +30,5 @@ in the packages parameter.
-
npm-test — npm@2.0.0
+
npm-test — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-uninstall.html b/deps/npm/html/doc/api/npm-uninstall.html
index ffd317e..962ff87 100644
--- a/deps/npm/html/doc/api/npm-uninstall.html
+++ b/deps/npm/html/doc/api/npm-uninstall.html
@@ -30,5 +30,5 @@ uninstalled or when an error has been encountered.
-
npm-uninstall — npm@2.0.0
+
npm-uninstall — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-unpublish.html b/deps/npm/html/doc/api/npm-unpublish.html
index e35acac..2b9a5c5 100644
--- a/deps/npm/html/doc/api/npm-unpublish.html
+++ b/deps/npm/html/doc/api/npm-unpublish.html
@@ -33,5 +33,5 @@ the root package entry is removed from the registry entirely.
diff --git a/deps/npm/html/doc/api/npm-version.html b/deps/npm/html/doc/api/npm-version.html
index 376d8b9..c4ce078 100644
--- a/deps/npm/html/doc/api/npm-version.html
+++ b/deps/npm/html/doc/api/npm-version.html
@@ -32,5 +32,5 @@ not have exactly one element. The only element should be a version number.
-
npm-version — npm@2.0.0
+
npm-version — npm@2.1.6
diff --git a/deps/npm/html/doc/api/npm-view.html b/deps/npm/html/doc/api/npm-view.html
index 482d912..75c75fd 100644
--- a/deps/npm/html/doc/api/npm-view.html
+++ b/deps/npm/html/doc/api/npm-view.html
@@ -81,5 +81,5 @@ the field name.
This is the API documentation for npm.
To find documentation of the command line
-client, see npm(1).
-
Prior to using npm's commands, npm.load() must be called.
-If you provide configObject as an object hash of top-level
-configs, they override the values stored in the various config
-locations. In the npm command line client, this set of configs
-is parsed from the command line options. Additional configuration
-params are loaded from two configuration files. See npm-config(1),
-npm-config(7), and npmrc(5) for more information.
Prior to using npm's commands, npm.load() must be called. If you provide
+configObject as an object map of top-level configs, they override the values
+stored in the various config locations. In the npm command line client, this
+set of configs is parsed from the command line options. Additional
+configuration params are loaded from two configuration files. See
+npm-config(1), npm-config(7), and npmrc(5) for more information.
After that, each of the functions are accessible in the
-commands object: npm.commands.<cmd>. See npm-index(7) for a list of
+commands object: npm.commands.<cmd>. See npm-index(7) for a list of
all possible commands.
All commands on the command object take an array of positional argument
strings. The last argument to any function is a callback. Some
@@ -80,9 +79,9 @@ command.
MAGIC
-
For each of the methods in the npm.commands hash, a method is added to
-the npm object, which takes a set of positional string arguments rather
-than an array and a callback.
+
For each of the methods in the npm.commands object, a method is added to the
+npm object, which takes a set of positional string arguments rather than an
+array and a callback.
If the last argument is a callback, then it will use the supplied
callback. However, if no callback is provided, then it will print out
the error or results.
@@ -110,5 +109,5 @@ method names. Use the npm.deref method to find the real name.
Create or verify a user named <username> in the specified registry, and
save the credentials to the .npmrc file. If no registry is specified,
-the default registry will be used (see npm-config(7)).
+the default registry will be used (see npm-config(7)).
The username, password, and email are read in from prompts.
You may use this command to change your email address, but not username
or password.
The base URL of the npm package registry. If scope is also specified,
-this registry will only be used for packages with that scope. See npm-scope(7).
+this registry will only be used for packages with that scope. See npm-scope(7).
scope
Default: none
If specified, the user and login credentials given will be associated
-with the specified scope. See npm-scope(7). You can use both at the same time,
+with the specified scope. See npm-scope(7). You can use both at the same time,
e.g.
This will set a registry for the given scope and login or create a user for
that registry at the same time.
+
always-auth
+
Default: false
+
If specified, save configuration indicating that all requests to the given
+registry should include authorization information. Useful for private
+registries. Can be used with --registry and / or --scope, e.g.
This will ensure that all requests to that registry (including for tarballs)
+include an authorization header. See always-auth in npm-config(7) for more
+details on always-auth. Registry-specific configuaration of always-auth takes
+precedence over any global configuration.
diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html
index e7ce93b..7758efa 100644
--- a/deps/npm/html/doc/cli/npm-bugs.html
+++ b/deps/npm/html/doc/cli/npm-bugs.html
@@ -33,14 +33,14 @@ a package.json in the current folder and use the name
@@ -54,5 +54,5 @@ a package.json in the current folder and use the name
-
npm-bugs — npm@2.0.0
+
npm-bugs — npm@2.1.6
diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html
index e2f60bb..ca62cb2 100644
--- a/deps/npm/html/doc/cli/npm-build.html
+++ b/deps/npm/html/doc/cli/npm-build.html
@@ -21,10 +21,10 @@ A folder containing a package.json file in its root.
@@ -31,5 +31,5 @@ install packages into the local space.
-
npm-bundle — npm@2.0.0
+
npm-bundle — npm@2.1.6
diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html
index a384b71..53835b3 100644
--- a/deps/npm/html/doc/cli/npm-cache.html
+++ b/deps/npm/html/doc/cli/npm-cache.html
@@ -61,13 +61,13 @@ they do not make an HTTP request to the registry.
@@ -81,5 +81,5 @@ they do not make an HTTP request to the registry.
-
npm-cache — npm@2.0.0
+
npm-cache — npm@2.1.6
diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html
index 2d0dae8..5a678ba 100644
--- a/deps/npm/html/doc/cli/npm-completion.html
+++ b/deps/npm/html/doc/cli/npm-completion.html
@@ -26,9 +26,9 @@ environment, npm completion acts in "plumbing mode", and
completions based on the arguments.
diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html
index 14f4479..e9f2c9e 100644
--- a/deps/npm/html/doc/cli/npm-docs.html
+++ b/deps/npm/html/doc/cli/npm-docs.html
@@ -36,13 +36,13 @@ the current folder and use the name property.
diff --git a/deps/npm/html/doc/cli/npm-help-search.html b/deps/npm/html/doc/cli/npm-help-search.html
index 22ddb9d..2cf7506 100644
--- a/deps/npm/html/doc/cli/npm-help-search.html
+++ b/deps/npm/html/doc/cli/npm-help-search.html
@@ -30,9 +30,9 @@ where the terms were found in the documentation.
If false, then help-search will just list out the help topics found.
This will ask you a bunch of questions, and then write a package.json for you.
It attempts to make reasonable guesses about what you want things to be set to,
@@ -20,11 +20,13 @@ and then writes a package.json file with the options you've selected.
the options in there.
It is strictly additive, so it does not delete options from your package.json
without a really good reason to do so.
+
If you invoke it with -f, --force, -y, or --yes, it will use only
+defaults and not prompt you for any options.
@@ -38,5 +40,5 @@ without a really good reason to do so.
-
npm-init — npm@2.0.0
+
npm-init — npm@2.1.6
diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html
index 38d160f..3759f01 100644
--- a/deps/npm/html/doc/cli/npm-install.html
+++ b/deps/npm/html/doc/cli/npm-install.html
@@ -23,13 +23,13 @@ npm i (with any of the previous argument usage)
DESCRIPTION
This command installs a package, and any packages that it depends on. If the
package has a shrinkwrap file, the installation of dependencies will be driven
-by that. See npm-shrinkwrap(1).
In most cases, this will install the latest version
of the module published on npm.
Example:
@@ -87,7 +87,7 @@ exact version rather than using npm's default semver range
operator.
<scope> is optional. The package will be downloaded from the registry
associated with the specified scope. If no registry is associated with
-the given scope the default registry is assumed. See npm-scope(7).
+the given scope the default registry is assumed. See npm-scope(7).
Note: if you do not include the @-symbol on your scope name, npm will
interpret this as a GitHub repository instead, see below. Scopes names
must also be followed by a slash.
@@ -123,7 +123,7 @@ fetch the package by name if it is not valid.
npm install [@<scope>/]<name>@<version range>:
Install a version of the package matching the specified version range. This
- will follow the same rules for resolving dependencies described in package.json(5).
+ will follow the same rules for resolving dependencies described in package.json(5).
Note that most version ranges must be put in quotes so that your shell will
treat it as a single argument.
Example:
@@ -161,7 +161,7 @@ versions.
local copy exists on disk.
npm install sax --force
The --global argument will cause npm to install the package globally
-rather than locally. See npm-folders(5).
The --link argument will cause npm to link global installs into the
local space in some cases.
The --no-bin-links argument will prevent npm from creating symlinks for
@@ -172,7 +172,7 @@ being installed.
shrinkwrap file and use the package.json instead.
The --nodedir=/path/to/node/source argument will allow npm to find the
node source code so that npm can compile native modules.
-
See npm-config(7). Many of the configuration params have some
+
See npm-config(7). Many of the configuration params have some
effect on installation, since that's most of what npm does.
ALGORITHM
To install a package, npm uses the following algorithm:
@@ -193,7 +193,7 @@ this algorithm produces:
`-- D
That is, the dependency from B to C is satisfied by the fact that A
already caused C to be installed at a higher level.
-
See npm-folders(5) for a more detailed description of the specific
+
See npm-folders(5) for a more detailed description of the specific
folder structures that npm creates.
Limitations of npm's Install Algorithm
There are some very rare and pathological edge-cases where a cycle can
@@ -213,19 +213,19 @@ to symlink the existing version into the new location. If this ever
affects a real use-case, it will be investigated.
@@ -239,5 +239,5 @@ affects a real use-case, it will be investigated.
-
npm-install — npm@2.0.0
+
npm-install — npm@2.1.6
diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html
index 0d28a7d..8d08589 100644
--- a/deps/npm/html/doc/cli/npm-link.html
+++ b/deps/npm/html/doc/cli/npm-link.html
@@ -18,12 +18,12 @@ npm ln (with any of the previous argument usage)
Package linking is a two-step process.
First, npm link in a package folder will create a globally-installed
symbolic link from prefix/package-name to the current folder (see
-npm-config(7) for the value of prefix).
diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html
index a52b117..30419bd 100644
--- a/deps/npm/html/doc/cli/npm-ls.html
+++ b/deps/npm/html/doc/cli/npm-ls.html
@@ -22,7 +22,7 @@ installed, as well as their dependencies, in a tree-structure.
limit the results to only the paths to the packages named. Note that
nested packages will also show the paths to the specified packages.
For example, running npm ls promzard in npm's source tree will show:
-
diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html
index b2f8f84..3600e08 100644
--- a/deps/npm/html/doc/cli/npm-owner.html
+++ b/deps/npm/html/doc/cli/npm-owner.html
@@ -32,10 +32,10 @@ or you can't. Future versions may contain more fine-grained access levels,
that is not implemented at this time.
Publishes a package to the registry so that it can be installed by name.
+
Publishes a package to the registry so that it can be installed by name. See
+npm-developers(7) for details on what's included in the published package, as
+well as details on how the package is built.
By default npm will publish to the public registry. This can be overridden by
-specifying a different default registry or using a npm-scope(7) in the name
-(see package.json(5)).
@@ -36,14 +38,14 @@ and npm install installs the latest tag.
the specified registry.
Once a package is published with a given name and version, that
specific name and version combination can never be used again, even if
-it is removed with npm-unpublish(1).
diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html
index 01d0f33..4da97a7 100644
--- a/deps/npm/html/doc/cli/npm-rebuild.html
+++ b/deps/npm/html/doc/cli/npm-rebuild.html
@@ -23,8 +23,8 @@ when you install a new version of node, and must recompile all your C++ addons w
the new binary.
diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html
index 350f2fd..02335b4 100644
--- a/deps/npm/html/doc/cli/npm-repo.html
+++ b/deps/npm/html/doc/cli/npm-repo.html
@@ -27,8 +27,8 @@ a package.json in the current folder and use the name
The browser that is called by the npm repo command to open websites.
This runs a package's "restart" script, if one was provided.
-Otherwise it runs package's "stop" script, if one was provided, and then
-the "start" script.
-
If no version is specified, then it restarts the "active" version.
+
This runs a package's "restart" script, if one was provided. Otherwise it runs
+package's "stop" script, if one was provided, and then the "start" script.
diff --git a/deps/npm/html/doc/cli/npm-run-script.html b/deps/npm/html/doc/cli/npm-run-script.html
index dec511c..8ca2ea2 100644
--- a/deps/npm/html/doc/cli/npm-run-script.html
+++ b/deps/npm/html/doc/cli/npm-run-script.html
@@ -20,13 +20,20 @@ in the current folder and use its "scripts" object. If no
is provided, it will list the available top level scripts.
It is used by the test, start, restart, and stop commands, but can be
called directly, as well.
+
As of npm@2.0.0, you can
+use custom arguments when executing scripts. The special option -- is used by
+getopt to delimit the end of the options. npm will pass
+all the arguments after the -- directly to your script:
+
npm run test -- --grep="pattern"
+
The arguments will only be passed to the script specified after npm run
+and not to any pre or post script.
diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html
index fac2fac..f5fe720 100644
--- a/deps/npm/html/doc/cli/npm-search.html
+++ b/deps/npm/html/doc/cli/npm-search.html
@@ -31,11 +31,11 @@ neatly on a single line. Modules with extremely long names will
fall on multiple lines.
Run "npm shrinkwrap", commit the new npm-shrinkwrap.json, and
publish your package.
-
You can use npm-outdated(1) to view dependencies with newer versions
+
You can use npm-outdated(1) to view dependencies with newer versions
available.
Other Notes
A shrinkwrap file must be consistent with the package's package.json
@@ -148,9 +148,9 @@ source control, or pursue some other mechanism that can verify
contents rather than versions.
@@ -164,5 +164,5 @@ contents rather than versions.
-
npm-shrinkwrap — npm@2.0.0
+
npm-shrinkwrap — npm@2.1.6
diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html
index 9b70357..d3bbde5 100644
--- a/deps/npm/html/doc/cli/npm-star.html
+++ b/deps/npm/html/doc/cli/npm-star.html
@@ -20,9 +20,9 @@ a vaguely positive way to show that you care.
It's a boolean thing. Starring repeatedly has no additional effect.
@@ -36,5 +36,5 @@ a vaguely positive way to show that you care.
-
npm-star — npm@2.0.0
+
npm-star — npm@2.1.6
diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html
index 9c3b24d..7873880 100644
--- a/deps/npm/html/doc/cli/npm-stars.html
+++ b/deps/npm/html/doc/cli/npm-stars.html
@@ -20,10 +20,10 @@ quickly this command lets you do just that.
you will most certainly enjoy this command.
diff --git a/deps/npm/html/doc/cli/npm-submodule.html b/deps/npm/html/doc/cli/npm-submodule.html
index 899005f..4ac55a8 100644
--- a/deps/npm/html/doc/cli/npm-submodule.html
+++ b/deps/npm/html/doc/cli/npm-submodule.html
@@ -27,7 +27,7 @@ or you can do npm explore <pkgname> -- npm install to install
dependencies into the submodule folder.
@@ -42,5 +42,5 @@ dependencies into the submodule folder.
-
npm-submodule — npm@2.0.0
+
npm-submodule — npm@2.1.2
diff --git a/deps/npm/html/doc/cli/npm-tag.html b/deps/npm/html/doc/cli/npm-tag.html
index 7dfbd18..946d5fa 100644
--- a/deps/npm/html/doc/cli/npm-tag.html
+++ b/deps/npm/html/doc/cli/npm-tag.html
@@ -24,13 +24,13 @@ of using a specific version number:
Publishing a package always sets the "latest" tag to the published version.
diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html
index c4e7858..2a3c12c 100644
--- a/deps/npm/html/doc/cli/npm-uninstall.html
+++ b/deps/npm/html/doc/cli/npm-uninstall.html
@@ -30,7 +30,7 @@ the package version in your main package.json:
--save-optional: Package will be removed from your optionalDependencies.
-
Scope is optional and follows the usual rules for npm-scope(7).
+
Scope is optional and follows the usual rules for npm-scope(7).
diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html
index eb17592..59b278e 100644
--- a/deps/npm/html/doc/cli/npm-unpublish.html
+++ b/deps/npm/html/doc/cli/npm-unpublish.html
@@ -26,14 +26,14 @@ the root package entry is removed from the registry entirely.
Even if a package version is unpublished, that specific name and
version combination can never be reused. In order to publish the
package again, a new version number must be used.
-
The scope is optional and follows the usual rules for npm-scope(7).
+
The scope is optional and follows the usual rules for npm-scope(7).
"Person" fields are shown as a string if they would be shown as an
object. So, for example, this will show the list of npm contributors in
-the shortened string format. (See package.json(5) for more on this.)
+the shortened string format. (See package.json(5) for more on this.)
npm view npm contributors
If a version range is provided, then data will be printed for every
matching version of the package. This will show which version of jsdom
@@ -63,12 +63,12 @@ will be prefixed with the version it applies to.
npm is the package manager for the Node JavaScript platform. It puts
modules in place so that node can find them, and manages dependency
@@ -25,7 +25,7 @@ programs.
INTRODUCTION
You probably got npm because you want to install stuff.
Use npm install blerg to install the latest version of "blerg". Check out
-npm-install(1) for more info. It can do a lot of stuff.
+npm-install(1) for more info. It can do a lot of stuff.
Use the npm search command to show everything that's available.
Use npm ls to show everything you've installed.
link:
For linking your current working code into Node's path, so that you
don't have to reinstall every time you make a change. Use
@@ -93,12 +93,12 @@ then that file is parsed instead.
Defaults: npm's default configuration options are defined in
lib/utils/config-defs.js. These must not be changed.
code:
-Read through npm-coding-style(7) if you plan to submit code.
+Read through npm-coding-style(7) if you plan to submit code.
You don't have to agree with it, but you do have to follow it.
docs:
If you find an error in the documentation, edit the appropriate markdown
@@ -110,7 +110,7 @@ easily by doing npm view npm contributors.
the issues list or ask on the mailing list.
@@ -154,5 +154,5 @@ will no doubt tell you to put the output in a gist or email.
-
npm — npm@2.0.0
+
npm — npm@2.1.6
diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html
index cb2b56c..ec32039 100644
--- a/deps/npm/html/doc/files/npm-folders.html
+++ b/deps/npm/html/doc/files/npm-folders.html
@@ -44,7 +44,7 @@ Global installs on Windows go to {prefix}/node_modules (that is, no
Scoped packages are installed the same way, except they are grouped together
in a sub-folder of the relevant node_modules folder with the name of that
scope prefix by the @ symbol, e.g. npm install @myorg/package would place
-the package in {prefix}/node_modules/@myorg/package. See scopes(7) for
+the package in {prefix}/node_modules/@myorg/package. See scopes(7) for
more details.
If you wish to require() a package, then install it locally.
Executables
@@ -59,7 +59,7 @@ when you run npm test.)
When in local mode, man pages are not installed.
Man pages are not installed on Windows systems.
Cache
-
See npm-cache(1). Cache files are stored in ~/.npm on Posix, or
+
See npm-cache(1). Cache files are stored in ~/.npm on Posix, or
~/npm-cache on Windows.
This is controlled by the cache configuration param.
Temp Files
@@ -159,18 +159,18 @@ the items there are not in the bundledDependencies array, then they
not be included in the package tarball.
This allows a package maintainer to install all of their dependencies
(and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere. See package.json(5) for more information.
+cannot be found elsewhere. See package.json(5) for more information.
If you wish to require() a package, then install it locally.
Executables
@@ -59,7 +59,7 @@ when you run npm test.)
When in local mode, man pages are not installed.
Man pages are not installed on Windows systems.
Cache
-
See npm-cache(1). Cache files are stored in ~/.npm on Posix, or
+
See npm-cache(1). Cache files are stored in ~/.npm on Posix, or
~/npm-cache on Windows.
This is controlled by the cache configuration param.
Temp Files
@@ -159,18 +159,18 @@ the items there are not in the bundledDependencies array, then they
not be included in the package tarball.
This allows a package maintainer to install all of their dependencies
(and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere. See package.json(5) for more information.
+cannot be found elsewhere. See package.json(5) for more information.
The most important things in your package.json are the name and version fields.
Those are actually required, and your package won't install without
@@ -35,7 +35,7 @@ be something short, but also reasonably descriptive.
already, before you get too attached to it. http://registry.npmjs.org/
A name can be optionally prefixed by a scope, e.g. @myorg/mypackage. See
-npm-scope(7) for more detail.
The most important things in your package.json are the name and version fields.
Those are actually required, and your package won't install without
@@ -45,7 +45,7 @@ changes to the version.
Version must be parseable by
node-semver, which is bundled
with npm as a dependency. (npm install semver to use it yourself.)
Put a description in it. It's a string. This helps people discover your
package, as it's listed in npm search.
@@ -161,16 +161,16 @@ compressed. The number dictates which man section the file is installed into.
directories
The CommonJS Packages spec details a
few ways that you can indicate the structure of your package using a directories
-hash. If you look at npm's package.json,
+object. If you look at npm's package.json,
you'll see that it has directories for doc, lib, and man.
In the future, this information may be used in other creative ways.
directories.lib
Tell people where the bulk of your library is. Nothing special is done
with the lib folder in any way, but it's useful meta info.
directories.bin
-
If you specify a "bin" directory, then all the files in that folder will
-be used as the "bin" hash.
-
If you have a "bin" hash already, then this has no effect.
+
If you specify a bin directory, then all the files in that folder will
+be added as children of the bin path.
+
If you have a bin path already, then this has no effect.
directories.man
A folder that is full of man pages. Sugar to generate a "man" array by
walking the folder.
@@ -197,37 +197,37 @@ command will be able to find you.
directly to a VCS program without any modification. It should not be a url to an
html project page that you put in your browser. It's for computers.
scripts
-
The "scripts" member is an object hash of script commands that are run
+
The "scripts" property is a dictionary containing script commands that are run
at various times in the lifecycle of your package. The key is the lifecycle
event, and the value is the command to run at that point.
-
See npm-scripts(7) to find out more about writing package scripts.
+
See npm-scripts(7) to find out more about writing package scripts.
config
-
A "config" hash can be used to set configuration
-parameters used in package scripts that persist across upgrades. For
-instance, if a package had the following:
+
A "config" object can be used to set configuration parameters used in package
+scripts that persist across upgrades. For instance, if a package had the
+following:
and then had a "start" command that then referenced the
npm_package_config_port environment variable, then the user could
override that by doing npm config set foo:port 8001.
Dependencies are specified with a simple hash of package name to
+
Dependencies are specified in a simple object that maps a package name to a
version range. The version range is a string which has one or more
-space-separated descriptors. Dependencies can also be identified with
-a tarball or git URL.
+space-separated descriptors. Dependencies can also be identified with a
+tarball or git URL.
Please do not put test harnesses or transpilers in your
-dependencies hash. See devDependencies, below.
-
See semver(7) for more details about specifying version ranges.
+dependencies object. See devDependencies, below.
+
See semver(7) for more details about specifying version ranges.
version Must match version exactly
>version Must be greater than version
>=version etc
<version
<=version
-
~version "Approximately equivalent to version" See semver(7)
@@ -278,12 +278,21 @@ an argument to git checkout. The default is master.
}
}
Local Paths
-
As of version 2.0.0 you can provide a path to a local directory that
-contains a package. Local paths can be in the form:
+
As of version 2.0.0 you can provide a path to a local directory that contains a
+package. Local paths can be saved using npm install --save, using any of
+these forms:
../foo/bar
~/foo/bar
./foo/bar
/foo/bar
+
in which case they will be normalized to a relative path and added to your
+package.json. For example:
This feature is helpful for local offline development and creating
tests that require npm installing where you don't want to hit an
external server, but should not be used when publishing packages
@@ -292,11 +301,11 @@ to the public registry.
If someone is planning on downloading and using your module in their
program, then they probably don't want or need to download and build
the external test or documentation framework that you use.
-
In this case, it's best to list these additional items in a
-devDependencies hash.
+
In this case, it's best to map these additional items in a devDependencies
+object.
These things will be installed when doing npm link or npm install
from the root of a package, and can be managed like any other npm
-configuration param. See npm-config(7) for more on the topic.
+configuration param. See npm-config(7) for more on the topic.
For build steps that are not platform-specific, such as compiling
CoffeeScript or other languages to JavaScript, use the prepublish
script to do this, and make the required package a devDependency.
@@ -346,11 +355,11 @@ this. If you depend on features introduced in 1.5.2, use ">= 1.5.2
Array of package names that will be bundled when publishing the package.
If this is spelled "bundleDependencies", then that is also honorable.
optionalDependencies
-
If a dependency can be used, but you would like npm to proceed if it
-cannot be found or fails to install, then you may put it in the
-optionalDependencies hash. This is a map of package name to version
-or url, just like the dependencies hash. The difference is that
-failure is tolerated.
+
If a dependency can be used, but you would like npm to proceed if it cannot be
+found or fails to install, then you may put it in the optionalDependencies
+object. This is a map of package name to version or url, just like the
+dependencies object. The difference is that build failures do not cause
+installation to fail.
It is still your program's responsibility to handle the lack of the
dependency. For example, something like this:
try {
@@ -385,11 +394,11 @@ are capable of properly installing your program. For example:
field is advisory only.
engineStrict
If you are sure that your module will definitely not run properly on
-versions of Node/npm other than those specified in the engines hash,
+versions of Node/npm other than those specified in the engines object,
then you can set "engineStrict": true in your package.json file.
This will override the user's engine-strict config setting.
Please do not do this unless you are really very very sure. If your
-engines hash is something overly restrictive, you can quite easily and
+engines object is something overly restrictive, you can quite easily and
inadvertently lock yourself into obscurity and prevent your users from
updating to new versions of Node. Consider this choice carefully. If
people abuse it, it will be removed in a future version of npm.
@@ -419,11 +428,11 @@ does help prevent some confusion if it doesn't work as expected.
private
If you set "private": true in your package.json, then npm will refuse
to publish it.
-
This is a way to prevent accidental publication of private repositories.
-If you would like to ensure that a given package is only ever published
-to a specific registry (for example, an internal registry),
-then use the publishConfig hash described below
-to override the registry config param at publish-time.
+
This is a way to prevent accidental publication of private repositories. If
+you would like to ensure that a given package is only ever published to a
+specific registry (for example, an internal registry), then use the
+publishConfig dictionary described below to override the registry config
+param at publish-time.
publishConfig
This is a set of config values that will be used at publish-time. It's
especially handy if you want to set the tag or registry, so that you can
@@ -431,7 +440,7 @@ ensure that a given package is not tagged with "latest" or published t
the global public registry by default.
Any config values can be overridden, but of course only "tag" and
"registry" probably matter for the purposes of publishing.
-
See npm-config(7) to see the list of config options that can be
+
See npm-config(7) to see the list of config options that can be
overridden.
DEFAULT VALUES
npm will default some values based on package contents.
The most important things in your package.json are the name and version fields.
Those are actually required, and your package won't install without
@@ -35,7 +35,7 @@ be something short, but also reasonably descriptive.
already, before you get too attached to it. http://registry.npmjs.org/
A name can be optionally prefixed by a scope, e.g. @myorg/mypackage. See
-npm-scope(7) for more detail.
The most important things in your package.json are the name and version fields.
Those are actually required, and your package won't install without
@@ -45,7 +45,7 @@ changes to the version.
Version must be parseable by
node-semver, which is bundled
with npm as a dependency. (npm install semver to use it yourself.)
Put a description in it. It's a string. This helps people discover your
package, as it's listed in npm search.
@@ -161,16 +161,16 @@ compressed. The number dictates which man section the file is installed into.
directories
The CommonJS Packages spec details a
few ways that you can indicate the structure of your package using a directories
-hash. If you look at npm's package.json,
+object. If you look at npm's package.json,
you'll see that it has directories for doc, lib, and man.
In the future, this information may be used in other creative ways.
directories.lib
Tell people where the bulk of your library is. Nothing special is done
with the lib folder in any way, but it's useful meta info.
directories.bin
-
If you specify a "bin" directory, then all the files in that folder will
-be used as the "bin" hash.
-
If you have a "bin" hash already, then this has no effect.
+
If you specify a bin directory, then all the files in that folder will
+be added as children of the bin path.
+
If you have a bin path already, then this has no effect.
directories.man
A folder that is full of man pages. Sugar to generate a "man" array by
walking the folder.
@@ -197,37 +197,37 @@ command will be able to find you.
directly to a VCS program without any modification. It should not be a url to an
html project page that you put in your browser. It's for computers.
scripts
-
The "scripts" member is an object hash of script commands that are run
+
The "scripts" property is a dictionary containing script commands that are run
at various times in the lifecycle of your package. The key is the lifecycle
event, and the value is the command to run at that point.
-
See npm-scripts(7) to find out more about writing package scripts.
+
See npm-scripts(7) to find out more about writing package scripts.
config
-
A "config" hash can be used to set configuration
-parameters used in package scripts that persist across upgrades. For
-instance, if a package had the following:
+
A "config" object can be used to set configuration parameters used in package
+scripts that persist across upgrades. For instance, if a package had the
+following:
and then had a "start" command that then referenced the
npm_package_config_port environment variable, then the user could
override that by doing npm config set foo:port 8001.
Dependencies are specified with a simple hash of package name to
+
Dependencies are specified in a simple object that maps a package name to a
version range. The version range is a string which has one or more
-space-separated descriptors. Dependencies can also be identified with
-a tarball or git URL.
+space-separated descriptors. Dependencies can also be identified with a
+tarball or git URL.
Please do not put test harnesses or transpilers in your
-dependencies hash. See devDependencies, below.
-
See semver(7) for more details about specifying version ranges.
+dependencies object. See devDependencies, below.
+
See semver(7) for more details about specifying version ranges.
version Must match version exactly
>version Must be greater than version
>=version etc
<version
<=version
-
~version "Approximately equivalent to version" See semver(7)
@@ -278,12 +278,21 @@ an argument to git checkout. The default is master.
}
}
Local Paths
-
As of version 2.0.0 you can provide a path to a local directory that
-contains a package. Local paths can be in the form:
+
As of version 2.0.0 you can provide a path to a local directory that contains a
+package. Local paths can be saved using npm install --save, using any of
+these forms:
../foo/bar
~/foo/bar
./foo/bar
/foo/bar
+
in which case they will be normalized to a relative path and added to your
+package.json. For example:
This feature is helpful for local offline development and creating
tests that require npm installing where you don't want to hit an
external server, but should not be used when publishing packages
@@ -292,11 +301,11 @@ to the public registry.
If someone is planning on downloading and using your module in their
program, then they probably don't want or need to download and build
the external test or documentation framework that you use.
-
In this case, it's best to list these additional items in a
-devDependencies hash.
+
In this case, it's best to map these additional items in a devDependencies
+object.
These things will be installed when doing npm link or npm install
from the root of a package, and can be managed like any other npm
-configuration param. See npm-config(7) for more on the topic.
+configuration param. See npm-config(7) for more on the topic.
For build steps that are not platform-specific, such as compiling
CoffeeScript or other languages to JavaScript, use the prepublish
script to do this, and make the required package a devDependency.
@@ -346,11 +355,11 @@ this. If you depend on features introduced in 1.5.2, use ">= 1.5.2
Array of package names that will be bundled when publishing the package.
If this is spelled "bundleDependencies", then that is also honorable.
optionalDependencies
-
If a dependency can be used, but you would like npm to proceed if it
-cannot be found or fails to install, then you may put it in the
-optionalDependencies hash. This is a map of package name to version
-or url, just like the dependencies hash. The difference is that
-failure is tolerated.
+
If a dependency can be used, but you would like npm to proceed if it cannot be
+found or fails to install, then you may put it in the optionalDependencies
+object. This is a map of package name to version or url, just like the
+dependencies object. The difference is that build failures do not cause
+installation to fail.
It is still your program's responsibility to handle the lack of the
dependency. For example, something like this:
try {
@@ -385,11 +394,11 @@ are capable of properly installing your program. For example:
field is advisory only.
engineStrict
If you are sure that your module will definitely not run properly on
-versions of Node/npm other than those specified in the engines hash,
+versions of Node/npm other than those specified in the engines object,
then you can set "engineStrict": true in your package.json file.
This will override the user's engine-strict config setting.
Please do not do this unless you are really very very sure. If your
-engines hash is something overly restrictive, you can quite easily and
+engines object is something overly restrictive, you can quite easily and
inadvertently lock yourself into obscurity and prevent your users from
updating to new versions of Node. Consider this choice carefully. If
people abuse it, it will be removed in a future version of npm.
@@ -419,11 +428,11 @@ does help prevent some confusion if it doesn't work as expected.
private
If you set "private": true in your package.json, then npm will refuse
to publish it.
-
This is a way to prevent accidental publication of private repositories.
-If you would like to ensure that a given package is only ever published
-to a specific registry (for example, an internal registry),
-then use the publishConfig hash described below
-to override the registry config param at publish-time.
+
This is a way to prevent accidental publication of private repositories. If
+you would like to ensure that a given package is only ever published to a
+specific registry (for example, an internal registry), then use the
+publishConfig dictionary described below to override the registry config
+param at publish-time.
publishConfig
This is a set of config values that will be used at publish-time. It's
especially handy if you want to set the tag or registry, so that you can
@@ -431,7 +440,7 @@ ensure that a given package is not tagged with "latest" or published t
the global public registry by default.
Any config values can be overridden, but of course only "tag" and
"registry" probably matter for the purposes of publishing.
-
See npm-config(7) to see the list of config options that can be
+
See npm-config(7) to see the list of config options that can be
overridden.
DEFAULT VALUES
npm will default some values based on package contents.
diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html
index 5d94f84..30d3e07 100644
--- a/deps/npm/html/doc/misc/npm-coding-style.html
+++ b/deps/npm/html/doc/misc/npm-coding-style.html
@@ -109,11 +109,11 @@ utility.
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
occurs.
-
Use appropriate log levels. See npm-config(7) and search for
+
Use appropriate log levels. See npm-config(7) and search for
"loglevel".
Case, naming, etc.
Use lowerCamelCase for multiword identifiers when they refer to objects,
-functions, methods, members, or anything not specified in this section.
+functions, methods, properties, or anything not specified in this section.
Use UpperCamelCase for class names (things that you'd pass to "new").
Use all-lower-hyphen-css-case for multiword filenames and config keys.
Use named functions. They make stack traces easier to follow.
A set of configuration parameters that are internal to npm, and are
defaults if nothing else is specified.
@@ -79,7 +79,7 @@ example:
# same as:
npm ls --global --parseable --long --loglevel info
Per-Package Config Settings
-
When running scripts (see npm-scripts(7)) the package.json "config"
+
When running scripts (see npm-scripts(7)) the package.json "config"
keys are overwritten in the environment if there is a config param of
<name>[@<version>]:<key>. For example, if the package.json has
this:
The location of npm's cache directory. See npm-cache(1)
+
The location of npm's cache directory. See npm-cache(1)
cache-lock-stale
Default: 60000 (1 minute)
@@ -285,7 +285,7 @@ the git binary.
Operates in "global" mode, so that packages are installed into the
prefix folder instead of the current working directory. See
-npm-folders(5) for more on the differences in behavior.
+npm-folders(5) for more on the differences in behavior.
packages are installed into the {prefix}/lib/node_modules folder, instead of the
current working directory.
@@ -332,32 +332,32 @@ user.
A module that will be loaded by the npm init command. See the
documentation for the
init-package-json module
-for more information, or npm-init(1).
What level of logs to report. On failure, all logs are written to
npm-debug.log in the current working directory.
Any logs of a higher level than the setting are shown.
-The default is "http", which shows http, warn, and error output.
+The default is "warn", which shows warn and error output.
logstream
Default: process.stderr
@@ -441,7 +441,7 @@ colored output if it is a TTY.
Default: process.version
Type: semver or false
-
The node version to use when checking package's "engines" hash.
+
The node version to use when checking a package's engines map.
npat
Default: false
@@ -460,7 +460,7 @@ usage.
Default: true
Type: Boolean
-
Attempt to install packages in the optionalDependencies hash. Note
+
Attempt to install packages in the optionalDependencies object. Note
that if these packages fail to install, the overall installation
process is not aborted.
parseable
@@ -472,7 +472,7 @@ process is not aborted.
standard output.
diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html
index 1734785..b4190a1 100644
--- a/deps/npm/html/doc/misc/npm-developers.html
+++ b/deps/npm/html/doc/misc/npm-developers.html
@@ -45,7 +45,7 @@ an argument to git checkout. The default is master.
The package.json File
You need to have a package.json file in the root of your project to do
much of anything with npm. That is basically the whole interface.
-
See package.json(5) for details about what goes in that file. At the very
+
See package.json(5) for details about what goes in that file. At the very
least, you need:
name:
@@ -70,9 +70,9 @@ Take some credit.
scripts:
If you have a special compilation or installation script, then you
-should put it in the scripts hash. You should definitely have at
+should put it in the scripts object. You should definitely have at
least a basic smoke-test command as the "scripts.test" field.
-See npm-scripts(7).
main:
If you have a single module that serves as the entry point to your
@@ -80,13 +80,13 @@ program (like what the "foo" package gives you at require("foo&qu
then you need to specify that in the "main" field.
directories:
-This is a hash of folders. The best ones to include are "lib" and
-"doc", but if you specify a folder full of man pages in "man", then
+This is an object mapping names to folders. The best ones to include are
+"lib" and "doc", but if you use "man" to specify a folder full of man pages,
they'll get installed just like these ones.
You can use npm init in the root of your package in order to get you
-started with a pretty basic package.json file. See npm-init(1) for
+started with a pretty basic package.json file. See npm-init(1) for
more info.
Keeping files out of your package
Use a .npmignore file to keep stuff out of your package. If there's
@@ -115,14 +115,14 @@ bother adding node_modules to .npmignore.
npm link is designed to install a development package and see the
changes in real time without having to keep re-installing it. (You do
need to either re-link or npm rebuild -g to update compiled packages,
of course.)
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.
@@ -51,12 +51,12 @@ Joe's appropriate course of action in each case is the same.
owner (Bob).
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 support@npmjs.com to the CC list of
+adds the npm support staff support@npmjs.com 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.
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 support
-support@npmjs.com and we'll sort it out. ("Reasonable" is
+support@npmjs.com and we'll sort it out. ("Reasonable" is
usually at least 4 weeks, but extra time is allowed around common
holidays.)
@@ -97,8 +97,8 @@ things into it.
If you see bad behavior like this, please report it right away.
Use the npm root command to see where modules go, and the npm bin
@@ -48,7 +48,7 @@ not going to happen, because it's a terrible idea that causes more
problems than it solves.
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(5) for
+proven to be an extremely successful approach. See npm-folders(5) for
more details.
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.
@@ -100,7 +100,7 @@ lower-case, though it starts most sentences it is a part of.
npm search
Arguments are greps. npm search jsdom shows jsdom packages.
How do I update npm?
-
npm update npm -g
+
npm install npm -g
You can also update all outdated local packages by doing npm update without
any arguments, or global packages by doing npm update -g.
Occasionally, the version of npm will progress such that the current
@@ -217,18 +217,18 @@ of Node 0.3.
You'll most likely want to npm link your development folder. That's
awesomely handy.
-
To set up your own private registry, check out npm-registry(7).
+
To set up your own private registry, check out npm-registry(7).
Can I list a url as a dependency?
Yes. It should be a url to a gzipped tarball containing a single folder
that has a package.json in its root, or a git url.
(See "what is a package?" above.)
How do I symlink to a dev folder so I don't have to keep re-installing?
@@ -236,7 +236,7 @@ that has a package.json in its root, or a git url.
To check if the registry is down, open up
https://registry.npmjs.org/ 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 us know by emailing support@npmjs.com
+
If the registry IS down, let us know by emailing support@npmjs.com
or posting an issue at https://github.com/npm/npm/issues. If it's
down for the world (and not just on your local network) then we're
probably already being pinged about it.
diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html
index 530e350..d746316 100644
--- a/deps/npm/html/doc/misc/npm-registry.html
+++ b/deps/npm/html/doc/misc/npm-registry.html
@@ -22,9 +22,9 @@ is powered by a CouchDB database, of which there is a public mirror at
http://skimdb.npmjs.com/registry. The code for the couchapp is
available at http://github.com/npm/npm-registry-couchapp.
The registry URL used is determined by the scope of the package (see
-npm-scope(7)). If no scope is specified, the default registry is used, which is
-supplied by the registry config parameter. See npm-config(1),
-npmrc(5), and npm-config(7) for more on managing npm's configuration.
+npm-scope(7)). If no scope is specified, the default registry is used, which is
+supplied by the registry config parameter. See npm-config(1),
+npmrc(5), and npm-config(7) for more on managing npm's configuration.
Can I run my own private registry?
Yes!
The easiest way is to replicate the couch database, and use the same (or
@@ -40,7 +40,7 @@ package for the whole world to see, you can simply override the
published at all, or
"publishConfig":{"registry":"http://my-internal-registry.local"}
to force it to be published only to your internal registry.
-
See package.json(5) for more info on what goes in the package.json file.
+
See package.json(5) for more info on what goes in the package.json file.
Will you replicate from my registry into the public one?
No. If you want things to be public, then publish them into the public
registry using npm. What little security there is would be for nought
@@ -52,11 +52,11 @@ effectively implement the entire CouchDB API anyway.
@@ -70,5 +70,5 @@ effectively implement the entire CouchDB API anyway.
-
npm-registry — npm@2.0.0
+
npm-registry — npm@2.1.6
diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html
index 91ac0ae..9fed0bb 100644
--- a/deps/npm/html/doc/misc/npm-scope.html
+++ b/deps/npm/html/doc/misc/npm-scope.html
@@ -27,15 +27,15 @@ folder, e.g. if your other packages are installed in node_modules/packagen
scoped modules will be in node_modules/@myorg/packagename. The scope folder
(@myorg) is simply the name of the scope preceded by an @-symbol, and can
contain any number of scoped packages.
-
A scoped package is install by referencing it by name, preceded by an @-symbol,
-in npm install:
+
A scoped package is installed by referencing it by name, preceded by an
+@-symbol, in npm install:
npm install @myorg/mypackage
Or in package.json:
"dependencies": {
"@myorg/mypackage": "^1.3.0"
}
Note that if the @-symbol is omitted in either case npm will instead attempt to
-install from GitHub; see npm-install(1).
npm supports the "scripts" member of the package.json script, for the
+
npm supports the "scripts" property of the package.json script, for the
following scripts:
prepublish:
@@ -41,9 +41,10 @@ Run by the npm start command.
Run by the npm restart command. Note: npm restart will run the
stop and start scripts if no restart script is provided.
-
Additionally, arbitrary scripts can be executed by running `npm run-script
-
. *Pre* and *post* commands with matching names will be run for
-those as well (e.g.premyscript,myscript,postmyscript`).
+
Additionally, arbitrary scripts can be executed by running npm
+run-script <pkg> <stage>. Pre and post commands with matching
+names will be run for those as well (e.g. premyscript, myscript,
+postmyscript).
NOTE: INSTALL SCRIPTS ARE AN ANTIPATTERN
tl;dr Don't use install. Use a .gyp file for compilation, and
prepublish for anything else.
@@ -123,7 +124,7 @@ package.json file, then your package scripts would have the
Configuration parameters are put in the environment with the
npm_config_ prefix. For instance, you can view the effective root
config by checking the npm_config_root environment variable.
-
Special: package.json "config" hash
+
Special: package.json "config" object
The package.json "config" keys are overwritten in the environment if
there is a config param of <name>[@<version>]:<key>. For example,
if the package.json has this:
@@ -189,7 +190,7 @@ fail, and potentially be rolled back. If the failure is minor or
only will prevent some optional features, then it's better to just
print a warning and exit successfully.
Try not to use scripts to do what npm can do for you. Read through
-package.json(5) to see all the things that you can specify and enable
+package.json(5) to see all the things that you can specify and enable
by simply describing your package appropriately. In general, this
will lead to a more robust and consistent state.
Inspect the env to determine where to put things. For instance, if
@@ -202,10 +203,10 @@ the user will sudo the npm command in question.
You can set any npm configuration params with that script:
+
npm_config_prefix=/some/path sh install.sh
+
Or, you can run it in uber-debuggery mode:
+
npm_debug=1 sh install.sh
+
Even Fancier
+
Get the code with git. Use make to build the docs and do other stuff.
+If you plan on hacking on npm, make link is your friend.
+
If you've got the npm source code, you can also semi-permanently set
+arbitrary config keys using the ./configure --key=val ..., and then
+run npm commands by doing node cli.js <cmd> <args>. (This is helpful
+for testing, or running stuff without actually installing npm itself.)
+
Fancy Windows Install
+
You can download a zip file from https://npmjs.org/dist/, and unpack it
+in the same folder where node.exe lives.
+
If that's not fancy enough for you, then you can fetch the code with
+git, and mess with it directly.
+
Installing on Cygwin
+
No.
+
Permissions when Using npm to Install Other Stuff
+
tl;dr
+
+
Use sudo for greater safety. Or don't, if you prefer not to.
+
npm will downgrade permissions if it's root before running any build
+scripts that package authors specified.
+
+
More details...
+
As of version 0.3, it is recommended to run npm as root.
+This allows npm to change the user identifier to the nobody user prior
+to running any package build or test commands.
+
If you are not the root user, or if you are on a platform that does not
+support uid switching, then npm will not attempt to change the userid.
+
If you would like to ensure that npm always runs scripts as the
+"nobody" user, and have it fail if it cannot downgrade permissions, then
+set the following configuration param:
+
npm config set unsafe-perm false
+
This will prevent running in unsafe mode, even as non-root users.
+
Uninstalling
+
So sad to see you go.
+
sudo npm uninstall npm -g
+
Or, if that fails,
+
sudo make uninstall
+
More Severe Uninstalling
+
Usually, the above instructions are sufficient. That will remove
+npm, but leave behind anything you've installed.
+
If you would like to remove all the packages that you have installed,
+then you can use the npm ls command to find them, and then npm rm to
+remove them.
+
To remove cruft left behind by npm 0.x, you can use the included
+clean-old.sh script file. You can run it conveniently like this:
+
npm explore npm -g -- sh scripts/clean-old.sh
+
npm uses two configuration files, one for per-user configs, and another
+for global (every-user) configs. You can view them by doing:
+
npm config get userconfig # defaults to ~/.npmrc
+npm config get globalconfig # defaults to /usr/local/etc/npmrc
+
Uninstalling npm does not remove configuration files by default. You
+must remove them yourself manually if you want them gone. Note that
+this means that future npm installs will not remember the settings that
+you have chosen.
+
Using npm Programmatically
+
If you would like to use npm programmatically, you can do that.
+It's not very well documented, but it is rather simple.
+
Most of the time, unless you actually want to do all the things that
+npm does, you should try using one of npm's dependencies rather than
+using npm itself, if possible.
+
Eventually, npm will be just a thin cli wrapper around the modules
+that it depends on, but for now, there are some things that you must
+use npm itself to do.
+
var npm = require("npm")
+npm.load(myConfigObject, function (er) {
+ if (er) return handlError(er)
+ npm.commands.install(["some", "args"], function (er, data) {
+ if (er) return commandFailed(er)
+ // command succeeded, and data might have some info
+ })
+ npm.registry.log.on("log", function (message) { .... })
+})
+
The load function takes an object hash of the command-line configs.
+The various npm.commands.<cmd> functions take an array of
+positional argument strings. The last argument to any
+npm.commands.<cmd> function is a callback. Some commands take other
+optional arguments. Read the source.
+
You cannot set configs individually for any single npm function at this
+time. Since npm is a singleton, any call to npm.config.set will
+change the value for all npm commands in that process.
+
See ./bin/npm-cli.js for an example of pulling config values off of the
+command line arguments using nopt. You may also want to check out npm
+help config to learn about all the options you can set there.
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
+
Legal Stuff
+
"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.
+
Modules published on the npm registry are not officially endorsed by
+npm, Inc. or the Node.js project.
+
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.
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.
+
If other people publish something, it's theirs.
+
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 you publish Bad Stuff, we may delete it from the registry, or even
+ban your account in extreme cases. So don't do that.
This command tries to guess at the likely location of a package's
+bug tracker URL, and then tries to open it using the --browser
+config param.
+
Like other commands, the first parameter is an array. This command only
+uses the first element, which is expected to be a package name with an
+optional version number.
+
This command will launch a browser, so this command may not be the most
+friendly for programmatic use.
+
diff --git a/deps/npm/html/partial/doc/api/npm-cache.html b/deps/npm/html/partial/doc/api/npm-cache.html
new file mode 100644
index 0000000..b837a68
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-cache.html
@@ -0,0 +1,22 @@
+
This acts much the same ways as the npm-cache(1) command line
+functionality.
+
The callback is called with the package.json data of the thing that is
+eventually added to or read from the cache.
+
The top level npm.commands.cache(...) functionality is a public
+interface, and like all commands on the npm.commands object, it will
+match the command line behavior exactly.
+
However, the cache folder structure and the cache helper functions are
+considered internal API surface, and as such, may change in future
+releases of npm, potentially without warning or significant version
+incrementation.
+
Use at your own risk.
+
diff --git a/deps/npm/html/partial/doc/api/npm-commands.html b/deps/npm/html/partial/doc/api/npm-commands.html
new file mode 100644
index 0000000..eaf57af
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-commands.html
@@ -0,0 +1,16 @@
+
npm comes with a full set of commands, and each of the commands takes a
+similar set of arguments.
+
In general, all commands on the command object take an array of positional
+argument strings. The last argument to any function is a callback. Some
+commands are special and take other optional arguments.
+
All commands have their own man page. See man npm-<command> for command-line
+usage, or man 3 npm-<command> for programmatic usage.
npm.commands.config(args, callback)
+var val = npm.config.get(key)
+npm.config.set(key, val)
+
DESCRIPTION
+
This function acts much the same way as the command-line version. The first
+element in the array tells config what to do. Possible values are:
+
+
set
+
Sets a config parameter. The second element in args is interpreted as the
+ key, and the third element is interpreted as the value.
+
+
get
+
Gets the value of a config parameter. The second element in args is the
+ key to get the value of.
+
+
delete (rm or del)
+
Deletes a parameter from the config. The second element in args is the
+ key to delete.
+
+
list (ls)
+
Show all configs that aren't secret. No parameters necessary.
+
+
edit:
+
Opens the config file in the default editor. This command isn't very useful
+ programmatically, but it is made available.
+
+
+
To programmatically access npm configuration settings, or set them for
+the duration of a program, use the npm.config.set and npm.config.get
+functions instead.
This command tries to guess at the likely location of a package's
+documentation URL, and then tries to open it using the --browser
+config param.
+
Like other commands, the first parameter is an array. This command only
+uses the first element, which is expected to be a package name with an
+optional version number.
+
This command will launch a browser, so this command may not be the most
+friendly for programmatic use.
+
diff --git a/deps/npm/html/partial/doc/api/npm-edit.html b/deps/npm/html/partial/doc/api/npm-edit.html
new file mode 100644
index 0000000..ef49f94
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-edit.html
@@ -0,0 +1,16 @@
+
Opens the package folder in the default editor (or whatever you've
+configured as the npm editor config -- see npm help config.)
+
After it has been edited, the package is rebuilt so as to pick up any
+changes in compiled packages.
+
For instance, you can do npm install connect to install connect
+into your package, and then npm.commands.edit(["connect"], callback)
+to make a few changes to your locally installed copy.
+
The first parameter is a string array with a single element, the package
+to open. The package can optionally have a version number attached.
+
Since this command opens an editor in a new process, be careful about where
+and how this is used.
+
diff --git a/deps/npm/html/partial/doc/api/npm-explore.html b/deps/npm/html/partial/doc/api/npm-explore.html
new file mode 100644
index 0000000..60f3ac1
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-explore.html
@@ -0,0 +1,11 @@
+
Spawn a subshell in the directory of the installed package specified.
+
If a command is specified, then it is run in the subshell, which then
+immediately terminates.
+
Note that the package is not automatically rebuilt afterwards, so be
+sure to use npm rebuild <pkg> if you make any changes.
+
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.
+
diff --git a/deps/npm/html/partial/doc/api/npm-help-search.html b/deps/npm/html/partial/doc/api/npm-help-search.html
new file mode 100644
index 0000000..7818b6b
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-help-search.html
@@ -0,0 +1,24 @@
+
This command is rarely useful, but it exists in the rare case that it is.
+
This command takes an array of search terms and returns the help pages that
+match in order of best match.
+
If there is only one match, then npm displays that help section. If there
+are multiple results, the results are printed to the screen formatted and the
+array of results is returned. Each result is an object with these properties:
+
+
hits:
+A map of args to number of hits on that arg. For example, {"npm": 3}
+
found:
+Total number of unique args that matched.
+
totalHits:
+Total number of hits.
+
lines:
+An array of all matching lines (and some adjacent lines).
+
file:
+Name of the file that matched
+
+
The silent parameter is not necessary not used, but it may in the future.
+
diff --git a/deps/npm/html/partial/doc/api/npm-init.html b/deps/npm/html/partial/doc/api/npm-init.html
new file mode 100644
index 0000000..723fbde
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-init.html
@@ -0,0 +1,19 @@
+
This will ask you a bunch of questions, and then write a package.json for you.
+
It attempts to make reasonable guesses about what you want things to be set to,
+and then writes a package.json file with the options you've selected.
+
If you already have a package.json file, it'll read that first, and default to
+the options in there.
+
It is strictly additive, so it does not delete options from your package.json
+without a really good reason to do so.
+
Since this function expects to be run on the command-line, it doesn't work very
+well as a programmatically. The best option is to roll your own, and since
+JavaScript makes it stupid simple to output formatted JSON, that is the
+preferred method. If you're sure you want to handle command-line prompting,
+then go ahead and use this programmatically.
npm.load() must be called before any other function call. Both parameters are
+optional, but the second is recommended.
+
The first parameter is an object containing command-line config params, and the
+second parameter is a callback that will be called when npm is loaded and ready
+to serve.
+
The first parameter should follow a similar structure as the package.json
+config object.
+
For example, to emulate the --dev flag, pass an object that looks like this:
+
{
+ "dev": true
+}
+
For a list of all the available command-line configs, see npm help config
+
diff --git a/deps/npm/html/partial/doc/api/npm-ls.html b/deps/npm/html/partial/doc/api/npm-ls.html
new file mode 100644
index 0000000..508003c
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-ls.html
@@ -0,0 +1,43 @@
+
This command will print to stdout all the versions of packages that are
+installed, as well as their dependencies, in a tree-structure. It will also
+return that data using the callback.
+
This command does not take any arguments, but args must be defined.
+Beyond that, if any arguments are passed in, npm will politely warn that it
+does not take positional arguments, though you may set config flags
+like with any other command, such as global to list global packages.
+
It will print out extraneous, missing, and invalid packages.
+
If the silent parameter is set to true, nothing will be output to the screen,
+but the data will still be returned.
+
Callback is provided an error if one occurred, the full data about which
+packages are installed and which dependencies they will receive, and a
+"lite" data object which just shows which versions are installed where.
+Note that the full data object is a circular structure, so care must be
+taken if it is serialized to JSON.
+
CONFIGURATION
+
long
+
+
Default: false
+
Type: Boolean
+
+
Show extended information.
+
parseable
+
+
Default: false
+
Type: Boolean
+
+
Show parseable output instead of tree view.
+
global
+
+
Default: false
+
Type: Boolean
+
+
List packages in the global install prefix instead of in the current
+project.
+
Note, if parseable is set or long isn't set, then duplicates will be trimmed.
+This means that if a submodule a same dependency as a parent module, then the
+dependency will only be output once.
+
diff --git a/deps/npm/html/partial/doc/api/npm-outdated.html b/deps/npm/html/partial/doc/api/npm-outdated.html
new file mode 100644
index 0000000..16d3150
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-outdated.html
@@ -0,0 +1,8 @@
+
The first element of the 'args' parameter defines what to do, and the subsequent
+elements depend on the action. Possible values for the action are (order of
+parameters are given in parenthesis):
+
+
ls (package):
+List all the users who have access to modify a package and push new versions.
+Handy when you need to know who to bug for help.
+
add (user, package):
+Add a new user as a maintainer of a package. This user is enabled to modify
+metadata, publish new versions, and add other owners.
+
rm (user, package):
+Remove a user from the package owner list. This immediately revokes their
+privileges.
+
+
Note that there is only one level of access. Either you can modify a package,
+or you can't. Future versions may contain more fine-grained access levels, but
+that is not implemented at this time.
For anything that's installable (that is, a package folder, tarball,
+tarball url, name@tag, name@version, or name), this command will fetch
+it to the cache, and then copy the tarball to the current working
+directory as <name>-<version>.tgz, and then write the filenames out to
+stdout.
+
If the same package is specified multiple times, then the file will be
+overwritten the second time.
+
If no arguments are supplied, then npm packs the current package folder.
+
diff --git a/deps/npm/html/partial/doc/api/npm-prefix.html b/deps/npm/html/partial/doc/api/npm-prefix.html
new file mode 100644
index 0000000..e9904b1
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-prefix.html
@@ -0,0 +1,9 @@
+
This command runs the npm build command on each of the matched packages. This is useful
+when you install a new version of node, and must recompile all your C++ addons with
+the new binary. If no 'packages' parameter is specify, every package will be rebuilt.
+
CONFIGURATION
+
See npm help build
+
diff --git a/deps/npm/html/partial/doc/api/npm-repo.html b/deps/npm/html/partial/doc/api/npm-repo.html
new file mode 100644
index 0000000..9a18976
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-repo.html
@@ -0,0 +1,13 @@
+
This command tries to guess at the likely location of a package's
+repository URL, and then tries to open it using the --browser
+config param.
+
Like other commands, the first parameter is an array. This command only
+uses the first element, which is expected to be a package name with an
+optional version number.
+
This command will launch a browser, so this command may not be the most
+friendly for programmatic use.
+
diff --git a/deps/npm/html/partial/doc/api/npm-restart.html b/deps/npm/html/partial/doc/api/npm-restart.html
new file mode 100644
index 0000000..35db404
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-restart.html
@@ -0,0 +1,16 @@
+
This runs a package's "restart" script, if one was provided.
+Otherwise it runs package's "stop" script, if one was provided, and then
+the "start" script.
+
If no version is specified, then it restarts the "active" version.
+
npm can run tests on multiple packages. Just specify multiple packages
+in the packages parameter.
This runs an arbitrary command from a package's "scripts" object.
+
It is used by the test, start, restart, and stop commands, but can be
+called directly, as well.
+
The 'args' parameter is an array of strings. Behavior depends on the number
+of elements. If there is only one element, npm assumes that the element
+represents a command to be run on the local repository. If there is more than
+one element, then the first is assumed to be the package and the second is
+assumed to be the command to run. All other elements are ignored.
Search the registry for packages matching the search terms. The available parameters are:
+
+
searchTerms:
+Array of search terms. These terms are case-insensitive.
+
silent:
+If true, npm will not log anything to the console.
+
staleness:
+This is the threshold for stale packages. "Fresh" packages are not refreshed
+from the registry. This value is measured in seconds.
+
callback:
+Returns an object where each key is the name of a package, and the value
+is information about that package along with a 'words' property, which is
+a space-delimited string of all of the interesting words in that package.
+The only properties included are those that are searched, which generally include:
+
+
name
+
description
+
maintainers
+
url
+
keywords
+
+
+
+
A search on the registry excludes any result that does not match all of the
+search terms. It also removes any items from the results that contain an
+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).
+
diff --git a/deps/npm/html/partial/doc/api/npm-shrinkwrap.html b/deps/npm/html/partial/doc/api/npm-shrinkwrap.html
new file mode 100644
index 0000000..b5f3359
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-shrinkwrap.html
@@ -0,0 +1,13 @@
+
This acts much the same ways as shrinkwrapping on the command-line.
+
This command does not take any arguments, but 'args' must be defined.
+Beyond that, if any arguments are passed in, npm will politely warn that it
+does not take positional arguments.
+
If the 'silent' parameter is set to true, nothing will be output to the screen,
+but the shrinkwrap file will still be written.
+
Finally, 'callback' is a function that will be called when the shrinkwrap has
+been saved.
+
diff --git a/deps/npm/html/partial/doc/api/npm-start.html b/deps/npm/html/partial/doc/api/npm-start.html
new file mode 100644
index 0000000..2eae8ba
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-start.html
@@ -0,0 +1,8 @@
+
For each package specified, npm will check if it has a git repository url
+in its package.json description then add it as a git submodule at
+node_modules/<pkg name>.
+
This is a convenience only. From then on, it's up to you to manage
+updates by using the appropriate git commands. npm will stubbornly
+refuse to update, modify, or remove anything with a .git subfolder
+in it.
+
This command also does not install missing dependencies, if the package
+does not include them in its git repository. If npm ls reports that
+things are missing, you can either install, link, or submodule them yourself,
+or you can do npm explore <pkgname> -- npm install to install the
+dependencies into the submodule folder.
+
SEE ALSO
+
+
npm help json
+
git help submodule
+
+
diff --git a/deps/npm/html/partial/doc/api/npm-tag.html b/deps/npm/html/partial/doc/api/npm-tag.html
new file mode 100644
index 0000000..f288fc1
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-tag.html
@@ -0,0 +1,16 @@
+
Tags the specified version of the package with the specified tag, or the
+--tag config if not specified.
+
The 'package@version' is an array of strings, but only the first two elements are
+currently used.
+
The first element must be in the form package@version, where package
+is the package name and version is the version number (much like installing a
+specific version).
+
The second element is the name of the tag to tag this version with. If this
+parameter is missing or falsey (empty), the default froom the config will be
+used. For more information about how to set this config, check
+man 3 npm-config for programmatic usage or man npm-config for cli usage.
+
diff --git a/deps/npm/html/partial/doc/api/npm-test.html b/deps/npm/html/partial/doc/api/npm-test.html
new file mode 100644
index 0000000..9c35bdc
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-test.html
@@ -0,0 +1,10 @@
+
This removes a package version from the registry, deleting its
+entry and removing the tarball.
+
The package parameter must be defined.
+
Only the first element in the package parameter is used. If there is no first
+element, then npm assumes that the package at the current working directory
+is what is meant.
+
If no version is specified, or if all versions are removed then
+the root package entry is removed from the registry entirely.
+
diff --git a/deps/npm/html/partial/doc/api/npm-update.html b/deps/npm/html/partial/doc/api/npm-update.html
new file mode 100644
index 0000000..d057711
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-update.html
@@ -0,0 +1,7 @@
+
Run this in a package directory to bump the version and write the new
+data back to the package.json file.
+
If run in a git repo, it will also create a version commit and tag, and
+fail if the repo is not clean.
+
Like all other commands, this function takes a string array as its first
+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.
+
diff --git a/deps/npm/html/partial/doc/api/npm-view.html b/deps/npm/html/partial/doc/api/npm-view.html
new file mode 100644
index 0000000..4f5acf6
--- /dev/null
+++ b/deps/npm/html/partial/doc/api/npm-view.html
@@ -0,0 +1,61 @@
+
This command shows data about a package and prints it to the stream
+referenced by the outfd config, which defaults to stdout.
+
The "args" parameter is an ordered list that closely resembles the command-line
+usage. The elements should be ordered such that the first element is
+the package and version (package@version). The version is optional. After that,
+the rest of the parameters are fields with optional subfields ("field.subfield")
+which can be used to get only the information desired from the registry.
+
The callback will be passed all of the data returned by the query.
+
For example, to get the package registry entry for the connect package,
+you can do this:
+
npm.commands.view(["connect"], callback)
+
If no version is specified, "latest" is assumed.
+
Field names can be specified after the package descriptor.
+For example, to show the dependencies of the ronn package at version
+0.3.5, you could do the following:
For fields that are arrays, requesting a non-numeric field will return
+all of the values from the objects in the list. For example, to get all
+the contributor names for the "express" project, you can do this:
You may also use numeric indices in square braces to specifically select
+an item in an array field. To just get the email address of the first
+contributor in the list, you can do this:
Multiple fields may be specified, and will be printed one after another.
+For exampls, to get all the contributor names and email addresses, you
+can do this:
"Person" fields are shown as a string if they would be shown as an
+object. So, for example, this will show the list of npm contributors in
+the shortened string format. (See npm help json for more on this.)
If a version range is provided, then data will be printed for every
+matching version of the package. This will show which version of jsdom
+was required by each matching version of yui3:
If only a single string field for a single version is output, then it
+will not be colorized or quoted, so as to enable piping the output to
+another command.
+
If the version range matches multiple versions, than each printed value
+will be prefixed with the version it applies to.
+
If multiple fields are requested, than each of them are prefixed with
+the field name.
+
Console output can be disabled by setting the 'silent' parameter to true.
+
RETURN VALUE
+
The data returned will be an object in this formation:
var npm = require("npm")
+npm.load([configObject, ]function (er, npm) {
+ // use the npm object, now that it's loaded.
+
+ npm.config.set(key, val)
+ val = npm.config.get(key)
+
+ console.log("prefix = %s", npm.prefix)
+
+ npm.commands.install(["package"], cb)
+})
+
VERSION
+
2.1.6
+
DESCRIPTION
+
This is the API documentation for npm.
+To find documentation of the command line
+client, see npm(1).
+
Prior to using npm's commands, npm.load() must be called. If you provide
+configObject as an object map of top-level configs, they override the values
+stored in the various config locations. In the npm command line client, this
+set of configs is parsed from the command line options. Additional
+configuration params are loaded from two configuration files. See
+npm-config(1), npm-config(7), and npmrc(5) for more information.
+
After that, each of the functions are accessible in the
+commands object: npm.commands.<cmd>. See npm-index(7) for a list of
+all possible commands.
+
All commands on the command object take an array of positional argument
+strings. The last argument to any function is a callback. Some
+commands take other optional arguments.
+
Configs cannot currently be set on a per function basis, as each call to
+npm.config.set will change the value for all npm commands in that process.
+
To find API documentation for a specific command, run the npm apihelp
+command.
+
METHODS AND PROPERTIES
+
+
npm.load(configs, cb)
+
Load the configuration params, and call the cb function once the
+ globalconfig and userconfig files have been loaded as well, or on
+ nextTick if they've already been loaded.
+
+
npm.config
+
An object for accessing npm configuration parameters.
+
+
npm.config.get(key)
+
npm.config.set(key, val)
+
npm.config.del(key)
+
+
+
npm.dir or npm.root
+
The node_modules directory where npm will operate.
+
+
npm.prefix
+
The prefix where npm is operating. (Most often the current working
+ directory.)
+
+
npm.cache
+
The place where npm keeps JSON and tarballs it fetches from the
+ registry (or uploads to the registry).
+
+
npm.tmp
+
npm's temporary working directory.
+
+
npm.deref
+
Get the "real" name for a command that has either an alias or
+ abbreviation.
+
+
+
MAGIC
+
For each of the methods in the npm.commands object, a method is added to the
+npm object, which takes a set of positional string arguments rather than an
+array and a callback.
+
If the last argument is a callback, then it will use the supplied
+callback. However, if no callback is provided, then it will print out
+the error or results.
Note that that won't work in a node program, since the install
+method will get called before the configuration load is completed.
+
ABBREVS
+
In order to support npm ins foo instead of npm install foo, the
+npm.commands object has a set of abbreviations as well as the full
+method names. Use the npm.deref method to find the real name.
+
For example:
+
var cmd = npm.deref("unp") // cmd === "unpublish"
+
diff --git a/deps/npm/html/partial/doc/cli/npm-adduser.html b/deps/npm/html/partial/doc/cli/npm-adduser.html
new file mode 100644
index 0000000..ac9fa00
--- /dev/null
+++ b/deps/npm/html/partial/doc/cli/npm-adduser.html
@@ -0,0 +1,47 @@
+
Create or verify a user named <username> in the specified registry, and
+save the credentials to the .npmrc file. If no registry is specified,
+the default registry will be used (see npm-config(7)).
+
The username, password, and email are read in from prompts.
+
You may use this command to change your email address, but not username
+or password.
The base URL of the npm package registry. If scope is also specified,
+this registry will only be used for packages with that scope. See npm-scope(7).
+
scope
+
Default: none
+
If specified, the user and login credentials given will be associated
+with the specified scope. See npm-scope(7). You can use both at the same time,
+e.g.
This will set a registry for the given scope and login or create a user for
+that registry at the same time.
+
always-auth
+
Default: false
+
If specified, save configuration indicating that all requests to the given
+registry should include authorization information. Useful for private
+registries. Can be used with --registry and / or --scope, e.g.
This will ensure that all requests to that registry (including for tarballs)
+include an authorization header. See always-auth in npm-config(7) for more
+details on always-auth. Registry-specific configuaration of always-auth takes
+precedence over any global configuration.
npm bugs <pkgname>
+npm bugs (with no args in a package dir)
+
DESCRIPTION
+
This command tries to guess at the likely location of a package's
+bug tracker URL, and then tries to open it using the --browser
+config param. If no package name is provided, it will search for
+a package.json in the current folder and use the name property.
+
CONFIGURATION
+
browser
+
+
Default: OS X: "open", Windows: "start", Others: "xdg-open"
+
Type: String
+
+
The browser that is called by the npm bugs command to open websites.
The npm bundle command has been removed in 1.0, for the simple reason
+that it is no longer necessary, as the default behavior is now to
+install packages into the local space.
+
Just use npm install now to do what npm bundle used to do.
add:
+Add the specified package to the local cache. This command is primarily
+intended to be used internally by npm, but it can provide a way to
+add data to the local installation cache explicitly.
+
+
ls:
+Show the data in the cache. Argument is a path to show in the cache
+folder. Works a bit like the find program, but limited by the
+depth config.
+
+
clean:
+Delete data out of the cache folder. If an argument is provided, then
+it specifies a subpath to delete. If no argument is provided, then
+the entire cache is cleared.
+
+
+
DETAILS
+
npm stores cache data in the directory specified in npm config get cache.
+For each package that is added to the cache, three pieces of information are
+stored in {cache}/{name}/{version}:
+
+
.../package/package.json:
+The package.json file, as npm sees it.
+
.../package.tgz:
+The tarball for that version.
+
+
Additionally, whenever a registry request is made, a .cache.json file
+is placed at the corresponding URI, to store the ETag and the requested
+data. This is stored in {cache}/{hostname}/{path}/.cache.json.
+
Commands that make non-essential registry requests (such as search and
+view, or the completion scripts) generally specify a minimum timeout.
+If the .cache.json file is younger than the specified timeout, then
+they do not make an HTTP request to the registry.
+
CONFIGURATION
+
cache
+
Default: ~/.npm on Posix, or %AppData%/npm-cache on Windows.
The synopsis above
+loads the completions into your current shell. Adding it to
+your ~/.bashrc or ~/.zshrc will make the completions available
+everywhere.
+
You may of course also pipe the output of npm completion to a file
+such as /usr/local/etc/bash_completion.d/npm if you have a system
+that will read that file for you.
+
When COMP_CWORD, COMP_LINE, and COMP_POINT are defined in the
+environment, npm completion acts in "plumbing mode", and outputs
+completions based on the arguments.
Searches the local package tree and attempts to simplify the overall
+structure by moving dependencies further up the tree, where they can
+be more effectively shared by multiple dependent packages.
+
For example, consider this dependency graph:
+
a
++-- b <-- depends on c@1.0.x
+| `-- c@1.0.3
+`-- d <-- depends on c@~1.0.9
+ `-- c@1.0.10
+
In this case, npm-dedupe(1) will transform the tree to:
+
a
++-- b
++-- d
+`-- c@1.0.10
+
Because of the hierarchical nature of node's module lookup, b and d
+will both get their dependency met by the single c package at the root
+level of the tree.
+
If a suitable version exists at the target location in the tree
+already, then it will be left untouched, but the other duplicates will
+be deleted.
+
If no suitable version can be found, then a warning is printed, and
+nothing is done.
+
If any arguments are supplied, then they are filters, and only the
+named packages will be touched.
+
Note that this operation transforms the dependency tree, and may
+result in packages getting updated versions, perhaps from the npm
+registry.
+
This feature is experimental, and may change in future versions.
+
The --tag argument will apply to all of the affected dependencies. If a
+tag with the given name exists, the tagged version is preferred over newer
+versions.
npm docs [<pkgname> [<pkgname> ...]]
+npm docs (with no args in a package dir)
+npm home [<pkgname> [<pkgname> ...]]
+npm home (with no args in a package dir)
+
DESCRIPTION
+
This command tries to guess at the likely location of a package's
+documentation URL, and then tries to open it using the --browser
+config param. You can pass multiple package names at once. If no
+package name is provided, it will search for a package.json in
+the current folder and use the name property.
+
CONFIGURATION
+
browser
+
+
Default: OS X: "open", Windows: "start", Others: "xdg-open"
+
Type: String
+
+
The browser that is called by the npm docs command to open websites.
Opens the package folder in the default editor (or whatever you've
+configured as the npm editor config -- see npm-config(7).)
+
After it has been edited, the package is rebuilt so as to pick up any
+changes in compiled packages.
+
For instance, you can do npm install connect to install connect
+into your package, and then npm edit connect to make a few
+changes to your locally installed copy.
+
CONFIGURATION
+
editor
+
+
Default: EDITOR environment variable if set, or "vi" on Posix,
+or "notepad" on Windows.
+
Type: path
+
+
The command to run for npm edit or npm config edit.
If supplied a topic, then show the appropriate documentation page.
+
If the topic does not exist, or if multiple terms are provided, then run
+the help-search command to find a match. Note that, if help-search
+finds a single subject, then it will run help on that topic, so unique
+matches are equivalent to specifying a topic name.
+
CONFIGURATION
+
viewer
+
+
Default: "man" on Posix, "browser" on Windows
+
Type: path
+
+
The program to use to view help content.
+
Set to "browser" to view html help content in the default web browser.
npm install (with no args in a package dir)
+npm install <tarball file>
+npm install <tarball url>
+npm install <folder>
+npm install [@<scope>/]<name> [--save|--save-dev|--save-optional] [--save-exact]
+npm install [@<scope>/]<name>@<tag>
+npm install [@<scope>/]<name>@<version>
+npm install [@<scope>/]<name>@<version range>
+npm i (with any of the previous argument usage)
+
DESCRIPTION
+
This command installs a package, and any packages that it depends on. If the
+package has a shrinkwrap file, the installation of dependencies will be driven
+by that. See npm-shrinkwrap(1).
+
A package is:
+
+
a) a folder containing a program described by a package.json file
+
b) a gzipped tarball containing (a)
+
c) a url that resolves to (b)
+
d) a <name>@<version> that is published on the registry (see npm-registry(7)) with (c)
+
e) a <name>@<tag> that points to (d)
+
f) a <name> that has a "latest" tag satisfying (e)
+
g) a <git remote url> that resolves to (b)
+
+
Even if you never publish your package, you can still get a lot of
+benefits of using npm if you just want to write a node program (a), and
+perhaps if you also want to be able to easily install it elsewhere
+after packing it up into a tarball (b).
+
+
npm install (in package directory, no arguments):
+
Install the dependencies in the local node_modules folder.
+
In global mode (ie, with -g or --global appended to the command),
+ it installs the current package context (ie, the current working
+ directory) as a global package.
+
By default, npm install will install all modules listed as
+ dependencies. With the --production flag,
+ npm will not install modules listed in devDependencies.
+
+
npm install <folder>:
+
Install a package that is sitting in a folder on the filesystem.
+
+
npm install <tarball file>:
+
Install a package that is sitting on the filesystem. Note: if you just want
+ to link a dev directory into your npm root, you can do this more easily by
+ using npm link.
+
Example:
+
npm install ./package.tgz
+
+
npm install <tarball url>:
+
Fetch the tarball url, and then install it. In order to distinguish between
+ this and other options, the argument must start with "http://" or "https://"
Do a <name>@<tag> install, where <tag> is the "tag" config. (See
+ npm-config(7).)
+
In most cases, this will install the latest version
+ of the module published on npm.
+
Example:
+
npm install sax
+
npm install takes 3 exclusive, optional flags which save or update
+ the package version in your main package.json:
+
+
--save: Package will appear in your dependencies.
+
+
--save-dev: Package will appear in your devDependencies.
+
+
--save-optional: Package will appear in your optionalDependencies.
+
When using any of the above options to save dependencies to your
+package.json, there is an additional, optional flag:
+
+
--save-exact: Saved dependencies will be configured with an
+exact version rather than using npm's default semver range
+operator.
+
<scope> is optional. The package will be downloaded from the registry
+associated with the specified scope. If no registry is associated with
+the given scope the default registry is assumed. See npm-scope(7).
+
Note: if you do not include the @-symbol on your scope name, npm will
+interpret this as a GitHub repository instead, see below. Scopes names
+must also be followed by a slash.
**Note**: If there is a file or folder named `<name>` in the current
+working directory, then it will try to install that, and only try to
+fetch the package by name if it is not valid.
+
+
npm install [@<scope>/]<name>@<tag>:
+
Install the version of the package that is referenced by the specified tag.
+ If the tag does not exist in the registry data for that package, then this
+ will fail.
Install a version of the package matching the specified version range. This
+ will follow the same rules for resolving dependencies described in package.json(5).
+
Note that most version ranges must be put in quotes so that your shell will
+ treat it as a single argument.
The --tag argument will apply to all of the specified install targets. If a
+tag with the given name exists, the tagged version is preferred over newer
+versions.
+
The --force argument will force npm to fetch remote resources even if a
+local copy exists on disk.
+
npm install sax --force
+
The --global argument will cause npm to install the package globally
+rather than locally. See npm-folders(5).
+
The --link argument will cause npm to link global installs into the
+local space in some cases.
+
The --no-bin-links argument will prevent npm from creating symlinks for
+any binaries the package might contain.
+
The --no-optional argument will prevent optional dependencies from
+being installed.
+
The --no-shrinkwrap argument, which will ignore an available
+shrinkwrap file and use the package.json instead.
+
The --nodedir=/path/to/node/source argument will allow npm to find the
+node source code so that npm can compile native modules.
+
See npm-config(7). Many of the configuration params have some
+effect on installation, since that's most of what npm does.
+
ALGORITHM
+
To install a package, npm uses the following algorithm:
+
install(where, what, family, ancestors)
+fetch what, unpack to <where>/node_modules/<what>
+for each dep in what.dependencies
+ resolve dep to precise version
+for each dep@version in what.dependencies
+ not in <where>/node_modules/<what>/node_modules/*
+ and not in <family>
+ add precise version deps to <family>
+ install(<where>/node_modules/<what>, dep, family)
+
For this package{dep} structure: A{B,C}, B{C}, C{D},
+this algorithm produces:
+
A
++-- B
+`-- C
+ `-- D
+
That is, the dependency from B to C is satisfied by the fact that A
+already caused C to be installed at a higher level.
+
See npm-folders(5) for a more detailed description of the specific
+folder structures that npm creates.
+
Limitations of npm's Install Algorithm
+
There are some very rare and pathological edge-cases where a cycle can
+cause npm to try to install a never-ending tree of packages. Here is
+the simplest case:
+
A -> B -> A' -> B' -> A -> B -> A' -> B' -> A -> ...
+
where A is some version of a package, and A' is a different version
+of the same package. Because B depends on a different version of A
+than the one that is already in the tree, it must install a separate
+copy. The same is true of A', which must install B'. Because B'
+depends on the original version of A, which has been overridden, the
+cycle falls into infinite regress.
+
To avoid this situation, npm flat-out refuses to install any
+name@version that is already present anywhere in the tree of package
+folder ancestors. A more correct, but more complex, solution would be
+to symlink the existing version into the new location. If this ever
+affects a real use-case, it will be investigated.
npm link (in package folder)
+npm link [@<scope>/]<pkgname>
+npm ln (with any of the previous argument usage)
+
DESCRIPTION
+
Package linking is a two-step process.
+
First, npm link in a package folder will create a globally-installed
+symbolic link from prefix/package-name to the current folder (see
+npm-config(7) for the value of prefix).
+
Next, in some other location, npm link package-name will create a
+symlink from the local node_modules folder to the global symlink.
+
Note that package-name is taken from package.json,
+not from directory name.
+
The package name can be optionally prefixed with a scope. See npm-scope(7).
+The scope must by preceded by an @-symbol and followed by a slash.
+
When creating tarballs for npm publish, the linked packages are
+"snapshotted" to their current state by resolving the symbolic links.
+
This is handy for installing your own stuff, so that you can work on it and
+test it iteratively without having to continually rebuild.
+
For example:
+
cd ~/projects/node-redis # go into the package directory
+npm link # creates global link
+cd ~/projects/node-bloggy # go into some other package directory.
+npm link redis # link-install the package
+
Now, any changes to ~/projects/node-redis will be reflected in
+~/projects/node-bloggy/node_modules/redis/
+
You may also shortcut the two steps in one. For example, to do the
+above use-case in a shorter way:
+
cd ~/projects/node-bloggy # go into the dir of your main project
+npm link ../node-redis # link the dir of your dependency
+
The second line is the equivalent of doing:
+
(cd ../node-redis; npm link)
+npm link redis
+
That is, it first creates a global link, and then links the global
+installation target into your project's node_modules folder.
+
If your linked package is scoped (see npm-scope(7)) your link command must
+include that scope, e.g.
npm list [[@<scope>/]<pkg> ...]
+npm ls [[@<scope>/]<pkg> ...]
+npm la [[@<scope>/]<pkg> ...]
+npm ll [[@<scope>/]<pkg> ...]
+
DESCRIPTION
+
This command will print to stdout all the versions of packages that are
+installed, as well as their dependencies, in a tree-structure.
+
Positional arguments are name@version-range identifiers, which will
+limit the results to only the paths to the packages named. Note that
+nested packages will also show the paths to the specified packages.
+For example, running npm ls promzard in npm's source tree will show:
It will print out extraneous, missing, and invalid packages.
+
If a project specifies git urls for dependencies these are shown
+in parentheses after the name@version to make it easier for users to
+recognize potential forks of a project.
+
When run as ll or la, it shows extended information by default.
+
CONFIGURATION
+
json
+
+
Default: false
+
Type: Boolean
+
+
Show information in JSON format.
+
long
+
+
Default: false
+
Type: Boolean
+
+
Show extended information.
+
parseable
+
+
Default: false
+
Type: Boolean
+
+
Show parseable output instead of tree view.
+
global
+
+
Default: false
+
Type: Boolean
+
+
List packages in the global install prefix instead of in the current
+project.
This command will check the registry to see if any (or, specific) installed
+packages are currently outdated.
+
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.
+
CONFIGURATION
+
json
+
+
Default: false
+
Type: Boolean
+
+
Show information in JSON format.
+
long
+
+
Default: false
+
Type: Boolean
+
+
Show extended information.
+
parseable
+
+
Default: false
+
Type: Boolean
+
+
Show parseable output instead of tree view.
+
global
+
+
Default: false
+
Type: Boolean
+
+
Check packages in the global install prefix instead of in the current
+project.
ls:
+List all the users who have access to modify a package and push new versions.
+Handy when you need to know who to bug for help.
+
add:
+Add a new user as a maintainer of a package. This user is enabled to modify
+metadata, publish new versions, and add other owners.
+
rm:
+Remove a user from the package owner list. This immediately revokes their
+privileges.
+
+
Note that there is only one level of access. Either you can modify a package,
+or you can't. Future versions may contain more fine-grained access levels, but
+that is not implemented at this time.
For anything that's installable (that is, a package folder, tarball,
+tarball url, name@tag, name@version, or name), this command will fetch
+it to the cache, and then copy the tarball to the current working
+directory as <name>-<version>.tgz, and then write the filenames out to
+stdout.
+
If the same package is specified multiple times, then the file will be
+overwritten the second time.
+
If no arguments are supplied, then npm packs the current package folder.
Publishes a package to the registry so that it can be installed by name. See
+npm-developers(7) for details on what's included in the published package, as
+well as details on how the package is built.
+
By default npm will publish to the public registry. This can be overridden by
+specifying a different default registry or using a npm-scope(7) in the name
+(see package.json(5)).
+
+
<folder>:
+A folder containing a package.json file
+
+
<tarball>:
+A url or file path to a gzipped tar archive containing a single folder
+with a package.json file inside.
+
+
[--tag <tag>]
+Registers the published package with the given tag, such that npm install
+<name>@<tag> will install this version. By default, npm publish updates
+and npm install installs the latest tag.
+
+
+
Fails if the package name and version combination already exists in
+the specified registry.
+
Once a package is published with a given name and version, that
+specific name and version combination can never be used again, even if
+it is removed with npm-unpublish(1).
This command runs the npm build command on the matched folders. This is useful
+when you install a new version of node, and must recompile all your C++ addons with
+the new binary.
npm repo <pkgname>
+npm repo (with no args in a package dir)
+
DESCRIPTION
+
This command tries to guess at the likely location of a package's
+repository URL, and then tries to open it using the --browser
+config param. If no package name is provided, it will search for
+a package.json in the current folder and use the name property.
+
CONFIGURATION
+
browser
+
+
Default: OS X: "open", Windows: "start", Others: "xdg-open"
+
Type: String
+
+
The browser that is called by the npm repo command to open websites.
This runs a package's "restart" script, if one was provided. Otherwise it runs
+package's "stop" script, if one was provided, and then the "start" script.
This runs an arbitrary command from a package's "scripts" object.
+If no package name is provided, it will search for a package.json
+in the current folder and use its "scripts" object. If no "command"
+is provided, it will list the available top level scripts.
+
It is used by the test, start, restart, and stop commands, but can be
+called directly, as well.
+
As of npm@2.0.0, you can
+use custom arguments when executing scripts. The special option -- is used by
+getopt to delimit the end of the options. npm will pass
+all the arguments after the -- directly to your script:
+
npm run test -- --grep="pattern"
+
The arguments will only be passed to the script specified after npm run
+and not to any pre or post script.
npm search [--long] [search terms ...]
+npm s [search terms ...]
+npm se [search terms ...]
+
DESCRIPTION
+
Search the registry for packages matching the search terms.
+
If a term starts with /, then it's interpreted as a regular expression.
+A trailing / will be ignored in this case. (Note that many regular
+expression characters must be escaped or quoted in most shells.)
+
CONFIGURATION
+
long
+
+
Default: false
+
Type: Boolean
+
+
Display full package descriptions and other long text across multiple
+lines. When disabled (default) search results are truncated to fit
+neatly on a single line. Modules with extremely long names will
+fall on multiple lines.
This command locks down the versions of a package's dependencies so
+that you can control exactly which versions of each dependency will be
+used when your package is installed. The "package.json" file is still
+required if you want to use "npm install".
+
By default, "npm install" recursively installs the target's
+dependencies (as specified in package.json), choosing the latest
+available version that satisfies the dependency's semver pattern. In
+some situations, particularly when shipping software where each change
+is tightly managed, it's desirable to fully specify each version of
+each dependency recursively so that subsequent builds and deploys do
+not inadvertently pick up newer versions of a dependency that satisfy
+the semver pattern. Specifying specific semver patterns in each
+dependency's package.json would facilitate this, but that's not always
+possible or desirable, as when another author owns the npm package.
+It's also possible to check dependencies directly into source control,
+but that may be undesirable for other reasons.
If these are the only versions of A, B, and C available in the
+registry, then a normal "npm install A" will install:
+
A@0.1.0
+`-- B@0.0.1
+ `-- C@0.0.1
+
However, if B@0.0.2 is published, then a fresh "npm install A" will
+install:
+
A@0.1.0
+`-- B@0.0.2
+ `-- C@0.0.1
+
assuming the new version did not modify B's dependencies. Of course,
+the new version of B could include a new version of C and any number
+of new dependencies. If such changes are undesirable, the author of A
+could specify a dependency on B@0.0.1. However, if A's author and B's
+author are not the same person, there's no way for A's author to say
+that he or she does not want to pull in newly published versions of C
+when B hasn't changed at all.
+
In this case, A's author can run
+
npm shrinkwrap
+
This generates npm-shrinkwrap.json, which will look something like this:
The shrinkwrap command has locked down the dependencies based on
+what's currently installed in node_modules. When "npm install"
+installs a package with a npm-shrinkwrap.json file in the package
+root, the shrinkwrap file (rather than package.json files) completely
+drives the installation of that package and all of its dependencies
+(recursively). So now the author publishes A@0.1.0, and subsequent
+installs of this package will use B@0.0.1 and C@0.1.0, regardless the
+dependencies and versions listed in A's, B's, and C's package.json
+files.
+
Using shrinkwrapped packages
+
Using a shrinkwrapped package is no different than using any other
+package: you can "npm install" it by hand, or add a dependency to your
+package.json file and "npm install" it.
+
Building shrinkwrapped packages
+
To shrinkwrap an existing package:
+
+
Run "npm install" in the package root to install the current
+versions of all dependencies.
+
Validate that the package works as expected with these versions.
+
Run "npm shrinkwrap", add npm-shrinkwrap.json to git, and publish
+your package.
+
+
To add or update a dependency in a shrinkwrapped package:
+
+
Run "npm install" in the package root to install the current
+versions of all dependencies.
+
Add or update dependencies. "npm install" each new or updated
+package individually and then update package.json. Note that they
+must be explicitly named in order to be installed: running npm
+install with no arguments will merely reproduce the existing
+shrinkwrap.
+
Validate that the package works as expected with the new
+dependencies.
+
Run "npm shrinkwrap", commit the new npm-shrinkwrap.json, and
+publish your package.
+
+
You can use npm-outdated(1) to view dependencies with newer versions
+available.
+
Other Notes
+
A shrinkwrap file must be consistent with the package's package.json
+file. "npm shrinkwrap" will fail if required dependencies are not
+already installed, since that would result in a shrinkwrap that
+wouldn't actually work. Similarly, the command will fail if there are
+extraneous packages (not referenced by package.json), since that would
+indicate that package.json is not correct.
+
Since "npm shrinkwrap" is intended to lock down your dependencies for
+production use, devDependencies will not be included unless you
+explicitly set the --dev flag when you run npm shrinkwrap. If
+installed devDependencies are excluded, then npm will print a
+warning. If you want them to be installed with your module by
+default, please consider adding them to dependencies instead.
+
If shrinkwrapped package A depends on shrinkwrapped package B, B's
+shrinkwrap will not be used as part of the installation of A. However,
+because A's shrinkwrap is constructed from a valid installation of B
+and recursively specifies all dependencies, the contents of B's
+shrinkwrap will implicitly be included in A's shrinkwrap.
+
Caveats
+
If you wish to lock down the specific bytes included in a package, for
+example to have 100% confidence in being able to reproduce a
+deployment or build, then you ought to check your dependencies into
+source control, or pursue some other mechanism that can verify
+contents rather than versions.
If the specified package has a git repository url in its package.json
+description, then this command will add it as a git submodule at
+node_modules/<pkg name>.
+
This is a convenience only. From then on, it's up to you to manage
+updates by using the appropriate git commands. npm will stubbornly
+refuse to update, modify, or remove anything with a .git subfolder
+in it.
+
This command also does not install missing dependencies, if the package
+does not include them in its git repository. If npm ls reports that
+things are missing, you can either install, link, or submodule them yourself,
+or you can do npm explore <pkgname> -- npm install to install the
+dependencies into the submodule folder.
It is generally considered bad behavior to remove versions of a library
+that others are depending on!
+
Consider using the deprecate command
+instead, if your intent is to encourage users to upgrade.
+
There is plenty of room on the registry.
+
DESCRIPTION
+
This removes a package version from the registry, deleting its
+entry and removing the tarball.
+
If no version is specified, or if all versions are removed then
+the root package entry is removed from the registry entirely.
+
Even if a package version is unpublished, that specific name and
+version combination can never be reused. In order to publish the
+package again, a new version number must be used.
+
The scope is optional and follows the usual rules for npm-scope(7).
npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease]
+
DESCRIPTION
+
Run this in a package directory to bump the version and write the new
+data back to the package.json file.
+
The newversion argument should be a valid semver string, or a
+valid second argument to semver.inc (one of "patch", "minor", "major",
+"prepatch", "preminor", "premajor", "prerelease"). In the second case,
+the existing version will be incremented by 1 in the specified field.
+
If run in a git repo, it will also create a version commit and tag, and
+fail if the repo is not clean.
+
If supplied with --message (shorthand: -m) config option, npm will
+use it as a commit message when creating a version commit. If the
+message config contains %s then that will be replaced with the
+resulting version number. For example:
+
npm version patch -m "Upgrade to %s for reasons"
+
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. 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/) <i@izs.me>"
+2048-bit RSA key, ID 6C481CF6, created 2010-08-31
+
+Enter passphrase:
+
npm view [@<scope>/]<name>[@<version>] [<field>[.<subfield>]...]
+npm v [@<scope>/]<name>[@<version>] [<field>[.<subfield>]...]
+
DESCRIPTION
+
This command shows data about a package and prints it to the stream
+referenced by the outfd config, which defaults to stdout.
+
To show the package registry entry for the connect package, you can do
+this:
+
npm view connect
+
The default version is "latest" if unspecified.
+
Field names can be specified after the package descriptor.
+For example, to show the dependencies of the ronn package at version
+0.3.5, you could do the following:
+
npm view ronn@0.3.5 dependencies
+
You can view child field by separating them with a period.
+To view the git repository URL for the latest version of npm, you could
+do this:
+
npm view npm repository.url
+
This makes it easy to view information about a dependency with a bit of
+shell scripting. For example, to view all the data about the version of
+opts that ronn depends on, you can do this:
+
npm view opts@$(npm view ronn dependencies.opts)
+
For fields that are arrays, requesting a non-numeric field will return
+all of the values from the objects in the list. For example, to get all
+the contributor names for the "express" project, you can do this:
+
npm view express contributors.email
+
You may also use numeric indices in square braces to specifically select
+an item in an array field. To just get the email address of the first
+contributor in the list, you can do this:
+
npm view express contributors[0].email
+
Multiple fields may be specified, and will be printed one after another.
+For exampls, to get all the contributor names and email addresses, you
+can do this:
"Person" fields are shown as a string if they would be shown as an
+object. So, for example, this will show the list of npm contributors in
+the shortened string format. (See package.json(5) for more on this.)
+
npm view npm contributors
+
If a version range is provided, then data will be printed for every
+matching version of the package. This will show which version of jsdom
+was required by each matching version of yui3:
+
npm view yui3@'>0.5.4' dependencies.jsdom
+
OUTPUT
+
If only a single string field for a single version is output, then it
+will not be colorized or quoted, so as to enable piping the output to
+another command. If the field is an object, it will be output as a JavaScript object literal.
+
If the --json flag is given, the outputted fields will be JSON.
+
If the version range matches multiple versions, than each printed value
+will be prefixed with the version it applies to.
+
If multiple fields are requested, than each of them are prefixed with
+the field name.
npm is the package manager for the Node JavaScript platform. It puts
+modules in place so that node can find them, and manages dependency
+conflicts intelligently.
+
It is extremely configurable to support a wide variety of use cases.
+Most commonly, it is used to publish, discover, install, and develop node
+programs.
+
Run npm help to get a list of available commands.
+
INTRODUCTION
+
You probably got npm because you want to install stuff.
+
Use npm install blerg to install the latest version of "blerg". Check out
+npm-install(1) for more info. It can do a lot of stuff.
+
Use the npm search command to show everything that's available.
+Use npm ls to show everything you've installed.
+
DEPENDENCIES
+
If a package references to another package with a git URL, npm depends
+on a preinstalled git.
+
If one of the packages npm tries to install is a native node module and
+requires compiling of C++ Code, npm will use
+node-gyp for that task.
+For a Unix system, node-gyp
+needs Python, make and a buildchain like GCC. On Windows,
+Python and Microsoft Visual Studio C++ is needed. Python 3 is
+not supported by node-gyp.
+For more information visit
+the node-gyp repository and
+the node-gyp Wiki.
global mode: npm installs packages into the install prefix at
+prefix/lib/node_modules and bins are installed in prefix/bin.
+
local mode: npm installs packages into the current project directory, which
+defaults to the current working directory. Packages are installed to
+./node_modules, and bins are installed to ./node_modules/.bin.
+
+
Local mode is the default. Use --global or -g on any command to
+operate in global mode instead.
+
DEVELOPER USAGE
+
If you're using npm to develop and publish your code, check out the
+following help topics:
link:
+For linking your current working code into Node's path, so that you
+don't have to reinstall every time you make a change. Use
+npm link to do this.
+
install:
+It's a good idea to install things if you don't need the symbolic link.
+Especially, installing other peoples code from the registry is done via
+npm install
+
adduser:
+Create an account or log in. Credentials are stored in the
+user config file.
+
publish:
+Use the npm publish command to upload your code to the registry.
+
+
CONFIGURATION
+
npm is extremely configurable. It reads its configuration options from
+5 places.
+
+
Command line switches: Set a config with --key val. All keys take a value, even if they
+are booleans (the config parser doesn't know what the options are at
+the time of parsing.) If no value is provided, then the option is set
+to boolean true.
+
Environment Variables: Set any config by prefixing the name in an environment variable with
+npm_config_. For example, export npm_config_key=val.
+
User Configs: The file at $HOME/.npmrc is an ini-formatted list of configs. If
+present, it is parsed. If the userconfig option is set in the cli
+or env, then that will be used instead.
+
Global Configs: The file found at ../etc/npmrc (from the node executable, by default
+this resolves to /usr/local/etc/npmrc) will be parsed if it is found.
+If the globalconfig option is set in the cli, env, or user config,
+then that file is parsed instead.
+
Defaults: npm's default configuration options are defined in
+lib/utils/config-defs.js. These must not be changed.
code:
+Read through npm-coding-style(7) if you plan to submit code.
+You don't have to agree with it, but you do have to follow it.
+
docs:
+If you find an error in the documentation, edit the appropriate markdown
+file in the "doc" folder. (Don't worry about generating the man page.)
+
+
Contributors are listed in npm's package.json file. You can view them
+easily by doing npm view npm contributors.
+
If you would like to contribute, but don't know what to work on, check
+the issues list or ask on the mailing list.
npm puts various things on your computer. That's its job.
+
This document will tell you what it puts where.
+
tl;dr
+
+
Local install (default): puts stuff in ./node_modules of the current
+package root.
+
Global install (with -g): puts stuff in /usr/local or wherever node
+is installed.
+
Install it locally if you're going to require() it.
+
Install it globally if you're going to run it on the command line.
+
If you need both, then install it in both places, or use npm link.
+
+
prefix Configuration
+
The prefix config defaults to the location where node is installed.
+On most systems, this is /usr/local, and most of the time is the same
+as node's process.installPrefix.
+
On windows, this is the exact location of the node.exe binary. On Unix
+systems, it's one level up, since node is typically installed at
+{prefix}/bin/node rather than {prefix}/node.exe.
+
When the global flag is set, npm installs things into this prefix.
+When it is not set, it uses the root of the current package, or the
+current working directory if not in a package already.
+
Node Modules
+
Packages are dropped into the node_modules folder under the prefix.
+When installing locally, this means that you can
+require("packagename") to load its main module, or
+require("packagename/lib/path/to/sub/module") to load other modules.
+
Global installs on Unix systems go to {prefix}/lib/node_modules.
+Global installs on Windows go to {prefix}/node_modules (that is, no
+lib folder.)
+
Scoped packages are installed the same way, except they are grouped together
+in a sub-folder of the relevant node_modules folder with the name of that
+scope prefix by the @ symbol, e.g. npm install @myorg/package would place
+the package in {prefix}/node_modules/@myorg/package. See scopes(7) for
+more details.
+
If you wish to require() a package, then install it locally.
+
Executables
+
When in global mode, executables are linked into {prefix}/bin on Unix,
+or directly into {prefix} on Windows.
+
When in local mode, executables are linked into
+./node_modules/.bin so that they can be made available to scripts run
+through npm. (For example, so that a test runner will be in the path
+when you run npm test.)
+
Man Pages
+
When in global mode, man pages are linked into {prefix}/share/man.
+
When in local mode, man pages are not installed.
+
Man pages are not installed on Windows systems.
+
Cache
+
See npm-cache(1). Cache files are stored in ~/.npm on Posix, or
+~/npm-cache on Windows.
+
This is controlled by the cache configuration param.
+
Temp Files
+
Temporary files are stored by default in the folder specified by the
+tmp config, which defaults to the TMPDIR, TMP, or TEMP environment
+variables, or /tmp on Unix and c:\windows\temp on Windows.
+
Temp files are given a unique folder under this root for each run of the
+program, and are deleted upon successful exit.
+
More Information
+
When installing locally, npm first tries to find an appropriate
+prefix folder. This is so that npm install foo@1.2.3 will install
+to the sensible root of your package, even if you happen to have cded
+into some other folder.
+
Starting at the $PWD, npm will walk up the folder tree checking for a
+folder that contains either a package.json file, or a node_modules
+folder. If such a thing is found, then that is treated as the effective
+"current directory" for the purpose of running npm commands. (This
+behavior is inspired by and similar to git's .git-folder seeking
+logic when running git commands in a working dir.)
+
If no package root is found, then the current folder is used.
+
When you run npm install foo@1.2.3, then the package is loaded into
+the cache, and then unpacked into ./node_modules/foo. Then, any of
+foo's dependencies are similarly unpacked into
+./node_modules/foo/node_modules/....
+
Any bin files are symlinked to ./node_modules/.bin/, so that they may
+be found by npm scripts when necessary.
+
Global Installation
+
If the global configuration is set to true, then npm will
+install packages "globally".
+
For global installation, packages are installed roughly the same way,
+but using the folders described above.
+
Cycles, Conflicts, and Folder Parsimony
+
Cycles are handled using the property of node's module system that it
+walks up the directories looking for node_modules folders. So, at every
+stage, if a package is already installed in an ancestor node_modules
+folder, then it is not installed at the current location.
+
Consider the case above, where foo -> bar -> baz. Imagine if, in
+addition to that, baz depended on bar, so you'd have:
+foo -> bar -> baz -> bar -> baz .... However, since the folder
+structure is: foo/node_modules/bar/node_modules/baz, there's no need to
+put another copy of bar into .../baz/node_modules, since when it calls
+require("bar"), it will get the copy that is installed in
+foo/node_modules/bar.
+
This shortcut is only used if the exact same
+version would be installed in multiple nested node_modules folders. It
+is still possible to have a/node_modules/b/node_modules/a if the two
+"a" packages are different versions. However, without repeating the
+exact same package multiple times, an infinite regress will always be
+prevented.
+
Another optimization can be made by installing dependencies at the
+highest level possible, below the localized "target" folder.
Since foo depends directly on bar@1.2.3 and baz@1.2.3, those are
+installed in foo's node_modules folder.
+
Even though the latest copy of blerg is 1.3.7, foo has a specific
+dependency on version 1.2.5. So, that gets installed at [A]. Since the
+parent installation of blerg satisfies bar's dependency on blerg@1.x,
+it does not install another copy under [B].
+
Bar [B] also has dependencies on baz and asdf, so those are installed in
+bar's node_modules folder. Because it depends on baz@2.x, it cannot
+re-use the baz@1.2.3 installed in the parent node_modules folder [D],
+and must install its own copy [C].
+
Underneath bar, the baz -> quux -> bar dependency creates a cycle.
+However, because bar is already in quux's ancestry [B], it does not
+unpack another copy of bar into that folder.
+
Underneath foo -> baz [D], quux's [E] folder tree is empty, because its
+dependency on bar is satisfied by the parent folder copy installed at [B].
+
For a graphical breakdown of what is installed where, use npm ls.
+
Publishing
+
Upon publishing, npm will look in the node_modules folder. If any of
+the items there are not in the bundledDependencies array, then they will
+not be included in the package tarball.
+
This allows a package maintainer to install all of their dependencies
+(and dev dependencies) locally, but only re-publish those items that
+cannot be found elsewhere. See package.json(5) for more information.
npm puts various things on your computer. That's its job.
+
This document will tell you what it puts where.
+
tl;dr
+
+
Local install (default): puts stuff in ./node_modules of the current
+package root.
+
Global install (with -g): puts stuff in /usr/local or wherever node
+is installed.
+
Install it locally if you're going to require() it.
+
Install it globally if you're going to run it on the command line.
+
If you need both, then install it in both places, or use npm link.
+
+
prefix Configuration
+
The prefix config defaults to the location where node is installed.
+On most systems, this is /usr/local, and most of the time is the same
+as node's process.installPrefix.
+
On windows, this is the exact location of the node.exe binary. On Unix
+systems, it's one level up, since node is typically installed at
+{prefix}/bin/node rather than {prefix}/node.exe.
+
When the global flag is set, npm installs things into this prefix.
+When it is not set, it uses the root of the current package, or the
+current working directory if not in a package already.
+
Node Modules
+
Packages are dropped into the node_modules folder under the prefix.
+When installing locally, this means that you can
+require("packagename") to load its main module, or
+require("packagename/lib/path/to/sub/module") to load other modules.
+
Global installs on Unix systems go to {prefix}/lib/node_modules.
+Global installs on Windows go to {prefix}/node_modules (that is, no
+lib folder.)
+
Scoped packages are installed the same way, except they are grouped together
+in a sub-folder of the relevant node_modules folder with the name of that
+scope prefix by the @ symbol, e.g. npm install @myorg/package would place
+the package in {prefix}/node_modules/@myorg/package. See scopes(7) for
+more details.
+
If you wish to require() a package, then install it locally.
+
Executables
+
When in global mode, executables are linked into {prefix}/bin on Unix,
+or directly into {prefix} on Windows.
+
When in local mode, executables are linked into
+./node_modules/.bin so that they can be made available to scripts run
+through npm. (For example, so that a test runner will be in the path
+when you run npm test.)
+
Man Pages
+
When in global mode, man pages are linked into {prefix}/share/man.
+
When in local mode, man pages are not installed.
+
Man pages are not installed on Windows systems.
+
Cache
+
See npm-cache(1). Cache files are stored in ~/.npm on Posix, or
+~/npm-cache on Windows.
+
This is controlled by the cache configuration param.
+
Temp Files
+
Temporary files are stored by default in the folder specified by the
+tmp config, which defaults to the TMPDIR, TMP, or TEMP environment
+variables, or /tmp on Unix and c:\windows\temp on Windows.
+
Temp files are given a unique folder under this root for each run of the
+program, and are deleted upon successful exit.
+
More Information
+
When installing locally, npm first tries to find an appropriate
+prefix folder. This is so that npm install foo@1.2.3 will install
+to the sensible root of your package, even if you happen to have cded
+into some other folder.
+
Starting at the $PWD, npm will walk up the folder tree checking for a
+folder that contains either a package.json file, or a node_modules
+folder. If such a thing is found, then that is treated as the effective
+"current directory" for the purpose of running npm commands. (This
+behavior is inspired by and similar to git's .git-folder seeking
+logic when running git commands in a working dir.)
+
If no package root is found, then the current folder is used.
+
When you run npm install foo@1.2.3, then the package is loaded into
+the cache, and then unpacked into ./node_modules/foo. Then, any of
+foo's dependencies are similarly unpacked into
+./node_modules/foo/node_modules/....
+
Any bin files are symlinked to ./node_modules/.bin/, so that they may
+be found by npm scripts when necessary.
+
Global Installation
+
If the global configuration is set to true, then npm will
+install packages "globally".
+
For global installation, packages are installed roughly the same way,
+but using the folders described above.
+
Cycles, Conflicts, and Folder Parsimony
+
Cycles are handled using the property of node's module system that it
+walks up the directories looking for node_modules folders. So, at every
+stage, if a package is already installed in an ancestor node_modules
+folder, then it is not installed at the current location.
+
Consider the case above, where foo -> bar -> baz. Imagine if, in
+addition to that, baz depended on bar, so you'd have:
+foo -> bar -> baz -> bar -> baz .... However, since the folder
+structure is: foo/node_modules/bar/node_modules/baz, there's no need to
+put another copy of bar into .../baz/node_modules, since when it calls
+require("bar"), it will get the copy that is installed in
+foo/node_modules/bar.
+
This shortcut is only used if the exact same
+version would be installed in multiple nested node_modules folders. It
+is still possible to have a/node_modules/b/node_modules/a if the two
+"a" packages are different versions. However, without repeating the
+exact same package multiple times, an infinite regress will always be
+prevented.
+
Another optimization can be made by installing dependencies at the
+highest level possible, below the localized "target" folder.
Since foo depends directly on bar@1.2.3 and baz@1.2.3, those are
+installed in foo's node_modules folder.
+
Even though the latest copy of blerg is 1.3.7, foo has a specific
+dependency on version 1.2.5. So, that gets installed at [A]. Since the
+parent installation of blerg satisfies bar's dependency on blerg@1.x,
+it does not install another copy under [B].
+
Bar [B] also has dependencies on baz and asdf, so those are installed in
+bar's node_modules folder. Because it depends on baz@2.x, it cannot
+re-use the baz@1.2.3 installed in the parent node_modules folder [D],
+and must install its own copy [C].
+
Underneath bar, the baz -> quux -> bar dependency creates a cycle.
+However, because bar is already in quux's ancestry [B], it does not
+unpack another copy of bar into that folder.
+
Underneath foo -> baz [D], quux's [E] folder tree is empty, because its
+dependency on bar is satisfied by the parent folder copy installed at [B].
+
For a graphical breakdown of what is installed where, use npm ls.
+
Publishing
+
Upon publishing, npm will look in the node_modules folder. If any of
+the items there are not in the bundledDependencies array, then they will
+not be included in the package tarball.
+
This allows a package maintainer to install all of their dependencies
+(and dev dependencies) locally, but only re-publish those items that
+cannot be found elsewhere. See package.json(5) for more information.
This document is all you need to know about what's required in your package.json
+file. It must be actual JSON, not just a JavaScript object literal.
+
A lot of the behavior described in this document is affected by the config
+settings described in npm-config(7).
+
name
+
The most important things in your package.json are the name and version fields.
+Those are actually required, and your package won't install without
+them. The name and version together form an identifier that is assumed
+to be completely unique. Changes to the package should come along with
+changes to the version.
+
The name is what your thing is called. Some tips:
+
+
Don't put "js" or "node" in the name. It's assumed that it's js, since you're
+writing a package.json file, and you can specify the engine using the "engines"
+field. (See below.)
+
The name ends up being part of a URL, an argument on the command line, and a
+folder name. Any name with non-url-safe characters will be rejected.
+Also, it can't start with a dot or an underscore.
+
The name will probably be passed as an argument to require(), so it should
+be something short, but also reasonably descriptive.
+
You may want to check the npm registry to see if there's something by that name
+already, before you get too attached to it. http://registry.npmjs.org/
+
+
A name can be optionally prefixed by a scope, e.g. @myorg/mypackage. See
+npm-scope(7) for more detail.
+
version
+
The most important things in your package.json are the name and version fields.
+Those are actually required, and your package won't install without
+them. The name and version together form an identifier that is assumed
+to be completely unique. Changes to the package should come along with
+changes to the version.
+
Version must be parseable by
+node-semver, which is bundled
+with npm as a dependency. (npm install semver to use it yourself.)
Put a description in it. It's a string. This helps people discover your
+package, as it's listed in npm search.
+
keywords
+
Put keywords in it. It's an array of strings. This helps people
+discover your package as it's listed in npm search.
+
homepage
+
The url to the project homepage.
+
NOTE: This is not the same as "url". If you put a "url" field,
+then the registry will think it's a redirection to your package that has
+been published somewhere else, and spit at you.
+
Literally. Spit. I'm so not kidding.
+
bugs
+
The url to your project's issue tracker and / or the email address to which
+issues should be reported. These are helpful for people who encounter issues
+with your package.
You can specify either one or both values. If you want to provide only a url,
+you can specify the value for "bugs" as a simple string instead of an object.
+
If a url is provided, it will be used by the npm bugs command.
+
license
+
You should specify a license for your package so that people know how they are
+permitted to use it, and any restrictions you're placing on it.
+
The simplest way, assuming you're using a common license such as BSD-3-Clause
+or MIT, is to just specify the standard SPDX ID of the license you're using,
+like this:
It's also a good idea to include a LICENSE file at the top level in
+your package.
+
people fields: author, contributors
+
The "author" is one person. "contributors" is an array of people. A "person"
+is an object with a "name" field and optionally "url" and "email", like this:
npm also sets a top-level "maintainers" field with your npm user info.
+
files
+
The "files" field is an array of files to include in your project. If
+you name a folder in the array, then it will also include the files
+inside that folder. (Unless they would be ignored by another rule.)
+
You can also provide a ".npmignore" file in the root of your package,
+which will keep files from being included, even if they would be picked
+up by the files array. The ".npmignore" file works just like a
+".gitignore".
+
main
+
The main field is a module ID that is the primary entry point to your program.
+That is, if your package is named foo, and a user installs it, and then does
+require("foo"), then your main module's exports object will be returned.
+
This should be a module ID relative to the root of your package folder.
+
For most modules, it makes the most sense to have a main script and often not
+much else.
+
bin
+
A lot of packages have one or more executable files that they'd like to
+install into the PATH. npm makes this pretty easy (in fact, it uses this
+feature to install the "npm" executable.)
+
To use this, supply a bin field in your package.json which is a map of
+command name to local file name. On install, npm will symlink that file into
+prefix/bin for global installs, or ./node_modules/.bin/ for local
+installs.
+
For example, npm has this:
+
{ "bin" : { "npm" : "./cli.js" } }
+
So, when you install npm, it'll create a symlink from the cli.js script to
+/usr/local/bin/npm.
+
If you have a single executable, and its name should be the name
+of the package, then you can just supply it as a string. For example:
Man files must end with a number, and optionally a .gz suffix if they are
+compressed. The number dictates which man section the file is installed into.
The CommonJS Packages spec details a
+few ways that you can indicate the structure of your package using a directories
+object. If you look at npm's package.json,
+you'll see that it has directories for doc, lib, and man.
+
In the future, this information may be used in other creative ways.
+
directories.lib
+
Tell people where the bulk of your library is. Nothing special is done
+with the lib folder in any way, but it's useful meta info.
+
directories.bin
+
If you specify a bin directory, then all the files in that folder will
+be added as children of the bin path.
+
If you have a bin path already, then this has no effect.
+
directories.man
+
A folder that is full of man pages. Sugar to generate a "man" array by
+walking the folder.
+
directories.doc
+
Put markdown files in here. Eventually, these will be displayed nicely,
+maybe, someday.
+
directories.example
+
Put example scripts in here. Someday, it might be exposed in some clever way.
+
repository
+
Specify the place where your code lives. This is helpful for people who
+want to contribute. If the git repo is on github, then the npm docs
+command will be able to find you.
The URL should be a publicly available (perhaps read-only) url that can be handed
+directly to a VCS program without any modification. It should not be a url to an
+html project page that you put in your browser. It's for computers.
+
scripts
+
The "scripts" property is a dictionary containing script commands that are run
+at various times in the lifecycle of your package. The key is the lifecycle
+event, and the value is the command to run at that point.
+
See npm-scripts(7) to find out more about writing package scripts.
+
config
+
A "config" object can be used to set configuration parameters used in package
+scripts that persist across upgrades. For instance, if a package had the
+following:
and then had a "start" command that then referenced the
+npm_package_config_port environment variable, then the user could
+override that by doing npm config set foo:port 8001.
Dependencies are specified in a simple object that maps a package name to a
+version range. The version range is a string which has one or more
+space-separated descriptors. Dependencies can also be identified with a
+tarball or git URL.
+
Please do not put test harnesses or transpilers in your
+dependencies object. See devDependencies, below.
+
See semver(7) for more details about specifying version ranges.
+
+
version Must match version exactly
+
>version Must be greater than version
+
>=version etc
+
<version
+
<=version
+
~version "Approximately equivalent to version" See semver(7)
As of version 2.0.0 you can provide a path to a local directory that contains a
+package. Local paths can be saved using npm install --save, using any of
+these forms:
+
../foo/bar
+~/foo/bar
+./foo/bar
+/foo/bar
+
in which case they will be normalized to a relative path and added to your
+package.json. For example:
This feature is helpful for local offline development and creating
+tests that require npm installing where you don't want to hit an
+external server, but should not be used when publishing packages
+to the public registry.
+
devDependencies
+
If someone is planning on downloading and using your module in their
+program, then they probably don't want or need to download and build
+the external test or documentation framework that you use.
+
In this case, it's best to map these additional items in a devDependencies
+object.
+
These things will be installed when doing npm link or npm install
+from the root of a package, and can be managed like any other npm
+configuration param. See npm-config(7) for more on the topic.
+
For build steps that are not platform-specific, such as compiling
+CoffeeScript or other languages to JavaScript, use the prepublish
+script to do this, and make the required package a devDependency.
The prepublish script will be run before publishing, so that users
+can consume the functionality without requiring them to compile it
+themselves. In dev mode (ie, locally running npm install), it'll
+run this script as well, so that you can test it easily.
+
peerDependencies
+
In some cases, you want to express the compatibility of your package with an
+host tool or library, while not necessarily doing a require of this host.
+This is usually refered to as a plugin. Notably, your module may be exposing
+a specific interface, expected and specified by the host documentation.
This ensures your package tea-latte can be installed along with the second
+major version of the host package tea only. The host package is automatically
+installed if needed. npm install tea-latte could possibly yield the following
+dependency graph:
+
âââ tea-latte@1.3.5
+âââ tea@2.2.0
+
Trying to install another plugin with a conflicting requirement will cause an
+error. For this reason, make sure your plugin requirement is as broad as
+possible, and not to lock it down to specific patch versions.
+
Assuming the host complies with semver, only changes in
+the host package's major version will break your plugin. Thus, if you've worked
+with every 1.x version of the host package, use "^1.0" or "1.x" to express
+this. If you depend on features introduced in 1.5.2, use ">= 1.5.2 < 2".
+
bundledDependencies
+
Array of package names that will be bundled when publishing the package.
+
If this is spelled "bundleDependencies", then that is also honorable.
+
optionalDependencies
+
If a dependency can be used, but you would like npm to proceed if it cannot be
+found or fails to install, then you may put it in the optionalDependencies
+object. This is a map of package name to version or url, just like the
+dependencies object. The difference is that build failures do not cause
+installation to fail.
+
It is still your program's responsibility to handle the lack of the
+dependency. For example, something like this:
+
try {
+ var foo = require('foo')
+ var fooVersion = require('foo/package.json').version
+} catch (er) {
+ foo = null
+}
+if ( notGoodFooVersion(fooVersion) ) {
+ foo = null
+}
+
+// .. then later in your program ..
+
+if (foo) {
+ foo.doFooThings()
+}
+
Entries in optionalDependencies will override entries of the same name in
+dependencies, so it's usually best to only put in one place.
+
engines
+
You can specify the version of node that your stuff works on:
+
{ "engines" : { "node" : ">=0.10.3 <0.12" } }
+
And, like with dependencies, if you don't specify the version (or if you
+specify "*" as the version), then any version of node will do.
+
If you specify an "engines" field, then npm will require that "node" be
+somewhere on that list. If "engines" is omitted, then npm will just assume
+that it works on node.
+
You can also use the "engines" field to specify which versions of npm
+are capable of properly installing your program. For example:
+
{ "engines" : { "npm" : "~1.0.20" } }
+
Note that, unless the user has set the engine-strict config flag, this
+field is advisory only.
+
engineStrict
+
If you are sure that your module will definitely not run properly on
+versions of Node/npm other than those specified in the engines object,
+then you can set "engineStrict": true in your package.json file.
+This will override the user's engine-strict config setting.
+
Please do not do this unless you are really very very sure. If your
+engines object is something overly restrictive, you can quite easily and
+inadvertently lock yourself into obscurity and prevent your users from
+updating to new versions of Node. Consider this choice carefully. If
+people abuse it, it will be removed in a future version of npm.
+
os
+
You can specify which operating systems your
+module will run on:
+
"os" : [ "darwin", "linux" ]
+
You can also blacklist instead of whitelist operating systems,
+just prepend the blacklisted os with a '!':
+
"os" : [ "!win32" ]
+
The host operating system is determined by process.platform
+
It is allowed to both blacklist, and whitelist, although there isn't any
+good reason to do this.
+
cpu
+
If your code only runs on certain cpu architectures,
+you can specify which ones.
+
"cpu" : [ "x64", "ia32" ]
+
Like the os option, you can also blacklist architectures:
+
"cpu" : [ "!arm", "!mips" ]
+
The host architecture is determined by process.arch
+
preferGlobal
+
If your package is primarily a command-line application that should be
+installed globally, then set this value to true to provide a warning
+if it is installed locally.
+
It doesn't actually prevent users from installing it locally, but it
+does help prevent some confusion if it doesn't work as expected.
+
private
+
If you set "private": true in your package.json, then npm will refuse
+to publish it.
+
This is a way to prevent accidental publication of private repositories. If
+you would like to ensure that a given package is only ever published to a
+specific registry (for example, an internal registry), then use the
+publishConfig dictionary described below to override the registry config
+param at publish-time.
+
publishConfig
+
This is a set of config values that will be used at publish-time. It's
+especially handy if you want to set the tag or registry, so that you can
+ensure that a given package is not tagged with "latest" or published to
+the global public registry by default.
+
Any config values can be overridden, but of course only "tag" and
+"registry" probably matter for the purposes of publishing.
+
See npm-config(7) to see the list of config options that can be
+overridden.
+
DEFAULT VALUES
+
npm will default some values based on package contents.
+
+
"scripts": {"start": "node server.js"}
+
If there is a server.js file in the root of your package, then npm
+will default the start command to node server.js.
+
+
"scripts":{"preinstall": "node-gyp rebuild"}
+
If there is a binding.gyp file in the root of your package, npm will
+default the preinstall command to compile using node-gyp.
+
+
"contributors": [...]
+
If there is an AUTHORS file in the root of your package, npm will
+treat each line as a Name <email> (url) format, where email and url
+are optional. Lines which start with a # or are blank, will be
+ignored.
All npm config files are an ini-formatted list of key = value
+parameters. Environment variables can be replaced using
+${VARIABLE_NAME}. For example:
+
prefix = ${HOME}/.npm-packages
+
Each of these files is loaded, and config options are resolved in
+priority order. For example, a setting in the userconfig file would
+override the setting in the globalconfig file.
+
Per-project config file
+
When working locally in a project, a .npmrc file in the root of the
+project (ie, a sibling of node_modules and package.json) will set
+config values specific to this project.
+
Note that this only applies to the root of the project that you're
+running npm in. It has no effect when your module is published. For
+example, you can't publish a module that forces itself to install
+globally, or in a different location.
+
Per-user config file
+
$HOME/.npmrc (or the userconfig param, if set in the environment
+or on the command line)
+
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.
+Environment variables can be replaced as above.
+
Built-in config file
+
path/to/npm/itself/npmrc
+
This is an unchangeable "builtin" configuration file that npm keeps
+consistent across updates. Set fields in here using the ./configure
+script that comes with npm. This is primarily for distribution
+maintainers to override default configs in a standard and consistent
+manner.
This document is all you need to know about what's required in your package.json
+file. It must be actual JSON, not just a JavaScript object literal.
+
A lot of the behavior described in this document is affected by the config
+settings described in npm-config(7).
+
name
+
The most important things in your package.json are the name and version fields.
+Those are actually required, and your package won't install without
+them. The name and version together form an identifier that is assumed
+to be completely unique. Changes to the package should come along with
+changes to the version.
+
The name is what your thing is called. Some tips:
+
+
Don't put "js" or "node" in the name. It's assumed that it's js, since you're
+writing a package.json file, and you can specify the engine using the "engines"
+field. (See below.)
+
The name ends up being part of a URL, an argument on the command line, and a
+folder name. Any name with non-url-safe characters will be rejected.
+Also, it can't start with a dot or an underscore.
+
The name will probably be passed as an argument to require(), so it should
+be something short, but also reasonably descriptive.
+
You may want to check the npm registry to see if there's something by that name
+already, before you get too attached to it. http://registry.npmjs.org/
+
+
A name can be optionally prefixed by a scope, e.g. @myorg/mypackage. See
+npm-scope(7) for more detail.
+
version
+
The most important things in your package.json are the name and version fields.
+Those are actually required, and your package won't install without
+them. The name and version together form an identifier that is assumed
+to be completely unique. Changes to the package should come along with
+changes to the version.
+
Version must be parseable by
+node-semver, which is bundled
+with npm as a dependency. (npm install semver to use it yourself.)
Put a description in it. It's a string. This helps people discover your
+package, as it's listed in npm search.
+
keywords
+
Put keywords in it. It's an array of strings. This helps people
+discover your package as it's listed in npm search.
+
homepage
+
The url to the project homepage.
+
NOTE: This is not the same as "url". If you put a "url" field,
+then the registry will think it's a redirection to your package that has
+been published somewhere else, and spit at you.
+
Literally. Spit. I'm so not kidding.
+
bugs
+
The url to your project's issue tracker and / or the email address to which
+issues should be reported. These are helpful for people who encounter issues
+with your package.
You can specify either one or both values. If you want to provide only a url,
+you can specify the value for "bugs" as a simple string instead of an object.
+
If a url is provided, it will be used by the npm bugs command.
+
license
+
You should specify a license for your package so that people know how they are
+permitted to use it, and any restrictions you're placing on it.
+
The simplest way, assuming you're using a common license such as BSD-3-Clause
+or MIT, is to just specify the standard SPDX ID of the license you're using,
+like this:
It's also a good idea to include a LICENSE file at the top level in
+your package.
+
people fields: author, contributors
+
The "author" is one person. "contributors" is an array of people. A "person"
+is an object with a "name" field and optionally "url" and "email", like this:
npm also sets a top-level "maintainers" field with your npm user info.
+
files
+
The "files" field is an array of files to include in your project. If
+you name a folder in the array, then it will also include the files
+inside that folder. (Unless they would be ignored by another rule.)
+
You can also provide a ".npmignore" file in the root of your package,
+which will keep files from being included, even if they would be picked
+up by the files array. The ".npmignore" file works just like a
+".gitignore".
+
main
+
The main field is a module ID that is the primary entry point to your program.
+That is, if your package is named foo, and a user installs it, and then does
+require("foo"), then your main module's exports object will be returned.
+
This should be a module ID relative to the root of your package folder.
+
For most modules, it makes the most sense to have a main script and often not
+much else.
+
bin
+
A lot of packages have one or more executable files that they'd like to
+install into the PATH. npm makes this pretty easy (in fact, it uses this
+feature to install the "npm" executable.)
+
To use this, supply a bin field in your package.json which is a map of
+command name to local file name. On install, npm will symlink that file into
+prefix/bin for global installs, or ./node_modules/.bin/ for local
+installs.
+
For example, npm has this:
+
{ "bin" : { "npm" : "./cli.js" } }
+
So, when you install npm, it'll create a symlink from the cli.js script to
+/usr/local/bin/npm.
+
If you have a single executable, and its name should be the name
+of the package, then you can just supply it as a string. For example:
Man files must end with a number, and optionally a .gz suffix if they are
+compressed. The number dictates which man section the file is installed into.
The CommonJS Packages spec details a
+few ways that you can indicate the structure of your package using a directories
+object. If you look at npm's package.json,
+you'll see that it has directories for doc, lib, and man.
+
In the future, this information may be used in other creative ways.
+
directories.lib
+
Tell people where the bulk of your library is. Nothing special is done
+with the lib folder in any way, but it's useful meta info.
+
directories.bin
+
If you specify a bin directory, then all the files in that folder will
+be added as children of the bin path.
+
If you have a bin path already, then this has no effect.
+
directories.man
+
A folder that is full of man pages. Sugar to generate a "man" array by
+walking the folder.
+
directories.doc
+
Put markdown files in here. Eventually, these will be displayed nicely,
+maybe, someday.
+
directories.example
+
Put example scripts in here. Someday, it might be exposed in some clever way.
+
repository
+
Specify the place where your code lives. This is helpful for people who
+want to contribute. If the git repo is on github, then the npm docs
+command will be able to find you.
The URL should be a publicly available (perhaps read-only) url that can be handed
+directly to a VCS program without any modification. It should not be a url to an
+html project page that you put in your browser. It's for computers.
+
scripts
+
The "scripts" property is a dictionary containing script commands that are run
+at various times in the lifecycle of your package. The key is the lifecycle
+event, and the value is the command to run at that point.
+
See npm-scripts(7) to find out more about writing package scripts.
+
config
+
A "config" object can be used to set configuration parameters used in package
+scripts that persist across upgrades. For instance, if a package had the
+following:
and then had a "start" command that then referenced the
+npm_package_config_port environment variable, then the user could
+override that by doing npm config set foo:port 8001.
Dependencies are specified in a simple object that maps a package name to a
+version range. The version range is a string which has one or more
+space-separated descriptors. Dependencies can also be identified with a
+tarball or git URL.
+
Please do not put test harnesses or transpilers in your
+dependencies object. See devDependencies, below.
+
See semver(7) for more details about specifying version ranges.
+
+
version Must match version exactly
+
>version Must be greater than version
+
>=version etc
+
<version
+
<=version
+
~version "Approximately equivalent to version" See semver(7)
As of version 2.0.0 you can provide a path to a local directory that contains a
+package. Local paths can be saved using npm install --save, using any of
+these forms:
+
../foo/bar
+~/foo/bar
+./foo/bar
+/foo/bar
+
in which case they will be normalized to a relative path and added to your
+package.json. For example:
This feature is helpful for local offline development and creating
+tests that require npm installing where you don't want to hit an
+external server, but should not be used when publishing packages
+to the public registry.
+
devDependencies
+
If someone is planning on downloading and using your module in their
+program, then they probably don't want or need to download and build
+the external test or documentation framework that you use.
+
In this case, it's best to map these additional items in a devDependencies
+object.
+
These things will be installed when doing npm link or npm install
+from the root of a package, and can be managed like any other npm
+configuration param. See npm-config(7) for more on the topic.
+
For build steps that are not platform-specific, such as compiling
+CoffeeScript or other languages to JavaScript, use the prepublish
+script to do this, and make the required package a devDependency.
The prepublish script will be run before publishing, so that users
+can consume the functionality without requiring them to compile it
+themselves. In dev mode (ie, locally running npm install), it'll
+run this script as well, so that you can test it easily.
+
peerDependencies
+
In some cases, you want to express the compatibility of your package with an
+host tool or library, while not necessarily doing a require of this host.
+This is usually refered to as a plugin. Notably, your module may be exposing
+a specific interface, expected and specified by the host documentation.
This ensures your package tea-latte can be installed along with the second
+major version of the host package tea only. The host package is automatically
+installed if needed. npm install tea-latte could possibly yield the following
+dependency graph:
+
âââ tea-latte@1.3.5
+âââ tea@2.2.0
+
Trying to install another plugin with a conflicting requirement will cause an
+error. For this reason, make sure your plugin requirement is as broad as
+possible, and not to lock it down to specific patch versions.
+
Assuming the host complies with semver, only changes in
+the host package's major version will break your plugin. Thus, if you've worked
+with every 1.x version of the host package, use "^1.0" or "1.x" to express
+this. If you depend on features introduced in 1.5.2, use ">= 1.5.2 < 2".
+
bundledDependencies
+
Array of package names that will be bundled when publishing the package.
+
If this is spelled "bundleDependencies", then that is also honorable.
+
optionalDependencies
+
If a dependency can be used, but you would like npm to proceed if it cannot be
+found or fails to install, then you may put it in the optionalDependencies
+object. This is a map of package name to version or url, just like the
+dependencies object. The difference is that build failures do not cause
+installation to fail.
+
It is still your program's responsibility to handle the lack of the
+dependency. For example, something like this:
+
try {
+ var foo = require('foo')
+ var fooVersion = require('foo/package.json').version
+} catch (er) {
+ foo = null
+}
+if ( notGoodFooVersion(fooVersion) ) {
+ foo = null
+}
+
+// .. then later in your program ..
+
+if (foo) {
+ foo.doFooThings()
+}
+
Entries in optionalDependencies will override entries of the same name in
+dependencies, so it's usually best to only put in one place.
+
engines
+
You can specify the version of node that your stuff works on:
+
{ "engines" : { "node" : ">=0.10.3 <0.12" } }
+
And, like with dependencies, if you don't specify the version (or if you
+specify "*" as the version), then any version of node will do.
+
If you specify an "engines" field, then npm will require that "node" be
+somewhere on that list. If "engines" is omitted, then npm will just assume
+that it works on node.
+
You can also use the "engines" field to specify which versions of npm
+are capable of properly installing your program. For example:
+
{ "engines" : { "npm" : "~1.0.20" } }
+
Note that, unless the user has set the engine-strict config flag, this
+field is advisory only.
+
engineStrict
+
If you are sure that your module will definitely not run properly on
+versions of Node/npm other than those specified in the engines object,
+then you can set "engineStrict": true in your package.json file.
+This will override the user's engine-strict config setting.
+
Please do not do this unless you are really very very sure. If your
+engines object is something overly restrictive, you can quite easily and
+inadvertently lock yourself into obscurity and prevent your users from
+updating to new versions of Node. Consider this choice carefully. If
+people abuse it, it will be removed in a future version of npm.
+
os
+
You can specify which operating systems your
+module will run on:
+
"os" : [ "darwin", "linux" ]
+
You can also blacklist instead of whitelist operating systems,
+just prepend the blacklisted os with a '!':
+
"os" : [ "!win32" ]
+
The host operating system is determined by process.platform
+
It is allowed to both blacklist, and whitelist, although there isn't any
+good reason to do this.
+
cpu
+
If your code only runs on certain cpu architectures,
+you can specify which ones.
+
"cpu" : [ "x64", "ia32" ]
+
Like the os option, you can also blacklist architectures:
+
"cpu" : [ "!arm", "!mips" ]
+
The host architecture is determined by process.arch
+
preferGlobal
+
If your package is primarily a command-line application that should be
+installed globally, then set this value to true to provide a warning
+if it is installed locally.
+
It doesn't actually prevent users from installing it locally, but it
+does help prevent some confusion if it doesn't work as expected.
+
private
+
If you set "private": true in your package.json, then npm will refuse
+to publish it.
+
This is a way to prevent accidental publication of private repositories. If
+you would like to ensure that a given package is only ever published to a
+specific registry (for example, an internal registry), then use the
+publishConfig dictionary described below to override the registry config
+param at publish-time.
+
publishConfig
+
This is a set of config values that will be used at publish-time. It's
+especially handy if you want to set the tag or registry, so that you can
+ensure that a given package is not tagged with "latest" or published to
+the global public registry by default.
+
Any config values can be overridden, but of course only "tag" and
+"registry" probably matter for the purposes of publishing.
+
See npm-config(7) to see the list of config options that can be
+overridden.
+
DEFAULT VALUES
+
npm will default some values based on package contents.
+
+
"scripts": {"start": "node server.js"}
+
If there is a server.js file in the root of your package, then npm
+will default the start command to node server.js.
+
+
"scripts":{"preinstall": "node-gyp rebuild"}
+
If there is a binding.gyp file in the root of your package, npm will
+default the preinstall command to compile using node-gyp.
+
+
"contributors": [...]
+
If there is an AUTHORS file in the root of your package, npm will
+treat each line as a Name <email> (url) format, where email and url
+are optional. Lines which start with a # or are blank, will be
+ignored.
npm's coding style is a bit unconventional. It is not different for
+difference's sake, but rather a carefully crafted style that is
+designed to reduce visual clutter and make bugs more apparent.
+
If you want to contribute to npm (which is very encouraged), you should
+make your code conform to npm's style.
+
Note: this concerns npm's code not the specific packages at npmjs.org
+
Line Length
+
Keep lines shorter than 80 characters. It's better for lines to be
+too short than to be too long. Break up long lists, objects, and other
+statements onto multiple lines.
+
Indentation
+
Two-spaces. Tabs are better, but they look like hell in web browsers
+(and on github), and node uses 2 spaces, so that's that.
+
Configure your editor appropriately.
+
Curly braces
+
Curly braces belong on the same line as the thing that necessitates them.
+
Bad:
+
function ()
+{
+
Good:
+
function () {
+
If a block needs to wrap to the next line, use a curly brace. Don't
+use it if it doesn't.
+
Bad:
+
if (foo) { bar() }
+while (foo)
+ bar()
+
Good:
+
if (foo) bar()
+while (foo) {
+ bar()
+}
+
Semicolons
+
Don't use them except in four situations:
+
+
for (;;) loops. They're actually required.
+
null loops like: while (something) ; (But you'd better have a good
+reason for doing that.)
+
case "foo": doSomething(); break
+
In front of a leading ( or [ at the start of the line.
+This prevents the expression from being interpreted
+as a function call or property access, respectively.
+
+
Some examples of good semicolon usage:
+
;(x || y).doSomething()
+;[a, b, c].forEach(doSomething)
+for (var i = 0; i < 10; i ++) {
+ switch (state) {
+ case "begin": start(); continue
+ case "end": finish(); break
+ default: throw new Error("unknown state")
+ }
+ end()
+}
+
Note that starting lines with - and + also should be prefixed
+with a semicolon, but this is much less common.
+
Comma First
+
If there is a list of things separated by commas, and it wraps
+across multiple lines, put the comma at the start of the next
+line, directly below the token that starts the list. Put the
+final token in the list on a line by itself. For example:
Put a single space in front of ( for anything other than a function call.
+Also use a single space wherever it makes things more readable.
+
Don't leave trailing whitespace at the end of lines. Don't indent empty
+lines. Don't use more spaces than are helpful.
+
Functions
+
Use named functions. They make stack traces a lot easier to read.
+
Callbacks, Sync/async Style
+
Use the asynchronous/non-blocking versions of things as much as possible.
+It might make more sense for npm to use the synchronous fs APIs, but this
+way, the fs and http and child process stuff all uses the same callback-passing
+methodology.
+
The callback should always be the last argument in the list. Its first
+argument is the Error or null.
+
Be very careful never to ever ever throw anything. It's worse than useless.
+Just send the error message back as the first argument to the callback.
+
Errors
+
Always create a new Error object with your message. Don't just return a
+string message to the callback. Stack traces are handy.
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
+occurs.
+
Use appropriate log levels. See npm-config(7) and search for
+"loglevel".
+
Case, naming, etc.
+
Use lowerCamelCase for multiword identifiers when they refer to objects,
+functions, methods, properties, or anything not specified in this section.
+
Use UpperCamelCase for class names (things that you'd pass to "new").
+
Use all-lower-hyphen-css-case for multiword filenames and config keys.
+
Use named functions. They make stack traces easier to follow.
+
Use CAPS_SNAKE_CASE for constants, things that should never change
+and are rarely used.
+
Use a single uppercase letter for function names where the function
+would normally be anonymous, but needs to call itself recursively. It
+makes it clear that it's a "throwaway" function.
+
null, undefined, false, 0
+
Boolean variables and functions should always be either true or
+false. Don't set it to 0 unless it's supposed to be a number.
+
When something is intentionally missing or removed, set it to null.
+
Don't set things to undefined. Reserve that value to mean "not yet
+set to anything."
More than you probably want to know about npm configuration
+
DESCRIPTION
+
npm gets its configuration values from 6 sources, in this priority:
+
Command Line Flags
+
Putting --foo bar on the command line sets the foo configuration
+parameter to "bar". A -- argument tells the cli parser to stop
+reading flags. A --flag parameter that is at the end of the
+command will be given the value of true.
+
Environment Variables
+
Any environment variables that start with npm_config_ will be
+interpreted as a configuration parameter. For example, putting
+npm_config_foo=bar in your environment will set the foo
+configuration parameter to bar. Any environment configurations that
+are not given a value will be given the value of true. Config
+values are case-insensitive, so NPM_CONFIG_FOO=bar will work the
+same.
A set of configuration parameters that are internal to npm, and are
+defaults if nothing else is specified.
+
Shorthands and Other CLI Niceties
+
The following shorthands are parsed on the command-line:
+
+
-v: --version
+
-h, -?, --help, -H: --usage
+
-s, --silent: --loglevel silent
+
-q, --quiet: --loglevel warn
+
-d: --loglevel info
+
-dd, --verbose: --loglevel verbose
+
-ddd: --loglevel silly
+
-g: --global
+
-C: --prefix
+
-l: --long
+
-m: --message
+
-p, --porcelain: --parseable
+
-reg: --registry
+
-v: --version
+
-f: --force
+
-desc: --description
+
-S: --save
+
-D: --save-dev
+
-O: --save-optional
+
-B: --save-bundle
+
-E: --save-exact
+
-y: --yes
+
-n: --yes false
+
ll and la commands: ls --long
+
+
If the specified configuration param resolves unambiguously to a known
+configuration parameter, then it is expanded to that configuration
+parameter. For example:
+
npm ls --par
+# same as:
+npm ls --parseable
+
If multiple single-character shorthands are strung together, and the
+resulting combination is unambiguously not some other configuration
+param, then it is expanded to its various component pieces. For
+example:
+
npm ls -gpld
+# same as:
+npm ls --global --parseable --long --loglevel info
+
Per-Package Config Settings
+
When running scripts (see npm-scripts(7)) the package.json "config"
+keys are overwritten in the environment if there is a config param of
+<name>[@<version>]:<key>. For example, if the package.json has
+this:
Force npm to always require authentication when accessing the registry,
+even for GET requests.
+
bin-links
+
+
Default: true
+
Type: Boolean
+
+
Tells npm to create symlinks (or .cmd shims on Windows) for package
+executables.
+
Set to false to have it not do this. This can be used to work around
+the fact that some file systems don't support symlinks, even on
+ostensibly Unix systems.
+
browser
+
+
Default: OS X: "open", Windows: "start", Others: "xdg-open"
+
Type: String
+
+
The browser that is called by the npm docs command to open websites.
+
ca
+
+
Default: The npm CA certificate
+
Type: String or null
+
+
The Certificate Authority signing certificate that is trusted for SSL
+connections to the registry.
+
Set to null to only allow "known" registrars, or to a specific CA cert
+to trust only that specific signing authority.
+
See also the strict-ssl config.
+
cafile
+
+
Default: null
+
Type: path
+
+
A path to a file containing one or multiple Certificate Authority signing
+certificates. Similar to the ca setting, but allows for multiple CA's, as
+well as for the CA information to be stored in a file on disk.
The location of npm's cache directory. See npm-cache(1)
+
cache-lock-stale
+
+
Default: 60000 (1 minute)
+
Type: Number
+
+
The number of ms before cache folder lockfiles are considered stale.
+
cache-lock-retries
+
+
Default: 10
+
Type: Number
+
+
Number of times to retry to acquire a lock on cache folder lockfiles.
+
cache-lock-wait
+
+
Default: 10000 (10 seconds)
+
Type: Number
+
+
Number of ms to wait for cache lock files to expire.
+
cache-max
+
+
Default: Infinity
+
Type: Number
+
+
The maximum time (in seconds) to keep items in the registry cache before
+re-checking against the registry.
+
Note that no purging is done unless the npm cache clean command is
+explicitly used, and that only GET requests use the cache.
+
cache-min
+
+
Default: 10
+
Type: Number
+
+
The minimum time (in seconds) to keep items in the registry cache before
+re-checking against the registry.
+
Note that no purging is done unless the npm cache clean command is
+explicitly used, and that only GET requests use the cache.
+
cert
+
+
Default: null
+
Type: String
+
+
A client certificate to pass when accessing the registry.
+
color
+
+
Default: true on Posix, false on Windows
+
Type: Boolean or "always"
+
+
If false, never shows colors. If "always" then always shows colors.
+If true, then only prints color codes for tty file descriptors.
+
depth
+
+
Default: Infinity
+
Type: Number
+
+
The depth to go when recursing directories for npm ls and
+npm cache ls.
+
description
+
+
Default: true
+
Type: Boolean
+
+
Show the description in npm search
+
dev
+
+
Default: false
+
Type: Boolean
+
+
Install dev-dependencies along with packages.
+
Note that dev-dependencies are also installed if the npat flag is
+set.
+
editor
+
+
Default: EDITOR environment variable if set, or "vi" on Posix,
+or "notepad" on Windows.
+
Type: path
+
+
The command to run for npm edit or npm config edit.
+
engine-strict
+
+
Default: false
+
Type: Boolean
+
+
If set to true, then npm will stubbornly refuse to install (or even
+consider installing) any package that claims to not be compatible with
+the current Node.js version.
+
force
+
+
Default: false
+
Type: Boolean
+
+
Makes various commands more forceful.
+
+
lifecycle script failure does not block progress.
+
publishing clobbers previously published versions.
+
skips cache when requesting from the registry.
+
prevents checks against clobbering non-npm files.
+
+
fetch-retries
+
+
Default: 2
+
Type: Number
+
+
The "retries" config for the retry module to use when fetching
+packages from the registry.
+
fetch-retry-factor
+
+
Default: 10
+
Type: Number
+
+
The "factor" config for the retry module to use when fetching
+packages.
+
fetch-retry-mintimeout
+
+
Default: 10000 (10 seconds)
+
Type: Number
+
+
The "minTimeout" config for the retry module to use when fetching
+packages.
+
fetch-retry-maxtimeout
+
+
Default: 60000 (1 minute)
+
Type: Number
+
+
The "maxTimeout" config for the retry module to use when fetching
+packages.
+
git
+
+
Default: "git"
+
Type: String
+
+
The command to use for git commands. If git is installed on the
+computer, but is not in the PATH, then set this to the full path to
+the git binary.
+
git-tag-version
+
+
Default: true
+
Type: Boolean
+
+
Tag the commit when using the npm version command.
+
global
+
+
Default: false
+
Type: Boolean
+
+
Operates in "global" mode, so that packages are installed into the
+prefix folder instead of the current working directory. See
+npm-folders(5) for more on the differences in behavior.
+
+
packages are installed into the {prefix}/lib/node_modules folder, instead of the
+current working directory.
+
bin files are linked to {prefix}/bin
+
man pages are linked to {prefix}/share/man
+
+
globalconfig
+
+
Default: {prefix}/etc/npmrc
+
Type: path
+
+
The config file to read for global config options.
+
group
+
+
Default: GID of the current process
+
Type: String or Number
+
+
The group to use when running package scripts in global mode as the root
+user.
+
heading
+
+
Default: "npm"
+
Type: String
+
+
The string that starts all the debugging log output.
+
https-proxy
+
+
Default: the HTTPS_PROXY or https_proxy or HTTP_PROXY or
+http_proxy environment variables.
+
Type: url
+
+
A proxy to use for outgoing https requests.
+
ignore-scripts
+
+
Default: false
+
Type: Boolean
+
+
If true, npm does not run scripts specified in package.json files.
+
init-module
+
+
Default: ~/.npm-init.js
+
Type: path
+
+
A module that will be loaded by the npm init command. See the
+documentation for the
+init-package-json module
+for more information, or npm-init(1).
+
init-author-name
+
+
Default: ""
+
Type: String
+
+
The value npm init should use by default for the package author's name.
+
init-author-email
+
+
Default: ""
+
Type: String
+
+
The value npm init should use by default for the package author's email.
+
init-author-url
+
+
Default: ""
+
Type: String
+
+
The value npm init should use by default for the package author's homepage.
+
init-license
+
+
Default: "ISC"
+
Type: String
+
+
The value npm init should use by default for the package license.
+
init-version
+
+
Default: "0.0.0"
+
Type: semver
+
+
The value that npm init should use by default for the package
+version number, if not already set in package.json.
+
json
+
+
Default: false
+
Type: Boolean
+
+
Whether or not to output JSON data, rather than the normal output.
+
This feature is currently experimental, and the output data structures
+for many commands is either not implemented in JSON yet, or subject to
+change. Only the output from npm ls --json is currently valid.
+
key
+
+
Default: null
+
Type: String
+
+
A client key to pass when accessing the registry.
+
link
+
+
Default: false
+
Type: Boolean
+
+
If true, then local installs will link if there is a suitable globally
+installed package.
+
Note that this means that local installs can cause things to be
+installed into the global space at the same time. The link is only done
+if one of the two conditions are met:
+
+
The package is not already installed globally, or
+
the globally installed version is identical to the version that is
+being installed locally.
+
+
local-address
+
+
Default: undefined
+
Type: IP Address
+
+
The IP address of the local interface to use when making connections
+to the npm registry. Must be IPv4 in versions of Node prior to 0.12.
What level of logs to report. On failure, all logs are written to
+npm-debug.log in the current working directory.
+
Any logs of a higher level than the setting are shown.
+The default is "warn", which shows warn and error output.
+
logstream
+
+
Default: process.stderr
+
Type: Stream
+
+
This is the stream that is passed to the
+npmlog module at run time.
+
It cannot be set from the command line, but if you are using npm
+programmatically, you may wish to send logs to somewhere other than
+stderr.
+
If the color config is set to true, then this stream will receive
+colored output if it is a TTY.
+
long
+
+
Default: false
+
Type: Boolean
+
+
Show extended information in npm ls and npm search.
+
message
+
+
Default: "%s"
+
Type: String
+
+
Commit message which is used by npm version when creating version commit.
+
Any "%s" in the message will be replaced with the version number.
+
node-version
+
+
Default: process.version
+
Type: semver or false
+
+
The node version to use when checking a package's engines map.
+
npat
+
+
Default: false
+
Type: Boolean
+
+
Run tests on installation.
+
onload-script
+
+
Default: false
+
Type: path
+
+
A node module to require() when npm loads. Useful for programmatic
+usage.
+
optional
+
+
Default: true
+
Type: Boolean
+
+
Attempt to install packages in the optionalDependencies object. Note
+that if these packages fail to install, the overall installation
+process is not aborted.
+
parseable
+
+
Default: false
+
Type: Boolean
+
+
Output parseable results from commands that write to
+standard output.
The location to install global items. If set on the command line, then
+it forces non-global commands to run in the specified folder.
+
production
+
+
Default: false
+
Type: Boolean
+
+
Set to true to run in "production" mode.
+
+
devDependencies are not installed at the topmost level when running
+local npm install without any arguments.
+
Set the NODE_ENV="production" for lifecycle scripts.
+
+
proprietary-attribs
+
+
Default: true
+
Type: Boolean
+
+
Whether or not to include proprietary extended attributes in the
+tarballs created by npm.
+
Unless you are expecting to unpack package tarballs with something other
+than npm -- particularly a very outdated tar implementation -- leave
+this as true.
+
proxy
+
+
Default: HTTP_PROXY or http_proxy environment variable, or null
Save installed packages to a package.json file as dependencies.
+
When used with the npm rm command, it removes it from the dependencies
+object.
+
Only works if there is already a package.json file present.
+
save-bundle
+
+
Default: false
+
Type: Boolean
+
+
If a package would be saved at install time by the use of --save,
+--save-dev, or --save-optional, then also put it in the
+bundleDependencies list.
+
When used with the npm rm command, it removes it from the
+bundledDependencies list.
+
save-dev
+
+
Default: false
+
Type: Boolean
+
+
Save installed packages to a package.json file as devDependencies.
+
When used with the npm rm command, it removes it from the
+devDependencies object.
+
Only works if there is already a package.json file present.
+
save-exact
+
+
Default: false
+
Type: Boolean
+
+
Dependencies saved to package.json using --save, --save-dev or
+--save-optional will be configured with an exact version rather than
+using npm's default semver range operator.
+
save-optional
+
+
Default: false
+
Type: Boolean
+
+
Save installed packages to a package.json file as
+optionalDependencies.
+
When used with the npm rm command, it removes it from the
+devDependencies object.
+
Only works if there is already a package.json file present.
+
save-prefix
+
+
Default: '^'
+
Type: String
+
+
Configure how versions of packages installed to a package.json file via
+--save or --save-dev get prefixed.
+
For example if a package has version 1.2.3, by default it's version is
+set to ^1.2.3 which allows minor upgrades for that package, but after
+npm config set save-prefix='~' it would be set to ~1.2.3 which only allows
+patch upgrades.
+
scope
+
+
Default: ""
+
Type: String
+
+
Associate an operation with a scope for a scoped registry. Useful when logging
+in to a private registry for the first time:
+npm login --scope=@organization --registry=registry.organization.com, which
+will cause @organization to be mapped to the registry for future installation
+of packages specified according to the pattern @organization/package.
+
searchopts
+
+
Default: ""
+
Type: String
+
+
Space-separated options that are always passed to search.
+
searchexclude
+
+
Default: ""
+
Type: String
+
+
Space-separated options that limit the results from search.
Indication of which field to sort search results by. Prefix with a -
+character to indicate reverse sort.
+
shell
+
+
Default: SHELL environment variable, or "bash" on Posix, or "cmd" on
+Windows
+
Type: path
+
+
The shell to run for the npm explore command.
+
shrinkwrap
+
+
Default: true
+
Type: Boolean
+
+
If set to false, then ignore npm-shrinkwrap.json files when
+installing.
+
sign-git-tag
+
+
Default: false
+
Type: Boolean
+
+
If set to true, then the npm version command will tag the version
+using -s to add a signature.
+
Note that git requires you to have set up GPG keys in your git configs
+for this to work properly.
+
spin
+
+
Default: true
+
Type: Boolean or "always"
+
+
When set to true, npm will display an ascii spinner while it is doing
+things, if process.stderr is a TTY.
+
Set to false to suppress the spinner, or set to always to output
+the spinner even for non-TTY outputs.
+
strict-ssl
+
+
Default: true
+
Type: Boolean
+
+
Whether or not to do SSL key validation when making requests to the
+registry via https.
+
See also the ca config.
+
tag
+
+
Default: latest
+
Type: String
+
+
If you ask npm to install a package and don't tell it a specific version, then
+it will install the specified tag.
+
Also the tag that is added to the package@version specified by the npm
+tag command, if no explicit tag is given.
+
tmp
+
+
Default: TMPDIR environment variable, or "/tmp"
+
Type: path
+
+
Where to store temporary files and folders. All temp files are deleted
+on success, but left behind on failure for forensic purposes.
+
unicode
+
+
Default: true
+
Type: Boolean
+
+
When set to true, npm uses unicode characters in the tree output. When
+false, it uses ascii characters to draw trees.
+
unsafe-perm
+
+
Default: false if running as root, true otherwise
+
Type: Boolean
+
+
Set to true to suppress the UID/GID switching when running package
+scripts. If set explicitly to false, then installing as a non-root user
+will fail.
+
usage
+
+
Default: false
+
Type: Boolean
+
+
Set to show short usage output (like the -H output)
+instead of complete help when doing npm-help(1).
+
user
+
+
Default: "nobody"
+
Type: String or Number
+
+
The UID to set to when running package scripts as root.
+
userconfig
+
+
Default: ~/.npmrc
+
Type: path
+
+
The location of user-level configuration settings.
+
umask
+
+
Default: 022
+
Type: Octal numeric string
+
+
The "umask" value to use when setting the file creation mode on files
+and folders.
+
Folders and executables are given a mode which is 0777 masked against
+this value. Other files are given a mode which is 0666 masked against
+this value. Thus, the defaults are 0755 and 0644 respectively.
So, you've decided to use npm to develop (and maybe publish/deploy)
+your project.
+
Fantastic!
+
There are a few things that you need to do above the simple steps
+that your users will do to install your program.
+
About These Documents
+
These are man pages. If you install npm, you should be able to
+then do man npm-thing to get the documentation on a particular
+topic, or npm help thing to see the same information.
+
What is a package
+
A package is:
+
+
a) a folder containing a program described by a package.json file
+
b) a gzipped tarball containing (a)
+
c) a url that resolves to (b)
+
d) a <name>@<version> that is published on the registry with (c)
+
e) a <name>@<tag> that points to (d)
+
f) a <name> that has a "latest" tag satisfying (e)
+
g) a git url that, when cloned, results in (a).
+
+
Even if you never publish your package, you can still get a lot of
+benefits of using npm if you just want to write a node program (a), and
+perhaps if you also want to be able to easily install it elsewhere
+after packing it up into a tarball (b).
The commit-ish can be any tag, sha, or branch which can be supplied as
+an argument to git checkout. The default is master.
+
The package.json File
+
You need to have a package.json file in the root of your project to do
+much of anything with npm. That is basically the whole interface.
+
See package.json(5) for details about what goes in that file. At the very
+least, you need:
+
+
name:
+This should be a string that identifies your project. Please do not
+use the name to specify that it runs on node, or is in JavaScript.
+You can use the "engines" field to explicitly state the versions of
+node (or whatever else) that your program requires, and it's pretty
+well assumed that it's javascript.
+
It does not necessarily need to match your github repository name.
+
So, node-foo and bar-js are bad names. foo or bar are better.
+
+
version:
+A semver-compatible version.
+
+
engines:
+Specify the versions of node (or whatever else) that your program
+runs on. The node API changes a lot, and there may be bugs or new
+functionality that you depend on. Be explicit.
+
+
author:
+Take some credit.
+
+
scripts:
+If you have a special compilation or installation script, then you
+should put it in the scripts object. You should definitely have at
+least a basic smoke-test command as the "scripts.test" field.
+See npm-scripts(7).
+
+
main:
+If you have a single module that serves as the entry point to your
+program (like what the "foo" package gives you at require("foo")),
+then you need to specify that in the "main" field.
+
+
directories:
+This is an object mapping names to folders. The best ones to include are
+"lib" and "doc", but if you use "man" to specify a folder full of man pages,
+they'll get installed just like these ones.
+
+
+
You can use npm init in the root of your package in order to get you
+started with a pretty basic package.json file. See npm-init(1) for
+more info.
+
Keeping files out of your package
+
Use a .npmignore file to keep stuff out of your package. If there's
+no .npmignore file, but there is a .gitignore file, then npm will
+ignore the stuff matched by the .gitignore file. If you want to
+include something that is excluded by your .gitignore file, you can
+create an empty .npmignore file to override it.
+
By default, the following paths and files are ignored, so there's no
+need to add them to .npmignore explicitly:
+
+
.*.swp
+
._*
+
.DS_Store
+
.git
+
.hg
+
.lock-wscript
+
.svn
+
.wafpickle-*
+
CVS
+
npm-debug.log
+
+
Additionally, everything in node_modules is ignored, except for
+bundled dependencies. npm automatically handles this for you, so don't
+bother adding node_modules to .npmignore.
+
The following paths and files are never ignored, so adding them to
+.npmignore is pointless:
npm link is designed to install a development package and see the
+changes in real time without having to keep re-installing it. (You do
+need to either re-link or npm rebuild -g to update compiled packages,
+of course.)
Before Publishing: Make Sure Your Package Installs and Works
+
This is important.
+
If you can not install it locally, you'll have
+problems trying to publish it. Or, worse yet, you'll be able to
+publish it, but you'll be publishing a broken or pointless package.
+So don't do that.
+
In the root of your package, do this:
+
npm install . -g
+
That'll show you that it's working. If you'd rather just create a symlink
+package that points to your working directory, then do this:
+
npm link
+
Use npm ls -g to see if it's there.
+
To test a local install, go into some other folder, and then do:
+
cd ../some-other-folder
+npm install ../my-package
+
to install it locally into the node_modules folder in that other place.
+
Then go into the node-repl, and try using require("my-thing") to
+bring in your module's main module.
+
Create a User Account
+
Create a user with the adduser command. It works like this:
This part's easy. IN the root of your folder, do this:
+
npm publish
+
You can give publish a url to a tarball, or a filename of a tarball,
+or a path to a folder.
+
Note that pretty much everything in that folder will be exposed
+by default. So, if you have secret stuff in there, use a
+.npmignore file to list out the globs to ignore, or publish
+from a fresh checkout.
+
Brag about it
+
Send emails, write blogs, blab in IRC.
+
Tell the world how easy it is to install your program!
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.
+
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.)
+
+
Joe writes a JavaScript module foo, which is not node-specific.
+Joe doesn't use node at all. Bob wants to use foo in node, so he
+wraps it in an npm module. Some time later, Joe starts using node,
+and wants to take over management of his program.
+
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.
+
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.
+
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.
+
+
npm owner ls foo. This will tell Joe the email address of the
+owner (Bob).
+
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 support@npmjs.com 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.
+
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 support
+support@npmjs.com and we'll sort it out. ("Reasonable" is
+usually at least 4 weeks, but extra time is allowed around common
+holidays.)
+
+
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:
+
+
Malware (that is, a package designed to exploit or harm the machine on
+which it is installed).
+
Violations of copyright or licenses (for example, cloning an
+MIT-licensed program, and then removing or changing the copyright and
+license statement).
+
Illegal content.
+
"Squatting" on a package name that you plan to use, but aren't
+actually using. Sorry, I don't care how great the name is, or how
+perfect a fit it is for the thing that someday might happen. If
+someone wants to use it today, and you're just taking up space with
+an empty tarball, you're going to be evicted.
+
Putting empty packages in the registry. Packages must have SOME
+functionality. It can be silly, but it can't be nothing. (See
+also: squatting.)
+
Doing weird things with the registry, like using it as your own
+personal application database or otherwise putting non-packagey
+things into it.
+
+
If you see bad behavior like this, please report it right away.
Use the npm root command to see where modules go, and the npm bin
+command to see where executables go
+
Global installs are different from local installs. If you install
+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 on my computer in a central location?
+
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.
+
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().
+
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.
+
Why can't npm just put everything in one place, like other package managers?
+
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.
+
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(5) for
+more details.
+
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.
+
Whatever, I really want the old style 'everything global' style.
+
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.
+
Should I check my node_modules folder into git?
+
Usually, no. Allow npm to resolve dependencies for your packages.
+
For packages you deploy, such as websites and apps,
+you should use npm shrinkwrap to lock down your full dependency tree:
If you are paranoid about depending on the npm ecosystem,
+you should run a private npm mirror or a private cache.
+
If you want 100% confidence in being able to reproduce the specific bytes
+included in a deployment, you should use an additional mechanism that can
+verify contents rather than versions. For example,
+Amazon machine images, DigitalOcean snapshots, Heroku slugs, or simple tarballs.
+
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?
+
Contrary to the belief of many, "npm" is not in fact an abbreviation for
+"Node Package Manager". It is a recursive bacronymic abbreviation for
+"npm is not an acronym". (If it was "ninaa", then it would be an
+acronym, and thus incorrectly named.)
+
"NPM", however, is an acronym (more precisely, a capitonym) for the
+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
+Chris Rorden. You can analyze pictures of brains with it. Learn more
+about the (capitalized) NPM program at http://www.cabiatl.com/mricro/npm/.
+
The first seed that eventually grew into this flower was a bash utility
+named "pm", which was a shortened descendent of "pkgmakeinst", a
+bash function that was used to install various different things on different
+platforms, most often using Yahoo's yinst. If npm was ever an
+acronym for anything, it was node pm or maybe new pm.
+
So, in all seriousness, the "npm" project is named after its command-line
+utility, which was organically selected to be easily typed by a right-handed
+programmer using a US QWERTY keyboard layout, ending with the
+right-ring-finger in a postition to type the - key for flags and
+other command-line arguments. That command-line utility is always
+lower-case, though it starts most sentences it is a part of.
+
How do I list installed packages?
+
npm ls
+
How do I search for packages?
+
npm search
+
Arguments are greps. npm search jsdom shows jsdom packages.
+
How do I update npm?
+
npm install npm -g
+
You can also update all outdated local packages by doing npm update without
+any arguments, or global packages by doing npm update -g.
+
Occasionally, the version of npm will progress such that the current
+version cannot be properly installed with the version that you have
+installed already. (Consider, if there is ever a bug in the update
+command.)
+
In those cases, you can do this:
+
curl https://www.npmjs.org/install.sh | sh
+
What is a package?
+
A package is:
+
+
a) a folder containing a program described by a package.json file
+
b) a gzipped tarball containing (a)
+
c) a url that resolves to (b)
+
d) a <name>@<version> that is published on the registry with (c)
+
e) a <name>@<tag> that points to (d)
+
f) a <name> that has a "latest" tag satisfying (e)
+
g) a git url that, when cloned, results in (a).
+
+
Even if you never publish your package, you can still get a lot of
+benefits of using npm if you just want to write a node program (a), and
+perhaps if you also want to be able to easily install it elsewhere
+after packing it up into a tarball (b).
The commit-ish can be any tag, sha, or branch which can be supplied as
+an argument to git checkout. The default is master.
+
What is a module?
+
A module is anything that can be loaded with require() in a Node.js
+program. The following things are all examples of things that can be
+loaded as modules:
+
+
A folder with a package.json file containing a main field.
+
A folder with an index.js file in it.
+
A JavaScript file.
+
+
Most npm packages are modules, because they are libraries that you
+load with require. However, there's no requirement that an npm
+package be a module! Some only contain an executable command-line
+interface, and don't provide a main field for use in Node programs.
+
Almost all npm packages (at least, those that are Node programs)
+contain many modules within them (because every file they load with
+require() is a module).
+
In the context of a Node program, the module is also the thing that
+was loaded from a file. For example, in the following program:
+
var req = require('request')
+
we might say that "The variable req refers to the request module".
+
So, why is it the "node_modules" folder, but "package.json" file? Why not node_packages or module.json?
+
The package.json file defines the package. (See "What is a
+package?" above.)
+
The node_modules folder is the place Node.js looks for modules.
+(See "What is a module?" above.)
+
For example, if you create a file at node_modules/foo.js and then
+had a program that did var f = require('foo.js') then it would load
+the module. However, foo.js is not a "package" in this case,
+because it does not have a package.json.
+
Alternatively, if you create a package which does not have an
+index.js or a "main" field in the package.json file, then it is
+not a module. Even if it's installed in node_modules, it can't be
+an argument to require().
+
"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 big
+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 #4.
+
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.
+
How do I install node with npm?
+
You don't. Try one of these node version managers:
You'll most likely want to npm link your development folder. That's
+awesomely handy.
+
To set up your own private registry, check out npm-registry(7).
+
Can I list a url as a dependency?
+
Yes. It should be a url to a gzipped tarball containing a single folder
+that has a package.json in its root, or a git url.
+(See "what is a package?" above.)
+
How do I symlink to a dev folder so I don't have to keep re-installing?
Either the registry is down, or node's DNS isn't able to reach out.
+
To check if the registry is down, open up
+https://registry.npmjs.org/ 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 us know by emailing support@npmjs.com
+or posting an issue at https://github.com/npm/npm/issues. 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.
tl;dr - It doesn't actually make things better, and can make them worse.
+
If you want to namespace your own packages, you may: simply use the
+- character to separate the names. npm is a mostly anarchic system.
+There is not sufficient need to impose namespace rules on everyone.
+
Who does npm?
+
npm was originally written by Isaac Z. Schlueter, and many others have
+contributed to it, some of them quite substantially.
+
The npm open source project, The npm Registry, and the community
+website are maintained and operated by the
+good folks at npm, Inc.
+
I have a question or request not addressed here. Where should I put it?
To resolve packages by name and version, npm talks to a registry website
+that implements the CommonJS Package Registry specification for reading
+package info.
+
Additionally, npm's package registry implementation supports several
+write APIs as well, to allow for publishing packages and managing user
+account information.
The registry URL used is determined by the scope of the package (see
+npm-scope(7)). If no scope is specified, the default registry is used, which is
+supplied by the registry config parameter. See npm-config(1),
+npmrc(5), and npm-config(7) for more on managing npm's configuration.
+
Can I run my own private registry?
+
Yes!
+
The easiest way is to replicate the couch database, and use the same (or
+similar) design doc to implement the APIs.
+
If you set up continuous replication from the official CouchDB, and then
+set your internal CouchDB as the registry config, then you'll be able
+to read any published packages, in addition to your private ones, and by
+default will only publish internally. If you then want to publish a
+package for the whole world to see, you can simply override the
+--registry config for that command.
+
I don't want my package published in the official registry. It's private.
+
Set "private": true in your package.json to prevent it from being
+published at all, or
+"publishConfig":{"registry":"http://my-internal-registry.local"}
+to force it to be published only to your internal registry.
+
See package.json(5) for more info on what goes in the package.json file.
+
Will you replicate from my registry into the public one?
+
No. If you want things to be public, then publish them into the public
+registry using npm. What little security there is would be for nought
+otherwise.
+
Do I have to use couchdb to build a registry that npm can talk to?
+
No, but it's way easier. Basically, yes, you do, or you have to
+effectively implement the entire CouchDB API anyway.
+
Is there a website or something to see package docs and such?
All npm packages have a name. Some package names also have a scope. A scope
+follows the usual rules for package names (url-safe characters, no leading dots
+or underscores). When used in package names, preceded by an @-symbol and
+followed by a slash, e.g.
+
@somescope/somepackagename
+
Scopes are a way of grouping related packages together, and also affect a few
+things about the way npm treats the package.
+
As of 2014-09-03, scoped packages are not supported by the public npm registry.
+However, the npm client is backwards-compatible with un-scoped registries, so
+it can be used to work with scoped and un-scoped registries at the same time.
+
Installing scoped packages
+
Scoped packages are installed to a sub-folder of the regular installation
+folder, e.g. if your other packages are installed in node_modules/packagename,
+scoped modules will be in node_modules/@myorg/packagename. The scope folder
+(@myorg) is simply the name of the scope preceded by an @-symbol, and can
+contain any number of scoped packages.
+
A scoped package is installed by referencing it by name, preceded by an
+@-symbol, in npm install:
Note that if the @-symbol is omitted in either case npm will instead attempt to
+install from GitHub; see npm-install(1).
+
Requiring scoped packages
+
Because scoped packages are installed into a scope folder, you have to
+include the name of the scope when requiring them in your code, e.g.
+
require('@myorg/mypackage')
+
There is nothing special about the way Node treats scope folders, this is
+just specifying to require the module mypackage in the folder called @myorg.
+
Publishing scoped packages
+
Scoped packages can be published to any registry that supports them.
+As of 2014-09-03, the public npm registry does not support scoped packages,
+so attempting to publish a scoped package to the registry will fail unless
+you have associated that scope with a different registry, see below.
+
Associating a scope with a registry
+
Scopes can be associated with a separate registry. This allows you to
+seamlessly use a mix of packages from the public npm registry and one or more
+private registries, such as npm Enterprise.
+
You can associate a scope with a registry at login, e.g.
Scopes have a many-to-one relationship with registries: one registry can
+host multiple scopes, but a scope only ever points to one registry.
+
You can also associate a scope with a registry using npm config:
+
npm config set @myco:registry http://reg.example.com
+
Once a scope is associated with a registry, any npm install for a package
+with that scope will request packages from that registry instead. Any
+npm publish for a package name that contains the scope will be published to
+that registry instead.
npm supports the "scripts" property of the package.json script, for the
+following scripts:
+
+
prepublish:
+Run BEFORE the package is published. (Also run on local npm
+install without any arguments.)
+
publish, postpublish:
+Run AFTER the package is published.
+
preinstall:
+Run BEFORE the package is installed
+
install, postinstall:
+Run AFTER the package is installed.
+
preuninstall, uninstall:
+Run BEFORE the package is uninstalled.
+
postuninstall:
+Run AFTER the package is uninstalled.
+
preupdate:
+Run BEFORE the package is updated with the update command.
+
update, postupdate:
+Run AFTER the package is updated with the update command.
+
pretest, test, posttest:
+Run by the npm test command.
+
prestop, stop, poststop:
+Run by the npm stop command.
+
prestart, start, poststart:
+Run by the npm start command.
+
prerestart, restart, postrestart:
+Run by the npm restart command. Note: npm restart will run the
+stop and start scripts if no restart script is provided.
+
+
Additionally, arbitrary scripts can be executed by running npm
+run-script <pkg> <stage>. Pre and post commands with matching
+names will be run for those as well (e.g. premyscript, myscript,
+postmyscript).
+
NOTE: INSTALL SCRIPTS ARE AN ANTIPATTERN
+
tl;dr Don't use install. Use a .gyp file for compilation, and
+prepublish for anything else.
+
You should almost never have to explicitly set a preinstall or
+install script. If you are doing this, please consider if there is
+another option.
+
The only valid use of install or preinstall scripts is for
+compilation which must be done on the target architecture. In early
+versions of node, this was often done using the node-waf scripts, or
+a standalone Makefile, and early versions of npm required that it be
+explicitly set in package.json. This was not portable, and harder to
+do properly.
+
In the current version of node, the standard way to do this is using a
+.gyp file. If you have a file with a .gyp extension in the root
+of your package, then npm will run the appropriate node-gyp commands
+automatically at install time. This is the only officially supported
+method for compiling binary addons, and does not require that you add
+anything to your package.json file.
+
If you have to do other things before your package is used, in a way
+that is not dependent on the operating system or architecture of the
+target system, then use a prepublish script instead. This includes
+tasks such as:
+
+
Compile CoffeeScript source code into JavaScript.
+
Create minified versions of JavaScript source code.
+
Fetching remote resources that your package will use.
+
+
The advantage of doing these things at prepublish time instead of
+preinstall or install time is that they can be done once, in a
+single place, and thus greatly reduce complexity and variability.
+Additionally, this means that:
+
+
You can depend on coffee-script as a devDependency, and thus
+your users don't need to have it installed.
+
You don't need to include the minifiers in your package, reducing
+the size for your users.
+
You don't need to rely on your users having curl or wget or
+other system tools on the target machines.
+
+
DEFAULT VALUES
+
npm will default some script values based on package contents.
+
+
"start": "node server.js":
+
If there is a server.js file in the root of your package, then npm
+will default the start command to node server.js.
If there is a wscript file in the root of your package, npm will
+default the preinstall command to compile using node-waf.
+
+
+
USER
+
If npm was invoked with root privileges, then it will change the uid
+to the user account or uid specified by the user config, which
+defaults to nobody. Set the unsafe-perm flag to run scripts with
+root privileges.
+
ENVIRONMENT
+
Package scripts run in an environment where many pieces of information
+are made available regarding the setup of npm and the current state of
+the process.
+
path
+
If you depend on modules that define executable scripts, like test
+suites, then those executables will be added to the PATH for
+executing the scripts. So, if your package.json has this:
then you could run npm start to execute the bar script, which is
+exported into the node_modules/.bin directory on npm install.
+
package.json vars
+
The package.json fields are tacked onto the npm_package_ prefix. So,
+for instance, if you had {"name":"foo", "version":"1.2.5"} in your
+package.json file, then your package scripts would have the
+npm_package_name environment variable set to "foo", and the
+npm_package_version set to "1.2.5"
+
configuration
+
Configuration parameters are put in the environment with the
+npm_config_ prefix. For instance, you can view the effective root
+config by checking the npm_config_root environment variable.
+
Special: package.json "config" object
+
The package.json "config" keys are overwritten in the environment if
+there is a config param of <name>[@<version>]:<key>. For example,
+if the package.json has this:
Lastly, the npm_lifecycle_event environment variable is set to
+whichever stage of the cycle is being executed. So, you could have a
+single script used for different parts of the process which switches
+based on what's currently happening.
+
Objects are flattened following this format, so if you had
+{"scripts":{"install":"foo.js"}} in your package.json, then you'd
+see this in the script:
then the scripts/install.js will be called for the install,
+post-install, stages of the lifecycle, and the scripts/uninstall.js
+would be called when the package is uninstalled. Since
+scripts/install.js is running for three different phases, it would
+be wise in this case to look at the npm_lifecycle_event environment
+variable.
+
If you want to run a make command, you can do so. This works just
+fine:
Scripts are run by passing the line as a script argument to sh.
+
If the script exits with a code other than 0, then this will abort the
+process.
+
Note that these script files don't have to be nodejs or even
+javascript programs. They just have to be some kind of executable
+file.
+
HOOK SCRIPTS
+
If you want to run a specific script at a specific lifecycle event for
+ALL packages, then you can use a hook script.
+
Place an executable file at node_modules/.hooks/{eventname}, and
+it'll get run for all packages when they are going through that point
+in the package lifecycle for any packages installed in that root.
+
Hook scripts are run exactly the same way as package.json scripts.
+That is, they are in a separate child process, with the env described
+above.
+
BEST PRACTICES
+
+
Don't exit with a non-zero error code unless you really mean it.
+Except for uninstall scripts, this will cause the npm action to
+fail, and potentially be rolled back. If the failure is minor or
+only will prevent some optional features, then it's better to just
+print a warning and exit successfully.
+
Try not to use scripts to do what npm can do for you. Read through
+package.json(5) to see all the things that you can specify and enable
+by simply describing your package appropriately. In general, this
+will lead to a more robust and consistent state.
+
Inspect the env to determine where to put things. For instance, if
+the npm_config_binroot environ is set to /home/user/bin, then
+don't try to install executables into /usr/local/bin. The user
+probably set it up that way for a reason.
+
Don't prefix your script commands with "sudo". If root permissions
+are required for some reason, then it'll fail with that error, and
+the user will sudo the npm command in question.
Or, if that fails, get the npm source code, and do:
+
sudo make uninstall
+
More Severe Uninstalling
+
Usually, the above instructions are sufficient. That will remove
+npm, but leave behind anything you've installed.
+
If that doesn't work, or if you require more drastic measures,
+continue reading.
+
Note that this is only necessary for globally-installed packages. Local
+installs are completely contained within a project's node_modules
+folder. Delete that folder, and everything is gone (unless a package's
+install script is particularly ill-behaved).
+
This assumes that you installed node and npm in the default place. If
+you configured node with a different --prefix, or installed npm with a
+different prefix setting, then adjust the paths accordingly, replacing
+/usr/local with your install prefix.
If you installed things with npm, then your best bet is to uninstall
+them with npm first, and then install them again once you have a
+proper install. This can help find any symlinks that are lying
+around:
+
ls -laF /usr/local/{lib/node{,/.npm},bin,share/man} | grep npm
+
Prior to version 0.3, npm used shim files for executables and node
+modules. To track those down, you can do the following:
$ semver -h
+
+Usage: semver <version> [<version> [...]] [-r <range> | -i <inc> | -d <dec>]
+Test if version(s) satisfy the supplied range(s), and sort them.
+
+Multiple versions or ranges may be supplied, unless increment
+or decrement options are specified. In that case, only a single
+version may be used, and it is incremented by the specified level
+
+Program exits successfully if any valid version satisfies
+all supplied ranges, and prints all satisfying versions.
+
+If no versions are valid, or ranges are not satisfied,
+then exits failure.
+
+Versions are printed in ascending order, so supplying
+multiple versions to the utility will just sort them.
+
Versions
+
A "version" is described by the v2.0.0 specification found at
+http://semver.org/.
+
A leading "=" or "v" character is stripped off and ignored.
+
Ranges
+
A version range is a set of comparators which specify versions
+that satisfy the range.
+
A comparator is composed of an operator and a version. The set
+of primitive operators is:
+
+
< Less than
+
<= Less than or equal to
+
> Greater than
+
>= Greater than or equal to
+
= Equal. If no operator is specified, then equality is assumed,
+so this operator is optional, but MAY be included.
+
+
For example, the comparator >=1.2.7 would match the versions
+1.2.7, 1.2.8, 2.5.3, and 1.3.9, but not the versions 1.2.6
+or 1.1.0.
+
Comparators can be joined by whitespace to form a comparator set,
+which is satisfied by the intersection of all of the comparators
+it includes.
+
A range is composed of one or more comparator sets, joined by ||. A
+version matches a range if and only if every comparator in at least
+one of the ||-separated comparator sets is satisfied by the version.
+
For example, the range >=1.2.7 <1.3.0 would match the versions
+1.2.7, 1.2.8, and 1.2.99, but not the versions 1.2.6, 1.3.0,
+or 1.1.0.
+
The range 1.2.7 || >=1.2.9 <2.0.0 would match the versions 1.2.7,
+1.2.9, and 1.4.6, but not the versions 1.2.8 or 2.0.0.
+
Prerelease Tags
+
If a version has a prerelease tag (for example, 1.2.3-alpha.3) then
+it will only be allowed to satisfy comparator sets if at least one
+comparator with the same [major, minor, patch] tuple also has a
+prerelease tag.
+
For example, the range >1.2.3-alpha.3 would be allowed to match the
+version 1.2.3-alpha.7, but it would not be satisfied by
+3.4.5-alpha.9, even though 3.4.5-alpha.9 is technically "greater
+than" 1.2.3-alpha.3 according to the SemVer sort rules. The version
+range only accepts prerelease tags on the 1.2.3 version. The
+version 3.4.5would satisfy the range, because it does not have a
+prerelease flag, and 3.4.5 is greater than 1.2.3-alpha.7.
+
The purpose for this behavior is twofold. First, prerelease versions
+frequently are updated very quickly, and contain many breaking changes
+that are (by the author's design) not yet fit for public consumption.
+Therefore, by default, they are excluded from range matching
+semantics.
+
Second, a user who has opted into using a prerelease version has
+clearly indicated the intent to use that specific set of
+alpha/beta/rc versions. By including a prerelease tag in the range,
+the user is indicating that they are aware of the risk. However, it
+is still not appropriate to assume that they have opted into taking a
+similar risk on the next set of prerelease versions.
+
Advanced Range Syntax
+
Advanced range syntax desugars to primitive comparators in
+deterministic ways.
+
Advanced ranges may be combined in the same way as primitive
+comparators using white space or ||.
+
Hyphen Ranges X.Y.Z - A.B.C
+
Specifies an inclusive set.
+
+
1.2.3 - 2.3.4 := >=1.2.3 <=2.3.4
+
+
If a partial version is provided as the first version in the inclusive
+range, then the missing pieces are replaced with zeroes.
+
+
1.2 - 2.3.4 := >=1.2.0 <=2.3.4
+
+
If a partial version is provided as the second version in the
+inclusive range, then all versions that start with the supplied parts
+of the tuple are accepted, but nothing that would be greater than the
+provided tuple parts.
+
+
1.2.3 - 2.3 := >=1.2.3 <2.4.0
+
1.2.3 - 2 := >=1.2.3 <3.0.0
+
+
X-Ranges 1.2.x1.X1.2.**
+
Any of X, x, or * may be used to "stand in" for one of the
+numeric values in the [major, minor, patch] tuple.
+
+
* := >=0.0.0 (Any version satisfies)
+
1.x := >=1.0.0 <2.0.0 (Matching major version)
+
1.2.x := >=1.2.0 <1.3.0 (Matching major and minor versions)
+
+
A partial version range is treated as an X-Range, so the special
+character is in fact optional.
+
+
"" (empty string) := * := >=0.0.0
+
1 := 1.x.x := >=1.0.0 <2.0.0
+
1.2 := 1.2.x := >=1.2.0 <1.3.0
+
+
Tilde Ranges ~1.2.3~1.2~1
+
Allows patch-level changes if a minor version is specified on the
+comparator. Allows minor-level changes if not.
+
+
~1.2.3 := >=1.2.3 <1.(2+1).0 := >=1.2.3 <1.3.0
+
~1.2 := >=1.2.0 <1.(2+1).0 := >=1.2.0 <1.3.0 (Same as 1.2.x)
+
~1 := >=1.0.0 <(1+1).0.0 := >=1.0.0 <2.0.0 (Same as 1.x)
+
~0.2.3 := >=0.2.3 <0.(2+1).0 := >=0.2.3 <0.3.0
+
~0.2 := >=0.2.0 <0.(2+1).0 := >=0.2.0 <0.3.0 (Same as 0.2.x)
+
~0 := >=0.0.0 <(0+1).0.0 := >=0.0.0 <1.0.0 (Same as 0.x)
+
~1.2.3-beta.2 := >=1.2.3-beta.2 <1.3.0 Note that prereleases in
+the 1.2.3 version will be allowed, if they are greater than or
+equal to beta.2. So, 1.2.3-beta.4 would be allowed, but
+1.2.4-beta.2 would not, because it is a prerelease of a
+different [major, minor, patch] tuple.
+
+
Note: this is the same as the ~> operator in rubygems.
+
Caret Ranges ^1.2.3^0.2.5^0.0.4
+
Allows changes that do not modify the left-most non-zero digit in the
+[major, minor, patch] tuple. In other words, this allows patch and
+minor updates for versions 1.0.0 and above, patch updates for
+versions 0.X >=0.1.0, and no updates for versions 0.0.X.
+
Many authors treat a 0.x version as if the x were the major
+"breaking-change" indicator.
+
Caret ranges are ideal when an author may make breaking changes
+between 0.2.4 and 0.3.0 releases, which is a common practice.
+However, it presumes that there will not be breaking changes between
+0.2.4 and 0.2.5. It allows for changes that are presumed to be
+additive (but non-breaking), according to commonly observed practices.
+
+
^1.2.3 := >=1.2.3 <2.0.0
+
^0.2.3 := >=0.2.3 <0.3.0
+
^0.0.3 := >=0.0.3 <0.0.4
+
^1.2.3-beta.2 := >=1.2.3-beta.2 <2.0.0 Note that prereleases in
+the 1.2.3 version will be allowed, if they are greater than or
+equal to beta.2. So, 1.2.3-beta.4 would be allowed, but
+1.2.4-beta.2 would not, because it is a prerelease of a
+different [major, minor, patch] tuple.
+
^0.0.3-beta := >=0.0.3-beta <0.0.4 Note that prereleases in the
+0.0.3 version only will be allowed, if they are greater than or
+equal to beta. So, 0.0.3-pr.2 would be allowed.
+
+
When parsing caret ranges, a missing patch value desugars to the
+number 0, but will allow flexibility within that value, even if the
+major and minor versions are both 0.
+
+
^1.2.x := >=1.2.0 <2.0.0
+
^0.0.x := >=0.0.0 <0.1.0
+
^0.0 := >=0.0.0 <0.1.0
+
+
A missing minor and patch values will desugar to zero, but also
+allow flexibility within those values, even if the major version is
+zero.
+
+
^1.x := >=1.0.0 <2.0.0
+
^0.x := >=0.0.0 <1.0.0
+
+
Functions
+
All methods and classes take a final loose boolean argument that, if
+true, will be more forgiving about not-quite-valid semver strings.
+The resulting output will always be 100% strict, of course.
+
Strict-mode Comparators and Ranges will be strict about the SemVer
+strings that they parse.
+
+
valid(v): Return the parsed version, or null if it's not valid.
+
inc(v, release): Return the version incremented by the release
+type (major, premajor, minor, preminor, patch,
+prepatch, or prerelease), or null if it's not valid
+
premajor in one call will bump the version up to the next major
+version and down to a prerelease of that major version.
+preminor, and prepatch work the same way.
+
If called from a non-prerelease version, the prerelease will work the
+same as prepatch. It increments the patch version, then makes a
+prerelease. If the input version is already a prerelease it simply
+increments it.
+
+
+
+
Comparison
+
+
gt(v1, v2): v1 > v2
+
gte(v1, v2): v1 >= v2
+
lt(v1, v2): v1 < v2
+
lte(v1, v2): v1 <= v2
+
eq(v1, v2): v1 == v2 This is true if they're logically equivalent,
+even if they're not the exact same string. You already know how to
+compare strings.
+
neq(v1, v2): v1 != v2 The opposite of eq.
+
cmp(v1, comparator, v2): Pass in a comparison string, and it'll call
+the corresponding function above. "===" and "!==" do simple
+string comparison, but are included for completeness. Throws if an
+invalid comparison string is provided.
+
compare(v1, v2): Return 0 if v1 == v2, or 1 if v1 is greater, or -1 if
+v2 is greater. Sorts in ascending order if passed to Array.sort().
+
rcompare(v1, v2): The reverse of compare. Sorts an array of versions
+in descending order when passed to Array.sort().
+
+
Ranges
+
+
validRange(range): Return the valid range or null if it's not valid
+
satisfies(version, range): Return true if the version satisfies the
+range.
+
maxSatisfying(versions, range): Return the highest version in the list
+that satisfies the range, or null if none of them do.
+
gtr(version, range): Return true if version is greater than all the
+versions possible in the range.
+
ltr(version, range): Return true if version is less than all the
+versions possible in the range.
+
outside(version, range, hilo): Return true if the version is outside
+the bounds of the range in either the high or low direction. The
+hilo argument must be either the string '>' or '<'. (This is
+the function called by gtr and ltr.)
+
+
Note that, since ranges may be non-contiguous, a version might not be
+greater than a range, less than a range, or satisfy a range! For
+example, the range 1.2 <1.2.9 || >2.0.0 would have a hole from 1.2.9
+until 2.0.0, so the version 1.2.10 would not be greater than the
+range (because 2.0.1 satisfies, which is higher), nor less than the
+range (since 1.2.8 satisfies, which is lower), and it also does not
+satisfy the range.
+
If you want to know if a version satisfies or does not satisfy a
+range, use the satisfies(version, range) function.
+
diff --git a/deps/npm/lib/adduser.js b/deps/npm/lib/adduser.js
index 7e933ea..9693aeb 100644
--- a/deps/npm/lib/adduser.js
+++ b/deps/npm/lib/adduser.js
@@ -166,9 +166,10 @@ function save (c, u, cb) {
}
else {
npm.config.setCredentialsByURI(uri, {
- username : u.u,
- password : u.p,
- email : u.e
+ username : u.u,
+ password : u.p,
+ email : u.e,
+ alwaysAuth : npm.config.get("always-auth")
})
}
diff --git a/deps/npm/lib/build.js b/deps/npm/lib/build.js
index f1c61bd..2e01ef6 100644
--- a/deps/npm/lib/build.js
+++ b/deps/npm/lib/build.js
@@ -19,6 +19,8 @@ var npm = require("./npm.js")
, cmdShim = require("cmd-shim")
, cmdShimIfExists = cmdShim.ifExists
, asyncMap = require("slide").asyncMap
+ , ini = require("ini")
+ , writeFile = require("write-file-atomic")
module.exports = build
build.usage = "npm build \n(this is plumbing)"
@@ -41,6 +43,7 @@ function build (args, global, didPre, didRB, cb) {
function build_ (global, didPre, didRB) { return function (folder, cb) {
folder = path.resolve(folder)
+ if (build._didBuild[folder]) log.error("build", "already built", folder)
build._didBuild[folder] = true
log.info("build", folder)
readJson(path.resolve(folder, "package.json"), function (er, pkg) {
@@ -48,7 +51,7 @@ function build_ (global, didPre, didRB) { return function (folder, cb) {
chain
( [ !didPre && [lifecycle, pkg, "preinstall", folder]
, [linkStuff, pkg, folder, global, didRB]
- , pkg.name === "npm" && [writeBuiltinConf, folder]
+ , [writeBuiltinConf, pkg, folder]
, didPre !== build._noLC && [lifecycle, pkg, "install", folder]
, didPre !== build._noLC && [lifecycle, pkg, "postinstall", folder]
, didPre !== build._noLC
@@ -58,14 +61,21 @@ function build_ (global, didPre, didRB) { return function (folder, cb) {
})
}}
-function writeBuiltinConf (folder, cb) {
- // the builtin config is "sticky". Any time npm installs itself,
- // it puts its builtin config file there, as well.
- if (!npm.config.usingBuiltin
- || folder !== path.dirname(__dirname)) {
+function writeBuiltinConf (pkg, folder, cb) {
+ // the builtin config is "sticky". Any time npm installs
+ // itself globally, it puts its builtin config file there
+ var parent = path.dirname(folder)
+ var dir = npm.globalDir
+
+ if (pkg.name !== "npm" ||
+ !npm.config.get("global") ||
+ !npm.config.usingBuiltin ||
+ dir !== parent) {
return cb()
}
- npm.config.save("builtin", cb)
+
+ var data = ini.stringify(npm.config.sources.builtin.data)
+ writeFile(path.resolve(folder, "npmrc"), data, cb)
}
function linkStuff (pkg, folder, global, didRB, cb) {
diff --git a/deps/npm/lib/cache.js b/deps/npm/lib/cache.js
index 281d610..e1afb0d 100644
--- a/deps/npm/lib/cache.js
+++ b/deps/npm/lib/cache.js
@@ -62,6 +62,7 @@ cache.read = read
var npm = require("./npm.js")
, fs = require("graceful-fs")
+ , writeFileAtomic = require("write-file-atomic")
, assert = require("assert")
, rm = require("./utils/gently-rm.js")
, readJson = require("read-package-json")
@@ -77,8 +78,10 @@ var npm = require("./npm.js")
, addRemoteGit = require("./cache/add-remote-git.js")
, maybeGithub = require("./cache/maybe-github.js")
, inflight = require("inflight")
+ , realizePackageSpecifier = require("realize-package-specifier")
, npa = require("npm-package-arg")
, getStat = require("./cache/get-stat.js")
+ , cachedPackageRoot = require("./cache/cached-package-root.js")
cache.usage = "npm cache add "
+ "\nnpm cache add "
@@ -129,8 +132,11 @@ function read (name, ver, forceBypass, cb) {
if (forceBypass === undefined || forceBypass === null) forceBypass = true
- var jsonFile = path.join(npm.cache, name, ver, "package", "package.json")
+ var root = cachedPackageRoot({name : name, version : ver})
function c (er, data) {
+ log.silly("cache", "addNamed cb", name+"@"+ver)
+ if (er) log.verbose("cache", "addNamed error for", name+"@"+ver, er)
+
if (data) deprCheck(data)
return cb(er, data)
@@ -141,15 +147,16 @@ function read (name, ver, forceBypass, cb) {
return addNamed(name, ver, null, c)
}
- readJson(jsonFile, function (er, data) {
- er = needName(er, data)
- er = needVersion(er, data)
+ readJson(path.join(root, "package", "package.json"), function (er, data) {
if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
- if (er) return addNamed(name, ver, null, c)
- deprCheck(data)
+ if (data) {
+ if (!data.name) return cb(new Error("No name provided"))
+ if (!data.version) return cb(new Error("No version provided"))
+ }
- c(er, data)
+ if (er) return addNamed(name, ver, null, c)
+ else c(er, data)
})
}
@@ -223,7 +230,6 @@ cache.add = function (pkg, ver, where, scrub, cb) {
add([pkg, ver], where, cb)
})
}
- log.verbose("cache add", [pkg, ver])
return add([pkg, ver], where, cb)
}
@@ -246,7 +252,8 @@ function add (args, where, cb) {
+ " npm cache add \n"
+ " npm cache add \n"
, spec
- , p
+
+ log.silly("cache add", "args", args)
if (args[1] === undefined) args[1] = null
@@ -257,43 +264,26 @@ function add (args, where, cb) {
spec = args[0]
}
- log.verbose("cache add", "spec=%j args=%j", spec, args)
+ log.verbose("cache add", "spec", spec)
if (!spec) return cb(usage)
if (adding <= 0) {
npm.spinner.start()
}
- adding ++
+ adding++
cb = afterAdd(cb)
- // package.json can have local URI ("file:") dependencies which require
- // normalization
- p = npa(spec)
- if (p.type === "local" && where) spec = path.resolve(where, p.spec)
- log.verbose("parsed spec", p)
-
- // short-circuit local installs
- fs.stat(spec, function (er, s) {
- if (er) return addNonLocal(spec, cb)
- if (!s.isDirectory()) return addAndLogLocal(spec, cb)
- fs.stat(path.join(spec, "package.json"), function (er) {
- if (er) return addNonLocal(spec, cb)
- addAndLogLocal(spec, cb)
- })
- })
-}
+ realizePackageSpecifier(spec, where, function (err, p) {
+ if (err) return cb(err)
-function addAndLogLocal (spec, cb) {
- log.verbose("cache add", "local package", path.resolve(spec))
- return addLocal(spec, null, cb)
-}
-
-function addNonLocal (spec, cb) {
- var p = npa(spec)
- log.verbose("parsed spec", p)
+ log.silly("cache add", "parsed spec", p)
switch (p.type) {
+ case "local":
+ case "directory":
+ addLocal(p, null, cb)
+ break
case "remote":
addRemoteTarball(p.spec, {name : p.name}, null, cb)
break
@@ -308,6 +298,7 @@ function addNonLocal (spec, cb) {
cb(new Error("couldn't figure out how to install " + spec))
}
+ })
}
function unpack (pkg, ver, unpackTarget, dMode, fMode, uid, gid, cb) {
@@ -323,7 +314,7 @@ function unpack (pkg, ver, unpackTarget, dMode, fMode, uid, gid, cb) {
}
npm.commands.unbuild([unpackTarget], true, function (er) {
if (er) return cb(er)
- tar.unpack( path.join(npm.cache, pkg, ver, "package.tgz")
+ tar.unpack( path.join(cachedPackageRoot({name : pkg, version : ver}), "package.tgz")
, unpackTarget
, dMode, fMode
, uid, gid
@@ -333,50 +324,25 @@ function unpack (pkg, ver, unpackTarget, dMode, fMode, uid, gid, cb) {
}
function afterAdd (cb) { return function (er, data) {
- adding --
- if (adding <= 0) {
- npm.spinner.stop()
- }
- if (er || !data || !data.name || !data.version) {
- return cb(er, data)
- }
+ adding--
+ if (adding <= 0) npm.spinner.stop()
+
+ if (er || !data || !data.name || !data.version) return cb(er, data)
+ log.silly("cache", "afterAdd", data.name+"@"+data.version)
// Save the resolved, shasum, etc. into the data so that the next
// time we load from this cached data, we have all the same info.
- var name = data.name
- var ver = data.version
- var pj = path.join(npm.cache, name, ver, "package", "package.json")
- var tmp = pj + "." + process.pid
+ var pj = path.join(cachedPackageRoot(data), "package", "package.json")
var done = inflight(pj, cb)
+ if (!done) return log.verbose("afterAdd", pj, "already in flight; not writing")
+ log.verbose("afterAdd", pj, "not in flight; writing")
- if (!done) return undefined
-
- fs.writeFile(tmp, JSON.stringify(data), "utf8", function (er) {
+ getStat(function (er, cs) {
if (er) return done(er)
- getStat(function (er, cs) {
- if (er) return done(er)
- fs.rename(tmp, pj, function (er) {
- if (cs.uid && cs.gid) {
- fs.chown(pj, cs.uid, cs.gid, function (er) {
- return done(er, data)
- })
- } else {
- done(er, data)
- }
- })
+ writeFileAtomic(pj, JSON.stringify(data), {chown : cs}, function (er) {
+ if (!er) log.verbose("afterAdd", pj, "written")
+ return done(er, data)
})
})
}}
-
-function needName (er, data) {
- return er ? er
- : (data && !data.name) ? new Error("No name provided")
- : null
-}
-
-function needVersion (er, data) {
- return er ? er
- : (data && !data.version) ? new Error("No version provided")
- : null
-}
diff --git a/deps/npm/lib/cache/add-local-tarball.js b/deps/npm/lib/cache/add-local-tarball.js
index f7cd761..e84b66d 100644
--- a/deps/npm/lib/cache/add-local-tarball.js
+++ b/deps/npm/lib/cache/add-local-tarball.js
@@ -1,80 +1,52 @@
var mkdir = require("mkdirp")
, assert = require("assert")
, fs = require("graceful-fs")
- , readJson = require("read-package-json")
- , log = require("npmlog")
+ , writeFileAtomic = require("write-file-atomic")
, path = require("path")
, sha = require("sha")
, npm = require("../npm.js")
+ , log = require("npmlog")
, tar = require("../utils/tar.js")
, pathIsInside = require("path-is-inside")
- , locker = require("../utils/locker.js")
- , lock = locker.lock
- , unlock = locker.unlock
, getCacheStat = require("./get-stat.js")
+ , cachedPackageRoot = require("./cached-package-root.js")
, chownr = require("chownr")
, inflight = require("inflight")
, once = require("once")
+ , writeStream = require("fs-write-stream-atomic")
+ , randomBytes = require("crypto").pseudoRandomBytes // only need uniqueness
module.exports = addLocalTarball
-function addLocalTarball (p, pkgData, shasum, cb_) {
+function addLocalTarball (p, pkgData, shasum, cb) {
assert(typeof p === "string", "must have path")
- assert(typeof cb_ === "function", "must have callback")
+ assert(typeof cb === "function", "must have callback")
if (!pkgData) pkgData = {}
- var name = pkgData.name || ""
- // If we don't have a shasum yet, then get the shasum now.
+ // If we don't have a shasum yet, compute it.
if (!shasum) {
return sha.get(p, function (er, shasum) {
- if (er) return cb_(er)
- addLocalTarball(p, pkgData, shasum, cb_)
+ if (er) return cb(er)
+ log.silly("addLocalTarball", "shasum (computed)", shasum)
+ addLocalTarball(p, pkgData, shasum, cb)
})
}
- // if it's a tar, and not in place,
- // then unzip to .tmp, add the tmp folder, and clean up tmp
- if (pathIsInside(p, npm.tmp))
- return addTmpTarball(p, pkgData, shasum, cb_)
-
if (pathIsInside(p, npm.cache)) {
- if (path.basename(p) !== "package.tgz") return cb_(new Error(
- "Not a valid cache tarball name: "+p))
- return addPlacedTarball(p, pkgData, shasum, cb_)
+ if (path.basename(p) !== "package.tgz") {
+ return cb(new Error("Not a valid cache tarball name: "+p))
+ }
+ log.verbose("addLocalTarball", "adding from inside cache", p)
+ return addPlacedTarball(p, pkgData, shasum, cb)
}
- function cb (er, data) {
+ addTmpTarball(p, pkgData, shasum, function (er, data) {
if (data) {
data._resolved = p
data._shasum = data._shasum || shasum
}
- return cb_(er, data)
- }
-
- // just copy it over and then add the temp tarball file.
- var tmp = path.join(npm.tmp, name + Date.now()
- + "-" + Math.random(), "tmp.tgz")
- mkdir(path.dirname(tmp), function (er) {
- if (er) return cb(er)
- var from = fs.createReadStream(p)
- , to = fs.createWriteStream(tmp)
- , errState = null
- function errHandler (er) {
- if (errState) return
- return cb(errState = er)
- }
- from.on("error", errHandler)
- to.on("error", errHandler)
- to.on("close", function () {
- if (errState) return
- log.verbose("chmod", tmp, npm.modes.file.toString(8))
- fs.chmod(tmp, npm.modes.file, function (er) {
- if (er) return cb(er)
- addTmpTarball(tmp, pkgData, shasum, cb)
- })
- })
- from.pipe(to)
+ return cb(er, data)
})
}
@@ -89,10 +61,7 @@ function addPlacedTarball (p, pkgData, shasum, cb) {
}
function addPlacedTarball_ (p, pkgData, uid, gid, resolvedSum, cb) {
- // now we know it's in place already as .cache/name/ver/package.tgz
- var name = pkgData.name
- , version = pkgData.version
- , folder = path.join(npm.cache, name, version, "package")
+ var folder = path.join(cachedPackageRoot(pkgData), "package")
// First, make sure we have the shasum, if we don't already.
if (!resolvedSum) {
@@ -103,90 +72,85 @@ function addPlacedTarball_ (p, pkgData, uid, gid, resolvedSum, cb) {
return
}
- lock(folder, function (er) {
+ mkdir(folder, function (er) {
if (er) return cb(er)
-
- // async try/finally
- var originalCb = cb
- cb = function (er, data) {
- unlock(folder, function (er2) {
- return originalCb(er || er2, data)
- })
- }
-
- mkdir(folder, function (er) {
- if (er) return cb(er)
- var pj = path.join(folder, "package.json")
- var json = JSON.stringify(pkgData, null, 2)
- fs.writeFile(pj, json, "utf8", function (er) {
- cb(er, pkgData)
- })
+ var pj = path.join(folder, "package.json")
+ var json = JSON.stringify(pkgData, null, 2)
+ writeFileAtomic(pj, json, function (er) {
+ cb(er, pkgData)
})
})
}
function addTmpTarball (tgz, pkgData, shasum, cb) {
assert(typeof cb === "function", "must have callback function")
- assert(shasum, "should have shasum by now")
+ assert(shasum, "must have shasum by now")
cb = inflight("addTmpTarball:" + tgz, cb)
- if (!cb) return
+ if (!cb) return log.verbose("addTmpTarball", tgz, "already in flight; not adding")
+ log.verbose("addTmpTarball", tgz, "not in flight; adding")
// we already have the package info, so just move into place
if (pkgData && pkgData.name && pkgData.version) {
+ log.verbose(
+ "addTmpTarball",
+ "already have metadata; skipping unpack for",
+ pkgData.name + "@" + pkgData.version
+ )
return addTmpTarball_(tgz, pkgData, shasum, cb)
}
- // This is a tarball we probably downloaded from the internet.
- // The shasum's already been checked, but we haven't ever had
- // a peek inside, so we unpack it here just to make sure it is
- // what it says it is.
- // Note: we might not have any clue what we think it is, for
- // example if the user just did `npm install ./foo.tgz`
-
- var target = tgz + "-unpack"
- getCacheStat(function (er, cs) {
- tar.unpack(tgz, target, null, null, cs.uid, cs.gid, next)
- })
+ // This is a tarball we probably downloaded from the internet. The shasum's
+ // already been checked, but we haven't ever had a peek inside, so we unpack
+ // it here just to make sure it is what it says it is.
+ //
+ // NOTE: we might not have any clue what we think it is, for example if the
+ // user just did `npm install ./foo.tgz`
- function next (er) {
+ // generate a unique filename
+ randomBytes(6, function (er, random) {
if (er) return cb(er)
- var pj = path.join(target, "package.json")
- readJson(pj, function (er, data) {
- // XXX dry with similar stanza in add-local.js
- er = needName(er, data)
- er = needVersion(er, data)
- // check that this is what we expected.
- if (!er && pkgData.name && pkgData.name !== data.name) {
- er = new Error( "Invalid Package: expected "
- + pkgData.name + " but found "
- + data.name )
- }
-
- if (!er && pkgData.version && pkgData.version !== data.version) {
- er = new Error( "Invalid Package: expected "
- + pkgData.name + "@" + pkgData.version
- + " but found "
- + data.name + "@" + data.version )
- }
+ var target = path.join(npm.tmp, "unpack-" + random.toString("hex"))
+ getCacheStat(function (er, cs) {
if (er) return cb(er)
- addTmpTarball_(tgz, data, shasum, cb)
+ log.verbose("addTmpTarball", "validating metadata from", tgz)
+ tar.unpack(tgz, target, null, null, cs.uid, cs.gid, function (er, data) {
+ if (er) return cb(er)
+
+ // check that this is what we expected.
+ if (!data.name) {
+ return cb(new Error("No name provided"))
+ }
+ else if (pkgData.name && data.name !== pkgData.name) {
+ return cb(new Error("Invalid Package: expected " + pkgData.name +
+ " but found " + data.name))
+ }
+
+ if (!data.version) {
+ return cb(new Error("No version provided"))
+ }
+ else if (pkgData.version && data.version !== pkgData.version) {
+ return cb(new Error("Invalid Package: expected " +
+ pkgData.name + "@" + pkgData.version +
+ " but found " + data.name + "@" + data.version))
+ }
+
+ addTmpTarball_(tgz, data, shasum, cb)
+ })
})
- }
+ })
}
function addTmpTarball_ (tgz, data, shasum, cb) {
assert(typeof cb === "function", "must have callback function")
cb = once(cb)
- var name = data.name
- var version = data.version
- assert(name, "should have package name by now")
- assert(version, "should have package version by now")
+ assert(data.name, "should have package name by now")
+ assert(data.version, "should have package version by now")
- var root = path.resolve(npm.cache, name, version)
+ var root = cachedPackageRoot(data)
var pkg = path.resolve(root, "package")
var target = path.resolve(root, "package.tgz")
getCacheStat(function (er, cs) {
@@ -196,13 +160,13 @@ function addTmpTarball_ (tgz, data, shasum, cb) {
// chown starting from the first dir created by mkdirp,
// or the root dir, if none had to be created, so that
// we know that we get all the children.
- function chown (er) {
+ function chown () {
chownr(created || root, cs.uid, cs.gid, done)
}
if (er) return cb(er)
var read = fs.createReadStream(tgz)
- var write = fs.createWriteStream(target)
+ var write = writeStream(target, { mode: npm.modes.file })
var fin = cs.uid && cs.gid ? chown : done
read.on("error", cb).pipe(write).on("error", cb).on("close", fin)
})
@@ -214,15 +178,3 @@ function addTmpTarball_ (tgz, data, shasum, cb) {
cb(null, data)
}
}
-
-function needName(er, data) {
- return er ? er
- : (data && !data.name) ? new Error("No name provided")
- : null
-}
-
-function needVersion(er, data) {
- return er ? er
- : (data && !data.version) ? new Error("No version provided")
- : null
-}
diff --git a/deps/npm/lib/cache/add-local.js b/deps/npm/lib/cache/add-local.js
index bedf34b..b425d7f 100644
--- a/deps/npm/lib/cache/add-local.js
+++ b/deps/npm/lib/cache/add-local.js
@@ -1,5 +1,4 @@
-var fs = require("graceful-fs")
- , assert = require("assert")
+var assert = require("assert")
, path = require("path")
, mkdir = require("mkdirp")
, chownr = require("chownr")
@@ -9,44 +8,36 @@ var fs = require("graceful-fs")
, npm = require("../npm.js")
, tar = require("../utils/tar.js")
, deprCheck = require("../utils/depr-check.js")
- , locker = require("../utils/locker.js")
- , lock = locker.lock
- , unlock = locker.unlock
, getCacheStat = require("./get-stat.js")
+ , cachedPackageRoot = require("./cached-package-root.js")
, addLocalTarball = require("./add-local-tarball.js")
, sha = require("sha")
module.exports = addLocal
function addLocal (p, pkgData, cb_) {
- assert(typeof p === "string", "must have path")
+ assert(typeof p === "object", "must have spec info")
assert(typeof cb === "function", "must have callback")
pkgData = pkgData || {}
function cb (er, data) {
- unlock(p, function () {
- if (er) {
- log.error("addLocal", "Could not install %s", p)
- return cb_(er)
- }
- if (data && !data._fromGithub) {
- data._from = path.relative(npm.prefix, p) || "."
- }
- return cb_(er, data)
- })
+ if (er) {
+ log.error("addLocal", "Could not install %s", p.spec)
+ return cb_(er)
+ }
+ if (data && !data._fromGithub) {
+ data._from = path.relative(npm.prefix, p.spec) || "."
+ }
+ return cb_(er, data)
}
- lock(p, function (er) {
- if (er) return cb(er)
- // figure out if this is a folder or file.
- fs.stat(p, function (er, s) {
- if (er) return cb(er)
-
- if (s.isDirectory()) addLocalDirectory(p, pkgData, null, cb)
- else addLocalTarball(p, pkgData, null, cb)
- })
- })
+ if (p.type === "directory") {
+ addLocalDirectory(p.spec, pkgData, null, cb)
+ }
+ else {
+ addLocalTarball(p.spec, pkgData, null, cb)
+ }
}
// At this point, if shasum is set, it's something that we've already
@@ -61,30 +52,33 @@ function addLocalDirectory (p, pkgData, shasum, cb) {
"Adding a cache directory to the cache will make the world implode."))
readJson(path.join(p, "package.json"), false, function (er, data) {
- er = needName(er, data)
- er = needVersion(er, data)
+ if (er) return cb(er)
- // check that this is what we expected.
- if (!er && pkgData.name && pkgData.name !== data.name) {
- er = new Error( "Invalid Package: expected "
- + pkgData.name + " but found "
- + data.name )
+ if (!data.name) {
+ return cb(new Error("No name provided in package.json"))
+ }
+ else if (pkgData.name && pkgData.name !== data.name) {
+ return cb(new Error(
+ "Invalid package: expected " + pkgData.name + " but found " + data.name
+ ))
}
- if (!er && pkgData.version && pkgData.version !== data.version) {
- er = new Error( "Invalid Package: expected "
- + pkgData.name + "@" + pkgData.version
- + " but found "
- + data.name + "@" + data.version )
+ if (!data.version) {
+ return cb(new Error("No version provided in package.json"))
+ }
+ else if (pkgData.version && pkgData.version !== data.version) {
+ return cb(new Error(
+ "Invalid package: expected " + pkgData.name + "@" + pkgData.version +
+ " but found " + data.name + "@" + data.version
+ ))
}
- if (er) return cb(er)
deprCheck(data)
// pack to {cache}/name/ver/package.tgz
- var croot = path.resolve(npm.cache, data.name, data.version)
- var tgz = path.resolve(croot, "package.tgz")
- var pj = path.resolve(croot, "package/package.json")
+ var root = cachedPackageRoot(data)
+ var tgz = path.resolve(root, "package.tgz")
+ var pj = path.resolve(root, "package/package.json")
getCacheStat(function (er, cs) {
mkdir(path.dirname(pj), function (er, made) {
if (er) return cb(er)
@@ -120,15 +114,3 @@ function addLocalDirectory (p, pkgData, shasum, cb) {
}
})
}
-
-function needName(er, data) {
- return er ? er
- : (data && !data.name) ? new Error("No name provided")
- : null
-}
-
-function needVersion(er, data) {
- return er ? er
- : (data && !data.version) ? new Error("No version provided")
- : null
-}
diff --git a/deps/npm/lib/cache/add-named.js b/deps/npm/lib/cache/add-named.js
index 091d43c..1bd7af1 100644
--- a/deps/npm/lib/cache/add-named.js
+++ b/deps/npm/lib/cache/add-named.js
@@ -10,42 +10,45 @@ var path = require("path")
, registry = npm.registry
, deprCheck = require("../utils/depr-check.js")
, inflight = require("inflight")
- , locker = require("../utils/locker.js")
- , lock = locker.lock
- , unlock = locker.unlock
, addRemoteTarball = require("./add-remote-tarball.js")
+ , cachedPackageRoot = require("./cached-package-root.js")
, mapToRegistry = require("../utils/map-to-registry.js")
module.exports = addNamed
-var NAME_PREFIX = "addName:"
+function getOnceFromRegistry (name, from, next, done) {
+ mapToRegistry(name, npm.config, function (er, uri) {
+ if (er) return done(er)
+
+ var key = "registry:" + uri
+ next = inflight(key, next)
+ if (!next) return log.verbose(from, key, "already in flight; waiting")
+ else log.verbose(from, key, "not in flight; fetching")
+
+ registry.get(uri, null, next)
+ })
+}
+
function addNamed (name, version, data, cb_) {
assert(typeof name === "string", "must have module name")
assert(typeof cb_ === "function", "must have callback")
- log.verbose("addNamed", [name, version])
-
var key = name + "@" + version
+ log.verbose("addNamed", key)
+
function cb (er, data) {
if (data && !data._fromGithub) data._from = key
- unlock(key, function () { cb_(er, data) })
+ cb_(er, data)
}
- cb_ = inflight(NAME_PREFIX + key, cb_)
-
- if (!cb_) return
-
- log.verbose("addNamed", [semver.valid(version), semver.validRange(version)])
- lock(key, function (er) {
- if (er) return cb(er)
-
- var fn = ( semver.valid(version, true) ? addNameVersion
- : semver.validRange(version, true) ? addNameRange
- : addNameTag
- )
- fn(name, version, data, cb)
- })
+ log.silly("addNamed", "semver.valid", semver.valid(version))
+ log.silly("addNamed", "semver.validRange", semver.validRange(version))
+ var fn = ( semver.valid(version, true) ? addNameVersion
+ : semver.validRange(version, true) ? addNameRange
+ : addNameTag
+ )
+ fn(name, version, data, cb)
}
function addNameTag (name, tag, data, cb) {
@@ -56,17 +59,14 @@ function addNameTag (name, tag, data, cb) {
tag = npm.config.get("tag")
}
- mapToRegistry(name, npm.config, function (er, uri) {
- if (er) return cb(er)
-
- registry.get(uri, null, next)
- })
+ getOnceFromRegistry(name, "addNameTag", next, cb)
function next (er, data, json, resp) {
- if (!er) {
- er = errorResponse(name, resp)
- }
+ if (!er) er = errorResponse(name, resp)
if (er) return cb(er)
+
+ log.silly("addNameTag", "next cb for", name, "with tag", tag)
+
engineFilter(data)
if (data["dist-tags"] && data["dist-tags"][tag]
&& data.versions[data["dist-tags"][tag]]) {
@@ -111,11 +111,7 @@ function addNameVersion (name, v, data, cb) {
return next()
}
- mapToRegistry(name, npm.config, function (er, uri) {
- if (er) return cb(er)
-
- registry.get(uri, null, setData)
- })
+ getOnceFromRegistry(name, "addNameVersion", setData, cb)
function setData (er, d, json, resp) {
if (!er) {
@@ -147,18 +143,27 @@ function addNameVersion (name, v, data, cb) {
}
// we got cached data, so let's see if we have a tarball.
- var pkgroot = path.join(npm.cache, name, ver)
+ var pkgroot = cachedPackageRoot({name : name, version : ver})
var pkgtgz = path.join(pkgroot, "package.tgz")
var pkgjson = path.join(pkgroot, "package", "package.json")
fs.stat(pkgtgz, function (er) {
if (!er) {
readJson(pkgjson, function (er, data) {
- er = needName(er, data)
- er = needVersion(er, data)
- if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR")
- return cb(er)
+ if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
+
+ if (data) {
+ if (!data.name) return cb(new Error("No name provided"))
+ if (!data.version) return cb(new Error("No version provided"))
+
+ // check the SHA of the package we have, to ensure it wasn't installed
+ // from somewhere other than the registry (eg, a fork)
+ if (data._shasum && dist.shasum && data._shasum !== dist.shasum) {
+ return fetchit()
+ }
+ }
+
if (er) return fetchit()
- return cb(null, data)
+ else return cb(null, data)
})
} else return fetchit()
})
@@ -193,17 +198,14 @@ function addNameVersion (name, v, data, cb) {
function addNameRange (name, range, data, cb) {
range = semver.validRange(range, true)
if (range === null) return cb(new Error(
- "Invalid version range: "+range))
+ "Invalid version range: " + range
+ ))
log.silly("addNameRange", {name:name, range:range, hasData:!!data})
if (data) return next()
- mapToRegistry(name, npm.config, function (er, uri) {
- if (er) return cb(er)
-
- registry.get(uri, null, setData)
- })
+ getOnceFromRegistry(name, "addNameRange", setData, cb)
function setData (er, d, json, resp) {
if (!er) {
@@ -271,15 +273,3 @@ function errorResponse (name, response) {
}
return er
}
-
-function needName(er, data) {
- return er ? er
- : (data && !data.name) ? new Error("No name provided")
- : null
-}
-
-function needVersion(er, data) {
- return er ? er
- : (data && !data.version) ? new Error("No version provided")
- : null
-}
diff --git a/deps/npm/lib/cache/add-remote-git.js b/deps/npm/lib/cache/add-remote-git.js
index 304d2f3..d8f3f1c 100644
--- a/deps/npm/lib/cache/add-remote-git.js
+++ b/deps/npm/lib/cache/add-remote-git.js
@@ -12,11 +12,9 @@ var mkdir = require("mkdirp")
, npm = require("../npm.js")
, rm = require("../utils/gently-rm.js")
, inflight = require("inflight")
- , locker = require("../utils/locker.js")
- , lock = locker.lock
- , unlock = locker.unlock
, getCacheStat = require("./get-stat.js")
, addLocalTarball = require("./add-local-tarball.js")
+ , writeStream = require("fs-write-stream-atomic")
// 1. cacheDir = path.join(cache,'_git-remotes',sha1(u))
@@ -26,17 +24,9 @@ var mkdir = require("mkdirp")
// 5. git archive /tmp/random.tgz
// 6. addLocalTarball(/tmp/random.tgz) --format=tar --prefix=package/
// silent flag is used if this should error quietly
-module.exports = function addRemoteGit (u, silent, cb_) {
+module.exports = function addRemoteGit (u, silent, cb) {
assert(typeof u === "string", "must have git URL")
- assert(typeof cb_ === "function", "must have callback")
-
- function cb (er, data) {
- unlock(u, function () { cb_(er, data) })
- }
-
- cb_ = inflight(u, cb_)
-
- if (!cb_) return
+ assert(typeof cb === "function", "must have callback")
log.verbose("addRemoteGit", "u=%j silent=%j", u, silent)
var parsed = url.parse(u, true)
@@ -56,23 +46,28 @@ module.exports = function addRemoteGit (u, silent, cb_) {
u = u.replace(/^ssh:\/\//, "")
}
- lock(u, function (er) {
- if (er) return cb(er)
+ cb = inflight(u, cb)
+ if (!cb) return log.verbose("addRemoteGit", u, "already in flight; waiting")
+ log.verbose("addRemoteGit", u, "not in flight; cloning")
+
+ // figure out what we should check out.
+ var co = parsed.hash && parsed.hash.substr(1) || "master"
- // figure out what we should check out.
- var co = parsed.hash && parsed.hash.substr(1) || "master"
+ var v = crypto.createHash("sha1").update(u).digest("hex").slice(0, 8)
+ v = u.replace(/[^a-zA-Z0-9]+/g, "-")+"-"+v
- var v = crypto.createHash("sha1").update(u).digest("hex").slice(0, 8)
- v = u.replace(/[^a-zA-Z0-9]+/g, "-")+"-"+v
+ log.verbose("addRemoteGit", [u, co])
- log.verbose("addRemoteGit", [u, co])
+ var p = path.join(npm.config.get("cache"), "_git-remotes", v)
- var p = path.join(npm.config.get("cache"), "_git-remotes", v)
+ // we don't need global templates when cloning. use this empty dir to specify as template dir
+ mkdir(path.join(npm.config.get("cache"), "_git-remotes", "_templates"), function (er) {
+ if (er) return cb(er)
+ checkGitDir(p, u, co, origUrl, silent, function (er, data) {
+ if (er) return cb(er, data)
- checkGitDir(p, u, co, origUrl, silent, function(er, data) {
- addModeRecursive(p, npm.modes.file, function(erAddMode) {
- if (er) return cb(er, data)
- return cb(erAddMode, data)
+ addModeRecursive(p, npm.modes.file, function (er) {
+ return cb(er, data)
})
})
})
@@ -110,7 +105,8 @@ function cloneGitRemote (p, u, co, origUrl, silent, cb) {
mkdir(p, function (er) {
if (er) return cb(er)
- var args = [ "clone", "--mirror", u, p ]
+ var args = [ "clone", "--template=" + path.join(npm.config.get("cache"),
+ "_git_remotes", "_templates"), "--mirror", u, p ]
var env = gitEnv()
// check for git
@@ -146,10 +142,7 @@ function archiveGitRemote (p, u, co, origUrl, cb) {
}
log.verbose("git fetch -a origin ("+u+")", stdout)
tmp = path.join(npm.tmp, Date.now()+"-"+Math.random(), "tmp.tgz")
- verifyOwnership()
- })
- function verifyOwnership() {
if (process.platform === "win32") {
log.silly("verifyOwnership", "skipping for windows")
resolveHead()
@@ -168,7 +161,7 @@ function archiveGitRemote (p, u, co, origUrl, cb) {
})
})
}
- }
+ })
function resolveHead () {
git.whichAndExec(resolve, {cwd: p, env: env}, function (er, stdout, stderr) {
@@ -205,7 +198,7 @@ function archiveGitRemote (p, u, co, origUrl, cb) {
if (er) return cb(er)
var gzip = zlib.createGzip({ level: 9 })
var args = ["archive", co, "--format=tar", "--prefix=package/"]
- var out = fs.createWriteStream(tmp)
+ var out = writeStream(tmp)
var env = gitEnv()
cb = once(cb)
var cp = git.spawn(args, { env: env, cwd: p })
@@ -231,7 +224,7 @@ function gitEnv () {
if (gitEnv_) return gitEnv_
gitEnv_ = {}
for (var k in process.env) {
- if (!~["GIT_PROXY_COMMAND","GIT_SSH","GIT_SSL_NO_VERIFY"].indexOf(k) && k.match(/^GIT/)) continue
+ if (!~["GIT_PROXY_COMMAND","GIT_SSH","GIT_SSL_NO_VERIFY","GIT_SSL_CAINFO"].indexOf(k) && k.match(/^GIT/)) continue
gitEnv_[k] = process.env[k]
}
return gitEnv_
@@ -261,11 +254,11 @@ function addModeRecursive(p, mode, cb) {
}
function addMode(p, mode, cb) {
- fs.stat(p, function (er, stats) {
- if (er) return cb(er)
- mode = stats.mode | mode
- fs.chmod(p, mode, cb)
- })
+ fs.stat(p, function (er, stats) {
+ if (er) return cb(er)
+ mode = stats.mode | mode
+ fs.chmod(p, mode, cb)
+ })
}
// taken from https://github.com/isaacs/chmodr/blob/master/chmodr.js
@@ -275,4 +268,3 @@ function dirMode(mode) {
if (mode & parseInt( "04", 8)) mode |= parseInt( "01", 8)
return mode
}
-
diff --git a/deps/npm/lib/cache/add-remote-tarball.js b/deps/npm/lib/cache/add-remote-tarball.js
index 2c7d013..9591ba8 100644
--- a/deps/npm/lib/cache/add-remote-tarball.js
+++ b/deps/npm/lib/cache/add-remote-tarball.js
@@ -4,13 +4,10 @@ var mkdir = require("mkdirp")
, path = require("path")
, sha = require("sha")
, retry = require("retry")
- , createWriteStream = require("graceful-fs").createWriteStream
+ , createWriteStream = require("fs-write-stream-atomic")
, npm = require("../npm.js")
, registry = npm.registry
, inflight = require("inflight")
- , locker = require("../utils/locker.js")
- , lock = locker.lock
- , unlock = locker.unlock
, addLocalTarball = require("./add-local-tarball.js")
, cacheFile = require("npm-cache-filename")
@@ -26,14 +23,12 @@ function addRemoteTarball (u, pkgData, shasum, cb_) {
data._shasum = data._shasum || shasum
data._resolved = u
}
- unlock(u, function () {
- cb_(er, data)
- })
+ cb_(er, data)
}
cb_ = inflight(u, cb_)
-
- if (!cb_) return
+ if (!cb_) return log.verbose("addRemoteTarball", u, "already in flight; waiting")
+ log.verbose("addRemoteTarball", u, "not in flight; adding")
// XXX Fetch direct to cache location, store tarballs under
// ${cache}/registry.npmjs.org/pkg/-/pkg-1.2.3.tgz
@@ -44,25 +39,22 @@ function addRemoteTarball (u, pkgData, shasum, cb_) {
addLocalTarball(tmp, pkgData, shasum, cb)
}
- lock(u, function (er) {
+ log.verbose("addRemoteTarball", [u, shasum])
+ mkdir(path.dirname(tmp), function (er) {
if (er) return cb(er)
-
- log.verbose("addRemoteTarball", [u, shasum])
- mkdir(path.dirname(tmp), function (er) {
- if (er) return cb(er)
- addRemoteTarball_(u, tmp, shasum, next)
- })
+ addRemoteTarball_(u, tmp, shasum, next)
})
}
function addRemoteTarball_(u, tmp, shasum, cb) {
// Tuned to spread 3 attempts over about a minute.
// See formula at .
- var operation = retry.operation
- ( { retries: npm.config.get("fetch-retries")
- , factor: npm.config.get("fetch-retry-factor")
- , minTimeout: npm.config.get("fetch-retry-mintimeout")
- , maxTimeout: npm.config.get("fetch-retry-maxtimeout") })
+ var operation = retry.operation({
+ retries: npm.config.get("fetch-retries")
+ , factor: npm.config.get("fetch-retry-factor")
+ , minTimeout: npm.config.get("fetch-retry-mintimeout")
+ , maxTimeout: npm.config.get("fetch-retry-maxtimeout")
+ })
operation.attempt(function (currentAttempt) {
log.info("retry", "fetch attempt " + currentAttempt
diff --git a/deps/npm/lib/cache/cached-package-root.js b/deps/npm/lib/cache/cached-package-root.js
new file mode 100644
index 0000000..7163314
--- /dev/null
+++ b/deps/npm/lib/cache/cached-package-root.js
@@ -0,0 +1,14 @@
+var assert = require("assert")
+var resolve = require("path").resolve
+
+var npm = require("../npm.js")
+
+module.exports = getCacheRoot
+
+function getCacheRoot (data) {
+ assert(data, "must pass package metadata")
+ assert(data.name, "package metadata must include name")
+ assert(data.version, "package metadata must include version")
+
+ return resolve(npm.cache, data.name, data.version)
+}
diff --git a/deps/npm/lib/cache/get-stat.js b/deps/npm/lib/cache/get-stat.js
index 372a86d..45b60ce 100644
--- a/deps/npm/lib/cache/get-stat.js
+++ b/deps/npm/lib/cache/get-stat.js
@@ -10,9 +10,6 @@ var cacheStat = null
module.exports = function getCacheStat (cb) {
if (cacheStat) return cb(null, cacheStat)
- cb = inflight("getCacheStat", cb)
- if (!cb) return
-
fs.stat(npm.cache, function (er, st) {
if (er) return makeCacheDir(cb)
if (!st.isDirectory()) {
@@ -24,6 +21,10 @@ module.exports = function getCacheStat (cb) {
}
function makeCacheDir (cb) {
+ cb = inflight("makeCacheDir", cb)
+ if (!cb) return log.verbose("getCacheStat", "cache creation already in flight; waiting")
+ log.verbose("getCacheStat", "cache creation not in flight; initializing")
+
if (!process.getuid) return mkdir(npm.cache, function (er) {
return cb(er, {})
})
diff --git a/deps/npm/lib/completion.js b/deps/npm/lib/completion.js
index 5c1098a..1d26ffc 100644
--- a/deps/npm/lib/completion.js
+++ b/deps/npm/lib/completion.js
@@ -6,7 +6,7 @@ completion.usage = "npm completion >> ~/.bashrc\n"
+ "source <(npm completion)"
var npm = require("./npm.js")
- , npmconf = require("npmconf")
+ , npmconf = require("./config/core.js")
, configDefs = npmconf.defs
, configTypes = configDefs.types
, shorthands = configDefs.shorthands
@@ -229,7 +229,7 @@ function configCompl (opts, cb) {
// expand with the valid values of various config values.
// not yet implemented.
function configValueCompl (opts, cb) {
- console.error('configValue', opts)
+ console.error("configValue", opts)
return cb(null, [])
}
diff --git a/deps/npm/lib/config.js b/deps/npm/lib/config.js
index 8dc814a..f51156a 100644
--- a/deps/npm/lib/config.js
+++ b/deps/npm/lib/config.js
@@ -11,8 +11,9 @@ config.usage = "npm config set "
var log = require("npmlog")
, npm = require("./npm.js")
+ , npmconf = require("./config/core.js")
, fs = require("graceful-fs")
- , npmconf = require("npmconf")
+ , writeFileAtomic = require("write-file-atomic")
, types = npmconf.defs.types
, ini = require("ini")
, editor = require("editor")
@@ -88,17 +89,16 @@ function edit (cb) {
if (key === "logstream") return arr
return arr.concat(
ini.stringify(obj)
- .replace(/\n$/m, '')
- .replace(/^/g, '; ')
- .replace(/\n/g, '\n; ')
- .split('\n'))
+ .replace(/\n$/m, "")
+ .replace(/^/g, "; ")
+ .replace(/\n/g, "\n; ")
+ .split("\n"))
}, []))
.concat([""])
.join(os.EOL)
- fs.writeFile
+ writeFileAtomic
( f
, data
- , "utf8"
, function (er) {
if (er) return cb(er)
editor(f, { editor: e }, cb)
diff --git a/deps/npm/node_modules/npmconf/npmconf.js b/deps/npm/lib/config/core.js
similarity index 68%
rename from deps/npm/node_modules/npmconf/npmconf.js
rename to deps/npm/lib/config/core.js
index 7607b50..6c61125 100644
--- a/deps/npm/node_modules/npmconf/npmconf.js
+++ b/deps/npm/lib/config/core.js
@@ -1,15 +1,15 @@
-var CC = require('config-chain').ConfigChain
-var inherits = require('inherits')
-var configDefs = require('./config-defs.js')
+var CC = require("config-chain").ConfigChain
+var inherits = require("inherits")
+var configDefs = require("./defaults.js")
var types = configDefs.types
-var once = require('once')
-var fs = require('fs')
-var path = require('path')
-var nopt = require('nopt')
-var ini = require('ini')
+var once = require("once")
+var fs = require("fs")
+var path = require("path")
+var nopt = require("nopt")
+var ini = require("ini")
var Octal = configDefs.Octal
-var mkdirp = require('mkdirp')
+var mkdirp = require("mkdirp")
exports.load = load
exports.Conf = Conf
@@ -18,11 +18,11 @@ exports.rootConf = null
exports.usingBuiltin = false
exports.defs = configDefs
-Object.defineProperty(exports, 'defaults', { get: function () {
+Object.defineProperty(exports, "defaults", { get: function () {
return configDefs.defaults
}, enumerable: true })
-Object.defineProperty(exports, 'types', { get: function () {
+Object.defineProperty(exports, "types", { get: function () {
return configDefs.types
}, enumerable: true })
@@ -36,13 +36,13 @@ var myGid = process.env.SUDO_GID !== undefined
var loading = false
var loadCbs = []
-function load (cli_, builtin_, cb_) {
+function load () {
var cli, builtin, cb
for (var i = 0; i < arguments.length; i++)
switch (typeof arguments[i]) {
- case 'string': builtin = arguments[i]; break
- case 'object': cli = arguments[i]; break
- case 'function': cb = arguments[i]; break
+ case "string": builtin = arguments[i]; break
+ case "object": cli = arguments[i]; break
+ case "function": cb = arguments[i]; break
}
if (!cb)
@@ -85,13 +85,14 @@ function load (cli_, builtin_, cb_) {
exports.usingBuiltin = !!builtin
var rc = exports.rootConf = new Conf()
if (builtin)
- rc.addFile(builtin, 'builtin')
+ rc.addFile(builtin, "builtin")
else
- rc.add({}, 'builtin')
+ rc.add({}, "builtin")
- rc.on('load', function () {
+ rc.on("load", function () {
load_(builtin, rc, cli, cb)
})
+ rc.on("error", cb)
}
function load_(builtin, rc, cli, cb) {
@@ -99,7 +100,7 @@ function load_(builtin, rc, cli, cb) {
var conf = new Conf(rc)
conf.usingBuiltin = !!builtin
- conf.add(cli, 'cli')
+ conf.add(cli, "cli")
conf.addEnv()
conf.loadPrefix(function(er) {
@@ -122,24 +123,24 @@ function load_(builtin, rc, cli, cb) {
// the default or resolved userconfig value. npm will log a "verbose"
// message about this when it happens, but it is a rare enough edge case
// that we don't have to be super concerned about it.
- var projectConf = path.resolve(conf.localPrefix, '.npmrc')
- var defaultUserConfig = rc.get('userconfig')
- var resolvedUserConfig = conf.get('userconfig')
- if (!conf.get('global') &&
+ var projectConf = path.resolve(conf.localPrefix, ".npmrc")
+ var defaultUserConfig = rc.get("userconfig")
+ var resolvedUserConfig = conf.get("userconfig")
+ if (!conf.get("global") &&
projectConf !== defaultUserConfig &&
projectConf !== resolvedUserConfig) {
- conf.addFile(projectConf, 'project')
- conf.once('load', afterPrefix)
+ conf.addFile(projectConf, "project")
+ conf.once("load", afterPrefix)
} else {
- conf.add({}, 'project')
+ conf.add({}, "project")
afterPrefix()
}
})
function afterPrefix() {
- conf.addFile(conf.get('userconfig'), 'user')
- conf.once('error', cb)
- conf.once('load', afterUser)
+ conf.addFile(conf.get("userconfig"), "user")
+ conf.once("error", cb)
+ conf.once("load", afterUser)
}
function afterUser () {
@@ -148,18 +149,18 @@ function load_(builtin, rc, cli, cb) {
// Eg, `npm config get globalconfig --prefix ~/local` should
// return `~/local/etc/npmrc`
// annoying humans and their expectations!
- if (conf.get('prefix')) {
- var etc = path.resolve(conf.get('prefix'), 'etc')
- defaults.globalconfig = path.resolve(etc, 'npmrc')
- defaults.globalignorefile = path.resolve(etc, 'npmignore')
+ if (conf.get("prefix")) {
+ var etc = path.resolve(conf.get("prefix"), "etc")
+ defaults.globalconfig = path.resolve(etc, "npmrc")
+ defaults.globalignorefile = path.resolve(etc, "npmignore")
}
- conf.addFile(conf.get('globalconfig'), 'global')
+ conf.addFile(conf.get("globalconfig"), "global")
// move the builtin into the conf stack now.
conf.root = defaults
- conf.add(rc.shift(), 'builtin')
- conf.once('load', function () {
+ conf.add(rc.shift(), "builtin")
+ conf.once("load", function () {
conf.loadExtras(afterExtras)
})
}
@@ -171,7 +172,7 @@ function load_(builtin, rc, cli, cb) {
// warn about invalid bits.
validate(conf)
- var cafile = conf.get('cafile')
+ var cafile = conf.get("cafile")
if (cafile) {
return conf.loadCAFile(cafile, finalize)
@@ -211,13 +212,13 @@ function Conf (base) {
this.root = configDefs.defaults
}
-Conf.prototype.loadPrefix = require('./lib/load-prefix.js')
-Conf.prototype.loadCAFile = require('./lib/load-cafile.js')
-Conf.prototype.loadUid = require('./lib/load-uid.js')
-Conf.prototype.setUser = require('./lib/set-user.js')
-Conf.prototype.findPrefix = require('./lib/find-prefix.js')
-Conf.prototype.getCredentialsByURI = require('./lib/get-credentials-by-uri.js')
-Conf.prototype.setCredentialsByURI = require('./lib/set-credentials-by-uri.js')
+Conf.prototype.loadPrefix = require("./load-prefix.js")
+Conf.prototype.loadCAFile = require("./load-cafile.js")
+Conf.prototype.loadUid = require("./load-uid.js")
+Conf.prototype.setUser = require("./set-user.js")
+Conf.prototype.findPrefix = require("./find-prefix.js")
+Conf.prototype.getCredentialsByURI = require("./get-credentials-by-uri.js")
+Conf.prototype.setCredentialsByURI = require("./set-credentials-by-uri.js")
Conf.prototype.loadExtras = function(cb) {
this.setUser(function(er) {
@@ -235,17 +236,17 @@ Conf.prototype.loadExtras = function(cb) {
Conf.prototype.save = function (where, cb) {
var target = this.sources[where]
if (!target || !(target.path || target.source) || !target.data) {
- if (where !== 'builtin')
- var er = new Error('bad save target: ' + where)
+ if (where !== "builtin")
+ var er = new Error("bad save target: " + where)
if (cb) {
process.nextTick(cb.bind(null, er))
return this
}
- return this.emit('error', er)
+ return this.emit("error", er)
}
if (target.source) {
- var pref = target.prefix || ''
+ var pref = target.prefix || ""
Object.keys(target.data).forEach(function (k) {
target.source[pref + k] = target.data[k]
})
@@ -259,9 +260,9 @@ Conf.prototype.save = function (where, cb) {
done = done.bind(this)
this._saving ++
- var mode = where === 'user' ? "0600" : "0666"
+ var mode = where === "user" ? "0600" : "0666"
if (!data.trim()) {
- fs.unlink(target.path, function (er) {
+ fs.unlink(target.path, function () {
// ignore the possible error (e.g. the file doesn't exist)
done(null)
})
@@ -269,10 +270,10 @@ Conf.prototype.save = function (where, cb) {
mkdirp(path.dirname(target.path), function (er) {
if (er)
return then(er)
- fs.writeFile(target.path, data, 'utf8', function (er) {
+ fs.writeFile(target.path, data, "utf8", function (er) {
if (er)
return then(er)
- if (where === 'user' && myUid && myGid)
+ if (where === "user" && myUid && myGid)
fs.chown(target.path, +myUid, +myGid, then)
else
then()
@@ -289,12 +290,12 @@ Conf.prototype.save = function (where, cb) {
function done (er) {
if (er) {
if (cb) return cb(er)
- else return this.emit('error', er)
+ else return this.emit("error", er)
}
this._saving --
if (this._saving === 0) {
if (cb) cb()
- this.emit('save')
+ this.emit("save")
}
}
@@ -304,26 +305,32 @@ Conf.prototype.save = function (where, cb) {
Conf.prototype.addFile = function (file, name) {
name = name || file
var marker = {__source__:name}
- this.sources[name] = { path: file, type: 'ini' }
+ this.sources[name] = { path: file, type: "ini" }
this.push(marker)
this._await()
- fs.readFile(file, 'utf8', function (er, data) {
+ fs.readFile(file, "utf8", function (er, data) {
if (er) // just ignore missing files.
return this.add({}, marker)
- this.addString(data, file, 'ini', marker)
+ this.addString(data, file, "ini", marker)
}.bind(this))
return this
}
// always ini files.
Conf.prototype.parse = function (content, file) {
- return CC.prototype.parse.call(this, content, file, 'ini')
+ return CC.prototype.parse.call(this, content, file, "ini")
}
Conf.prototype.add = function (data, marker) {
- Object.keys(data).forEach(function (k) {
- data[k] = parseField(data[k], k)
- })
+ try {
+ Object.keys(data).forEach(function (k) {
+ data[k] = parseField(data[k], k)
+ })
+ }
+ catch (e) {
+ this.emit("error", e)
+ return this
+ }
return CC.prototype.add.call(this, data, marker)
}
@@ -339,15 +346,15 @@ Conf.prototype.addEnv = function (env) {
// leave first char untouched, even if
// it is a "_" - convert all other to "-"
var p = k.toLowerCase()
- .replace(/^npm_config_/, '')
- .replace(/(?!^)_/g, '-')
+ .replace(/^npm_config_/, "")
+ .replace(/(?!^)_/g, "-")
conf[p] = env[k]
})
- return CC.prototype.addEnv.call(this, '', conf, 'env')
+ return CC.prototype.addEnv.call(this, "", conf, "env")
}
function parseField (f, k) {
- if (typeof f !== 'string' && !(f instanceof String))
+ if (typeof f !== "string" && !(f instanceof String))
return f
// type can be an array or single thing.
@@ -358,25 +365,31 @@ function parseField (f, k) {
var isOctal = -1 !== typeList.indexOf(Octal)
var isNumber = isOctal || (-1 !== typeList.indexOf(Number))
- f = (''+f).trim()
+ f = (""+f).trim()
- if (f.match(/^".*"$/))
- f = JSON.parse(f)
+ if (f.match(/^".*"$/)) {
+ try {
+ f = JSON.parse(f)
+ }
+ catch (e) {
+ throw new Error("Failed parsing JSON config key " + k + ": " + f)
+ }
+ }
- if (isBool && !isString && f === '')
+ if (isBool && !isString && f === "")
return true
switch (f) {
- case 'true': return true
- case 'false': return false
- case 'null': return null
- case 'undefined': return undefined
+ case "true": return true
+ case "false": return false
+ case "null": return null
+ case "undefined": return undefined
}
f = envReplace(f)
if (isPath) {
- var homePattern = process.platform === 'win32' ? /^~(\/|\\)/ : /^~\//
+ var homePattern = process.platform === "win32" ? /^~(\/|\\)/ : /^~\//
if (f.match(homePattern) && process.env.HOME) {
f = path.resolve(process.env.HOME, f.substr(2))
}
@@ -390,7 +403,7 @@ function parseField (f, k) {
}
function envReplace (f) {
- if (typeof f !== 'string' || !f) return f
+ if (typeof f !== "string" || !f) return f
// replace any ${ENV} values with the appropriate environ.
var envExpr = /(\\*)\$\{([^}]+)\}/g
@@ -399,7 +412,7 @@ function envReplace (f) {
if (esc)
return orig
if (undefined === process.env[name])
- throw new Error('Failed to replace env in config: '+orig)
+ throw new Error("Failed to replace env in config: "+orig)
return process.env[name]
})
}
diff --git a/deps/npm/node_modules/npmconf/config-defs.js b/deps/npm/lib/config/defaults.js
similarity index 95%
rename from deps/npm/node_modules/npmconf/config-defs.js
rename to deps/npm/lib/config/defaults.js
index b0b4acf..7bd6721 100644
--- a/deps/npm/node_modules/npmconf/config-defs.js
+++ b/deps/npm/lib/config/defaults.js
@@ -16,7 +16,7 @@ try {
} catch (er) {
var util = require("util")
log = { warn: function (m) {
- console.warn(m + ' ' + util.format.apply(util, [].slice.call(arguments, 1)))
+ console.warn(m + " " + util.format.apply(util, [].slice.call(arguments, 1)))
} }
}
@@ -41,7 +41,7 @@ function validateSemver (data, k, val) {
}
function validateTag (data, k, val) {
- val = ('' + val).trim()
+ val = ("" + val).trim()
if (!val || semver.validRange(val)) return false
data[k] = val
}
@@ -126,8 +126,8 @@ Object.defineProperty(exports, "defaults", {get: function () {
}
}
- return defaults =
- { "always-auth" : false
+ defaults = {
+ "always-auth" : false
, "bin-links" : true
, browser : null
@@ -168,11 +168,11 @@ Object.defineProperty(exports, "defaults", {get: function () {
, heading: "npm"
, "ignore-scripts": false
, "init-module": path.resolve(home, ".npm-init.js")
- , "init.author.name" : ""
- , "init.author.email" : ""
- , "init.author.url" : ""
- , "init.version": "1.0.0"
- , "init.license": "ISC"
+ , "init-author-name" : ""
+ , "init-author-email" : ""
+ , "init-author-url" : ""
+ , "init-version": "1.0.0"
+ , "init-license": "ISC"
, json: false
, key: null
, link: false
@@ -231,7 +231,9 @@ Object.defineProperty(exports, "defaults", {get: function () {
, viewer: process.platform === "win32" ? "browser" : "man"
, _exit : true
- }
+ }
+
+ return defaults
}})
exports.types =
@@ -268,11 +270,11 @@ exports.types =
, "heading": String
, "ignore-scripts": Boolean
, "init-module": path
- , "init.author.name" : String
- , "init.author.email" : String
- , "init.author.url" : ["", url]
- , "init.license": String
- , "init.version": semver
+ , "init-author-name" : String
+ , "init-author-email" : String
+ , "init-author-url" : ["", url]
+ , "init-license": String
+ , "init-version": semver
, json: Boolean
, key: [null, String]
, link: Boolean
diff --git a/deps/npm/node_modules/npmconf/lib/find-prefix.js b/deps/npm/lib/config/find-prefix.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/lib/find-prefix.js
rename to deps/npm/lib/config/find-prefix.js
diff --git a/deps/npm/node_modules/npmconf/lib/get-credentials-by-uri.js b/deps/npm/lib/config/get-credentials-by-uri.js
similarity index 75%
rename from deps/npm/node_modules/npmconf/lib/get-credentials-by-uri.js
rename to deps/npm/lib/config/get-credentials-by-uri.js
index 6fb8f31..26a7f43 100644
--- a/deps/npm/node_modules/npmconf/lib/get-credentials-by-uri.js
+++ b/deps/npm/lib/config/get-credentials-by-uri.js
@@ -9,7 +9,16 @@ function getCredentialsByURI (uri) {
var nerfed = toNerfDart(uri)
var defnerf = toNerfDart(this.get("registry"))
- var c = {scope : nerfed}
+ // hidden class micro-optimization
+ var c = {
+ scope : nerfed,
+ token : undefined,
+ password : undefined,
+ username : undefined,
+ email : undefined,
+ auth : undefined,
+ alwaysAuth : undefined
+ }
if (this.get(nerfed + ":_authToken")) {
c.token = this.get(nerfed + ":_authToken")
@@ -49,6 +58,13 @@ function getCredentialsByURI (uri) {
c.email = this.get("email")
}
+ if (this.get(nerfed + ":always-auth") !== undefined) {
+ var val = this.get(nerfed + ":always-auth")
+ c.alwaysAuth = val === "false" ? false : !!val
+ } else if (this.get("always-auth") !== undefined) {
+ c.alwaysAuth = this.get("always-auth")
+ }
+
if (c.username && c.password) {
c.auth = new Buffer(c.username + ":" + c.password).toString("base64")
}
diff --git a/deps/npm/node_modules/npmconf/lib/load-cafile.js b/deps/npm/lib/config/load-cafile.js
similarity index 72%
rename from deps/npm/node_modules/npmconf/lib/load-cafile.js
rename to deps/npm/lib/config/load-cafile.js
index b8c9fff..dc1ff9f 100644
--- a/deps/npm/node_modules/npmconf/lib/load-cafile.js
+++ b/deps/npm/lib/config/load-cafile.js
@@ -1,18 +1,18 @@
module.exports = loadCAFile
-var fs = require('fs')
+var fs = require("fs")
function loadCAFile(cafilePath, cb) {
if (!cafilePath)
return process.nextTick(cb)
- fs.readFile(cafilePath, 'utf8', afterCARead.bind(this))
+ fs.readFile(cafilePath, "utf8", afterCARead.bind(this))
function afterCARead(er, cadata) {
if (er)
return cb(er)
- var delim = '-----END CERTIFICATE-----'
+ var delim = "-----END CERTIFICATE-----"
var output
output = cadata
@@ -24,8 +24,7 @@ function loadCAFile(cafilePath, cb) {
return xs.trimLeft() + delim
})
- this.set('ca', output)
+ this.set("ca", output)
cb(null)
}
-
}
diff --git a/deps/npm/node_modules/npmconf/lib/load-prefix.js b/deps/npm/lib/config/load-prefix.js
similarity index 89%
rename from deps/npm/node_modules/npmconf/lib/load-prefix.js
rename to deps/npm/lib/config/load-prefix.js
index bb39d9c..39d076f 100644
--- a/deps/npm/node_modules/npmconf/lib/load-prefix.js
+++ b/deps/npm/lib/config/load-prefix.js
@@ -1,7 +1,7 @@
module.exports = loadPrefix
var findPrefix = require("./find-prefix.js")
-var path = require('path')
+var path = require("path")
function loadPrefix (cb) {
var cli = this.list[0]
@@ -9,7 +9,7 @@ function loadPrefix (cb) {
Object.defineProperty(this, "prefix",
{ set : function (prefix) {
var g = this.get("global")
- this[g ? 'globalPrefix' : 'localPrefix'] = prefix
+ this[g ? "globalPrefix" : "localPrefix"] = prefix
}.bind(this)
, get : function () {
var g = this.get("global")
@@ -20,7 +20,7 @@ function loadPrefix (cb) {
Object.defineProperty(this, "globalPrefix",
{ set : function (prefix) {
- this.set('prefix', prefix)
+ this.set("prefix", prefix)
}.bind(this)
, get : function () {
return path.resolve(this.get("prefix"))
@@ -44,6 +44,6 @@ function loadPrefix (cb) {
findPrefix(process.cwd(), function (er, found) {
p = found
cb(er)
- }.bind(this))
+ })
}
}
diff --git a/deps/npm/node_modules/npmconf/lib/load-uid.js b/deps/npm/lib/config/load-uid.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/lib/load-uid.js
rename to deps/npm/lib/config/load-uid.js
diff --git a/deps/npm/node_modules/npmconf/lib/nerf-dart.js b/deps/npm/lib/config/nerf-dart.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/lib/nerf-dart.js
rename to deps/npm/lib/config/nerf-dart.js
diff --git a/deps/npm/node_modules/npmconf/lib/set-credentials-by-uri.js b/deps/npm/lib/config/set-credentials-by-uri.js
similarity index 62%
rename from deps/npm/node_modules/npmconf/lib/set-credentials-by-uri.js
rename to deps/npm/lib/config/set-credentials-by-uri.js
index 2fa0d19..31eab44 100644
--- a/deps/npm/node_modules/npmconf/lib/set-credentials-by-uri.js
+++ b/deps/npm/lib/config/set-credentials-by-uri.js
@@ -12,9 +12,10 @@ function setCredentialsByURI (uri, c) {
if (c.token) {
this.set(nerfed + ":_authToken", c.token, "user")
- this.del(nerfed + ":_password", "user")
- this.del(nerfed + ":username", "user")
- this.del(nerfed + ":email", "user")
+ this.del(nerfed + ":_password", "user")
+ this.del(nerfed + ":username", "user")
+ this.del(nerfed + ":email", "user")
+ this.del(nerfed + ":always-auth", "user")
}
else if (c.username || c.password || c.email) {
assert(c.username, "must include username")
@@ -24,9 +25,16 @@ function setCredentialsByURI (uri, c) {
this.del(nerfed + ":_authToken", "user")
var encoded = new Buffer(c.password, "utf8").toString("base64")
- this.set(nerfed + ":_password", encoded, "user")
+ this.set(nerfed + ":_password", encoded, "user")
this.set(nerfed + ":username", c.username, "user")
- this.set(nerfed + ":email", c.email, "user")
+ this.set(nerfed + ":email", c.email, "user")
+
+ if (c.alwaysAuth !== undefined) {
+ this.set(nerfed + ":always-auth", c.alwaysAuth, "user")
+ }
+ else {
+ this.del(nerfed + ":always-auth", "user")
+ }
}
else {
throw new Error("No credentials to set.")
diff --git a/deps/npm/node_modules/npmconf/lib/set-user.js b/deps/npm/lib/config/set-user.js
similarity index 63%
rename from deps/npm/node_modules/npmconf/lib/set-user.js
rename to deps/npm/lib/config/set-user.js
index cf29b1a..4c207a6 100644
--- a/deps/npm/node_modules/npmconf/lib/set-user.js
+++ b/deps/npm/lib/config/set-user.js
@@ -1,9 +1,9 @@
module.exports = setUser
-var Conf = require('../npmconf.js').Conf
-var assert = require('assert')
-var path = require('path')
-var fs = require('fs')
+var assert = require("assert")
+var path = require("path")
+var fs = require("fs")
+var mkdirp = require("mkdirp")
function setUser (cb) {
var defaultConf = this.root
@@ -19,8 +19,11 @@ function setUser (cb) {
}
var prefix = path.resolve(this.get("prefix"))
- fs.stat(prefix, function (er, st) {
- defaultConf.user = st && st.uid
- return cb(er)
+ mkdirp(prefix, function (er) {
+ if (er) return cb(er)
+ fs.stat(prefix, function (er, st) {
+ defaultConf.user = st && st.uid
+ return cb(er)
+ })
})
}
diff --git a/deps/npm/lib/explore.js b/deps/npm/lib/explore.js
index 767d9a8..e87e839 100644
--- a/deps/npm/lib/explore.js
+++ b/deps/npm/lib/explore.js
@@ -27,7 +27,7 @@ function explore (args, cb) {
"Type 'exit' or ^D when finished\n")
npm.spinner.stop()
- var shell = spawn(sh, args, { cwd: cwd, customFds: [0, 1, 2] })
+ var shell = spawn(sh, args, { cwd: cwd, stdio: "inherit" })
shell.on("close", function (er) {
// only fail if non-interactive.
if (!args.length) return cb()
diff --git a/deps/npm/lib/help.js b/deps/npm/lib/help.js
index 8f54d69..747bd50 100644
--- a/deps/npm/lib/help.js
+++ b/deps/npm/lib/help.js
@@ -31,7 +31,7 @@ function help (args, cb) {
// npm help : show basic usage
if (!section) {
- var valid = argv[0] === 'help' ? 0 : 1
+ var valid = argv[0] === "help" ? 0 : 1
return npmUsage(valid, cb)
}
@@ -111,7 +111,7 @@ function viewMan (man, cb) {
switch (viewer) {
case "woman":
var a = ["-e", "(woman-find-file \"" + man + "\")"]
- conf = { env: env, customFds: [ 0, 1, 2] }
+ conf = { env: env, stdio: "inherit" }
var woman = spawn("emacsclient", a, conf)
woman.on("close", cb)
break
@@ -121,7 +121,7 @@ function viewMan (man, cb) {
break
default:
- conf = { env: env, customFds: [ 0, 1, 2] }
+ conf = { env: env, stdio: "inherit" }
var manProcess = spawn("man", [num, section], conf)
manProcess.on("close", cb)
break
@@ -153,8 +153,8 @@ function htmlMan (man) {
function npmUsage (valid, cb) {
npm.config.set("loglevel", "silent")
log.level = "silent"
- console.log
- ( ["\nUsage: npm "
+ console.log(
+ [ "\nUsage: npm "
, ""
, "where is one of:"
, npm.config.get("long") ? usages()
@@ -196,7 +196,7 @@ function usages () {
function wrap (arr) {
- var out = ['']
+ var out = [""]
, l = 0
, line
@@ -209,9 +209,9 @@ function wrap (arr) {
arr.sort(function (a,b) { return a --save` afterwards to install a package and"
- ,"save it as a dependency in the package.json file."
- ,""
- ,"Press ^C at any time to quit."
- ].join("\n"))
-
+ var initFile = npm.config.get("init-module")
+ if (!initJson.yes(npm.config)) {
+ console.log(
+ ["This utility will walk you through creating a package.json file."
+ ,"It only covers the most common items, and tries to guess sane defaults."
+ ,""
+ ,"See `npm help json` for definitive documentation on these fields"
+ ,"and exactly what they do."
+ ,""
+ ,"Use `npm install --save` afterwards to install a package and"
+ ,"save it as a dependency in the package.json file."
+ ,""
+ ,"Press ^C at any time to quit."
+ ].join("\n"))
+ }
initJson(dir, initFile, npm.config, function (er, data) {
log.resume()
- log.silly('package data', data)
- log.info('init', 'written successfully')
- if (er && er.message === 'canceled') {
- log.warn('init', 'canceled')
+ log.silly("package data", data)
+ log.info("init", "written successfully")
+ if (er && er.message === "canceled") {
+ log.warn("init", "canceled")
return cb(null, data)
}
cb(er, data)
diff --git a/deps/npm/lib/install.js b/deps/npm/lib/install.js
index 82d8725..e539307 100644
--- a/deps/npm/lib/install.js
+++ b/deps/npm/lib/install.js
@@ -73,6 +73,7 @@ var npm = require("./npm.js")
, log = require("npmlog")
, path = require("path")
, fs = require("graceful-fs")
+ , writeFileAtomic = require("write-file-atomic")
, cache = require("./cache.js")
, asyncMap = require("slide").asyncMap
, chain = require("slide").chain
@@ -84,6 +85,10 @@ var npm = require("./npm.js")
, sortedObject = require("sorted-object")
, mapToRegistry = require("./utils/map-to-registry.js")
, npa = require("npm-package-arg")
+ , inflight = require("inflight")
+ , locker = require("./utils/locker.js")
+ , lock = locker.lock
+ , unlock = locker.unlock
function install (args, cb_) {
var hasArguments = !!args.length
@@ -143,6 +148,22 @@ function install (args, cb_) {
}
var deps = Object.keys(data.dependencies || {})
log.verbose("install", "where, deps", [where, deps])
+
+ // FIXME: Install peerDependencies as direct dependencies, but only at
+ // the top level. Should only last until peerDependencies are nerfed to
+ // no longer implicitly install themselves.
+ var peers = []
+ Object.keys(data.peerDependencies || {}).forEach(function (dep) {
+ if (!data.dependencies[dep]) {
+ log.verbose(
+ "install",
+ "peerDependency", dep, "wasn't going to be installed; adding"
+ )
+ peers.push(dep)
+ }
+ })
+ log.verbose("install", "where, peers", [where, peers])
+
var context = { family: {}
, ancestors: {}
, explicit: false
@@ -160,10 +181,12 @@ function install (args, cb_) {
installManyTop(deps.map(function (dep) {
var target = data.dependencies[dep]
- target = dep + "@" + target
- return target
- }), where, context, function(er, results) {
- if (er) return cb(er, results)
+ return dep + "@" + target
+ }).concat(peers.map(function (dep) {
+ var target = data.peerDependencies[dep]
+ return dep + "@" + target
+ })), where, context, function(er, results) {
+ if (er || npm.config.get("production")) return cb(er, results)
lifecycle(data, "prepublish", where, function(er) {
return cb(er, results)
})
@@ -205,7 +228,7 @@ function findPeerInvalid (where, cb) {
function findPeerInvalid_ (packageMap, fpiList) {
if (fpiList.indexOf(packageMap) !== -1)
- return
+ return undefined
fpiList.push(packageMap)
@@ -260,7 +283,13 @@ function readDependencies (context, where, opts, cb) {
if (opts && opts.dev) {
if (!data.dependencies) data.dependencies = {}
Object.keys(data.devDependencies || {}).forEach(function (k) {
- data.dependencies[k] = data.devDependencies[k]
+ if (data.dependencies[k]) {
+ log.warn("package.json", "Dependency '%s' exists in both dependencies " +
+ "and devDependencies, using '%s@%s' from dependencies",
+ k, k, data.dependencies[k])
+ } else {
+ data.dependencies[k] = data.devDependencies[k]
+ }
})
}
@@ -292,11 +321,9 @@ function readDependencies (context, where, opts, cb) {
var wrapfile = path.resolve(where, "npm-shrinkwrap.json")
fs.readFile(wrapfile, "utf8", function (er, wrapjson) {
- if (er) {
- log.verbose("readDependencies", "using package.json deps")
- return cb(null, data, null)
- }
+ if (er) return cb(null, data, null)
+ log.verbose("readDependencies", "npm-shrinkwrap.json is overriding dependencies")
var newwrap
try {
newwrap = JSON.parse(wrapjson)
@@ -346,7 +373,7 @@ function save (where, installed, tree, pretty, hasArguments, cb) {
}
var saveBundle = npm.config.get("save-bundle")
- var savePrefix = npm.config.get("save-prefix") || "^"
+ var savePrefix = npm.config.get("save-prefix")
// each item in the tree is a top-level thing that should be saved
// to the package.json file.
@@ -420,7 +447,7 @@ function save (where, installed, tree, pretty, hasArguments, cb) {
data[deps] = sortedObject(data[deps])
data = JSON.stringify(data, null, 2) + "\n"
- fs.writeFile(saveTarget, data, function (er) {
+ writeFileAtomic(saveTarget, data, function (er) {
cb(er, installed, tree, pretty)
})
})
@@ -551,30 +578,58 @@ function installManyTop_ (what, where, context, cb) {
fs.readdir(nm, function (er, pkgs) {
if (er) return installMany(what, where, context, cb)
- pkgs = pkgs.filter(function (p) {
+
+ var scopes = [], unscoped = []
+ pkgs.filter(function (p) {
return !p.match(/^[\._-]/)
+ }).forEach(function (p) {
+ // @names deserve deeper investigation
+ if (p[0] === "@") {
+ scopes.push(p)
+ }
+ else {
+ unscoped.push(p)
+ }
})
- asyncMap(pkgs.map(function (p) {
- return path.resolve(nm, p, "package.json")
- }), function (jsonfile, cb) {
- readJson(jsonfile, log.warn, function (er, data) {
- if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
- if (er) return cb(null, [])
- return cb(null, [[data.name, data.version]])
- })
- }, function (er, packages) {
- // if there's nothing in node_modules, then don't freak out.
- if (er) packages = []
- // add all the existing packages to the family list.
- // however, do not add to the ancestors list.
- packages.forEach(function (p) {
- context.family[p[0]] = p[1]
+
+ maybeScoped(scopes, nm, function (er, scoped) {
+ if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
+ // recombine unscoped with @scope/package packages
+ asyncMap(unscoped.concat(scoped).map(function (p) {
+ return path.resolve(nm, p, "package.json")
+ }), function (jsonfile, cb) {
+ readJson(jsonfile, log.warn, function (er, data) {
+ if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
+ if (er) return cb(null, [])
+ cb(null, [[data.name, data.version]])
+ })
+ }, function (er, packages) {
+ // if there's nothing in node_modules, then don't freak out.
+ if (er) packages = []
+ // add all the existing packages to the family list.
+ // however, do not add to the ancestors list.
+ packages.forEach(function (p) {
+ context.family[p[0]] = p[1]
+ })
+ installMany(what, where, context, cb)
})
- return installMany(what, where, context, cb)
})
})
}
+function maybeScoped (scopes, where, cb) {
+ // find packages in scopes
+ asyncMap(scopes, function (scope, cb) {
+ fs.readdir(path.resolve(where, scope), function (er, scoped) {
+ if (er) return cb(er)
+ var paths = scoped.map(function (p) {
+ return path.join(scope, p)
+ })
+ cb(null, paths)
+ })
+ }, cb)
+}
+
function installMany (what, where, context, cb) {
// readDependencies takes care of figuring out whether the list of
// dependencies we'll iterate below comes from an existing shrinkwrap from a
@@ -614,7 +669,7 @@ function installMany (what, where, context, cb) {
targets.forEach(function (t) {
newPrev[t.name] = t.version
})
- log.silly("resolved", targets)
+ log.silly("install resolved", targets)
targets.filter(function (t) { return t }).forEach(function (t) {
log.info("install", "%s into %s", t._id, where)
})
@@ -652,9 +707,8 @@ function targetResolver (where, context, deps) {
// don't even mess with non-package looking things
inst = inst.filter(function (p) {
if (!p.match(/^[@\._-]/)) return true
- // scope pacakges
- var scopepath = path.join(name, p)
- readdir(scopepath)
+ // scoped packages
+ readdir(path.join(name, p))
})
asyncMap(inst, function (pkg, cb) {
@@ -847,15 +901,9 @@ function resultList (target, where, parentId) {
, target._from ]
}
-// name => install locations
-var installOnesInProgress = Object.create(null)
+var installed = Object.create(null)
-function isIncompatibleInstallOneInProgress(target, where) {
- return target.name in installOnesInProgress &&
- installOnesInProgress[target.name].indexOf(where) !== -1
-}
-
-function installOne_ (target, where, context, cb) {
+function installOne_ (target, where, context, cb_) {
var nm = path.resolve(where, "node_modules")
, targetFolder = path.resolve(nm, target.name)
, prettyWhere = path.relative(process.cwd(), where)
@@ -863,37 +911,55 @@ function installOne_ (target, where, context, cb) {
if (prettyWhere === ".") prettyWhere = null
- if (isIncompatibleInstallOneInProgress(target, where)) {
- // just call back, with no error. the error will be detected in the
- // final check for peer-invalid dependencies
- return cb()
+ cb_ = inflight(target.name + ":" + where, cb_)
+ if (!cb_) return log.verbose(
+ "installOne",
+ "of", target.name,
+ "to", where,
+ "already in flight; waiting"
+ )
+ else log.verbose(
+ "installOne",
+ "of", target.name,
+ "to", where,
+ "not in flight; installing"
+ )
+
+ function cb(er, data) {
+ unlock(nm, target.name, function () { cb_(er, data) })
}
- if (!(target.name in installOnesInProgress)) {
- installOnesInProgress[target.name] = []
- }
- installOnesInProgress[target.name].push(where)
- var indexOfIOIP = installOnesInProgress[target.name].length - 1
- , force = npm.config.get("force")
- , nodeVersion = npm.config.get("node-version")
- , strict = npm.config.get("engine-strict")
- , c = npmInstallChecks
-
- chain
- ( [ [c.checkEngine, target, npm.version, nodeVersion, force, strict]
- , [c.checkPlatform, target, force]
- , [c.checkCycle, target, context.ancestors]
- , [c.checkGit, targetFolder]
- , [write, target, targetFolder, context] ]
- , function (er, d) {
- installOnesInProgress[target.name].splice(indexOfIOIP, 1)
+ lock(nm, target.name, function (er) {
+ if (er) return cb(er)
- if (er) return cb(er)
+ if (targetFolder in installed) {
+ log.error("install", "trying to install", target.version, "to", targetFolder)
+ log.error("install", "but already installed versions", installed[targetFolder])
+ installed[targetFolder].push(target.version)
+ }
+ else {
+ installed[targetFolder] = [target.version]
+ }
- d.push(resultList(target, where, parent && parent._id))
- cb(er, d)
- }
- )
+ var force = npm.config.get("force")
+ , nodeVersion = npm.config.get("node-version")
+ , strict = npm.config.get("engine-strict")
+ , c = npmInstallChecks
+
+ chain(
+ [ [c.checkEngine, target, npm.version, nodeVersion, force, strict]
+ , [c.checkPlatform, target, force]
+ , [c.checkCycle, target, context.ancestors]
+ , [c.checkGit, targetFolder]
+ , [write, target, targetFolder, context] ]
+ , function (er, d) {
+ if (er) return cb(er)
+
+ d.push(resultList(target, where, parent && parent._id))
+ cb(er, d)
+ }
+ )
+ })
}
function write (target, targetFolder, context, cb_) {
@@ -907,15 +973,16 @@ function write (target, targetFolder, context, cb_) {
// is the list of installed packages from that last thing.
if (!er) return cb_(er, data)
- if (false === npm.config.get("rollback")) return cb_(er)
+ if (npm.config.get("rollback") === false) return cb_(er)
npm.rollbacks.push(targetFolder)
cb_(er, data)
}
var bundled = []
- chain
- ( [ [ cache.unpack, target.name, target.version, targetFolder
+ log.silly("install write", "writing", target.name, target.version, "to", targetFolder)
+ chain(
+ [ [ cache.unpack, target.name, target.version, targetFolder
, null, null, user, group ]
, [ fs, "writeFile"
, path.resolve(targetFolder, "package.json")
@@ -950,14 +1017,27 @@ function write (target, targetFolder, context, cb_) {
, explicit: false
, wrap: wrap }
+ var actions =
+ [ [ installManyAndBuild, deps, depsTargetFolder, depsContext ] ]
+
+ // FIXME: This is an accident waiting to happen!
+ //
+ // 1. If multiple children at the same level of the tree share a
+ // peerDependency that's not in the parent's dependencies, because
+ // the peerDeps don't get added to the family, they will keep
+ // getting reinstalled (worked around by inflighting installOne).
+ // 2. The installer can't safely build at the parent level because
+ // that's already being done by the parent's installAndBuild. This
+ // runs the risk of the peerDependency never getting built.
+ //
+ // The fix: Don't install peerDependencies; require them to be
+ // included as explicit dependencies / devDependencies, and warn
+ // or error when they're missing. See #5080 for more arguments in
+ // favor of killing implicit peerDependency installs with fire.
var peerDeps = prepareForInstallMany(data, "peerDependencies", bundled,
wrap, family)
var pdTargetFolder = path.resolve(targetFolder, "..", "..")
var pdContext = context
-
- var actions =
- [ [ installManyAndBuild, deps, depsTargetFolder, depsContext ] ]
-
if (peerDeps.length > 0) {
actions.push(
[ installMany, peerDeps, pdTargetFolder, pdContext ]
@@ -1000,8 +1080,9 @@ function prepareForInstallMany (packageData, depsKey, bundled, wrap, family) {
return !semver.satisfies(family[d], packageData[depsKey][d], true)
return true
}).map(function (d) {
- var t = packageData[depsKey][d]
- t = d + "@" + t
+ var v = packageData[depsKey][d]
+ var t = d + "@" + v
+ log.silly("prepareForInstallMany", "adding", t, "from", packageData.name, depsKey)
return t
})
}
diff --git a/deps/npm/lib/npm.js b/deps/npm/lib/npm.js
index c811be5..e933a13 100644
--- a/deps/npm/lib/npm.js
+++ b/deps/npm/lib/npm.js
@@ -16,7 +16,7 @@ require('child-process-close')
var EventEmitter = require("events").EventEmitter
, npm = module.exports = new EventEmitter()
- , npmconf = require("npmconf")
+ , npmconf = require("./config/core.js")
, log = require("npmlog")
, fs = require("graceful-fs")
, path = require("path")
@@ -99,7 +99,6 @@ var commandCache = {}
, "update"
, "outdated"
, "prune"
- , "submodule"
, "pack"
, "dedupe"
@@ -424,11 +423,7 @@ Object.defineProperty(npm, "cache",
})
var tmpFolder
-var crypto = require("crypto")
-var rand = crypto.randomBytes(6)
- .toString("base64")
- .replace(/\//g, '_')
- .replace(/\+/, '-')
+var rand = require("crypto").randomBytes(4).toString("hex")
Object.defineProperty(npm, "tmp",
{ get : function () {
if (!tmpFolder) tmpFolder = "npm-" + process.pid + "-" + rand
diff --git a/deps/npm/lib/pack.js b/deps/npm/lib/pack.js
index f955cb7..a5ce900 100644
--- a/deps/npm/lib/pack.js
+++ b/deps/npm/lib/pack.js
@@ -11,6 +11,8 @@ var npm = require("./npm.js")
, chain = require("slide").chain
, path = require("path")
, cwd = process.cwd()
+ , writeStream = require('fs-write-stream-atomic')
+ , cachedPackageRoot = require("./cache/cached-package-root.js")
pack.usage = "npm pack "
@@ -43,17 +45,14 @@ function pack_ (pkg, cb) {
cache.add(pkg, null, null, false, function (er, data) {
if (er) return cb(er)
- var name = data.name
// scoped packages get special treatment
+ var name = data.name
if (name[0] === "@") name = name.substr(1).replace(/\//g, "-")
-
var fname = name + "-" + data.version + ".tgz"
- , cached = path.resolve( npm.cache
- , data.name
- , data.version
- , "package.tgz" )
+
+ var cached = path.join(cachedPackageRoot(data), "package.tgz")
, from = fs.createReadStream(cached)
- , to = fs.createWriteStream(fname)
+ , to = writeStream(fname)
, errState = null
from.on("error", cb_)
diff --git a/deps/npm/lib/publish.js b/deps/npm/lib/publish.js
index 701dc2b..2a0fcff 100644
--- a/deps/npm/lib/publish.js
+++ b/deps/npm/lib/publish.js
@@ -8,9 +8,10 @@ var url = require("url")
, readJson = require("read-package-json")
, lifecycle = require("./utils/lifecycle.js")
, chain = require("slide").chain
- , Conf = require("npmconf").Conf
+ , Conf = require("./config/core.js").Conf
, RegClient = require("npm-registry-client")
, mapToRegistry = require("./utils/map-to-registry.js")
+ , cachedPackageRoot = require("./cache/cached-package-root.js")
publish.usage = "npm publish "
+ "\nnpm publish "
@@ -35,14 +36,18 @@ function publish (args, isRetry, cb) {
var arg = args[0]
// if it's a local folder, then run the prepublish there, first.
readJson(path.resolve(arg, "package.json"), function (er, data) {
- er = needVersion(er, data)
if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
- // error is ok. could be publishing a url or tarball
- // however, that means that we will not have automatically run
- // the prepublish script, since that gets run when adding a folder
- // to the cache.
+
+ if (data) {
+ if (!data.name) return cb(new Error("No name provided"))
+ if (!data.version) return cb(new Error("No version provided"))
+ }
+
+ // Error is OK. Could be publishing a URL or tarball, however, that means
+ // that we will not have automatically run the prepublish script, since
+ // that gets run when adding a folder to the cache.
if (er) return cacheAddPublish(arg, false, isRetry, cb)
- cacheAddPublish(arg, true, isRetry, cb)
+ else cacheAddPublish(arg, true, isRetry, cb)
})
}
@@ -55,10 +60,7 @@ function cacheAddPublish (dir, didPre, isRetry, cb) {
npm.commands.cache.add(dir, null, null, false, function (er, data) {
if (er) return cb(er)
log.silly("publish", data)
- var cachedir = path.resolve( npm.cache
- , data.name
- , data.version
- , "package" )
+ var cachedir = path.resolve(cachedPackageRoot(data), "package")
chain([ !didPre &&
[lifecycle, data, "prepublish", cachedir]
, [publish_, dir, data, isRetry, cachedir]
@@ -88,7 +90,8 @@ function publish_ (arg, data, isRetry, cachedir, cb) {
registry = new RegClient(config)
}
- data._npmVersion = npm.version
+ data._npmVersion = npm.version
+ data._nodeVersion = process.versions.node
delete data.modules
if (data.private) return cb(
@@ -128,9 +131,3 @@ function publish_ (arg, data, isRetry, cachedir, cb) {
})
})
}
-
-function needVersion(er, data) {
- return er ? er
- : (data && !data.version) ? new Error("No version provided")
- : null
-}
diff --git a/deps/npm/lib/run-script.js b/deps/npm/lib/run-script.js
index 6cb7bf7..4495b93 100644
--- a/deps/npm/lib/run-script.js
+++ b/deps/npm/lib/run-script.js
@@ -53,7 +53,10 @@ runScript.completion = function (opts, cb) {
next()
})
- if (npm.config.get("global")) scripts = [], next()
+ if (npm.config.get("global")) {
+ scripts = []
+ next()
+ }
else readJson(path.join(npm.localPrefix, "package.json"), function (er, d) {
if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
d = d || {}
@@ -63,7 +66,8 @@ runScript.completion = function (opts, cb) {
function next () {
if (!installed || !scripts) return
- return cb(null, scripts.concat(installed))
+
+ cb(null, scripts.concat(installed))
}
}
@@ -80,9 +84,9 @@ function runScript (args, cb) {
}
function list(cb) {
- var json = path.join(npm.localPrefix, 'package.json')
+ var json = path.join(npm.localPrefix, "package.json")
return readJson(json, function(er, d) {
- if (er && er.code !== 'ENOENT' && er.code !== 'ENOTDIR') return cb(er)
+ if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
if (er) d = {}
var scripts = Object.keys(d.scripts || {})
@@ -110,22 +114,27 @@ function list(cb) {
}
function run (pkg, wd, cmd, args, cb) {
- var cmds = []
if (!pkg.scripts) pkg.scripts = {}
+
+ var cmds
if (cmd === "restart") {
- cmds = ["prestop","stop","poststop"
- ,"restart"
- ,"prestart","start","poststart"]
+ cmds = [
+ "prestop", "stop", "poststop",
+ "restart",
+ "prestart", "start", "poststart"
+ ]
} else {
cmds = [cmd]
}
+
if (!cmd.match(/^(pre|post)/)) {
cmds = ["pre"+cmd].concat(cmds).concat("post"+cmd)
}
+
log.verbose("run-script", cmds)
chain(cmds.map(function (c) {
// pass cli arguments after -- to script.
- if (pkg.scripts[c]) pkg.scripts[c] = pkg.scripts[c] + joinArgs(args)
+ if (pkg.scripts[c] && c === cmd) pkg.scripts[c] = pkg.scripts[c] + joinArgs(args)
// when running scripts explicitly, assume that they're trusted.
return [lifecycle, pkg, c, wd, true]
@@ -135,10 +144,10 @@ function run (pkg, wd, cmd, args, cb) {
// join arguments after '--' and pass them to script,
// handle special characters such as ', ", ' '.
function joinArgs (args) {
- var joinedArgs = ''
- args.forEach(function(arg, i) {
+ var joinedArgs = ""
+ args.forEach(function(arg) {
if (arg.match(/[ '"]/)) arg = '"' + arg.replace(/"/g, '\\"') + '"'
- joinedArgs += ' ' + arg
+ joinedArgs += " " + arg
})
return joinedArgs
}
diff --git a/deps/npm/lib/search.js b/deps/npm/lib/search.js
index 3be8b0d..5dd060f 100644
--- a/deps/npm/lib/search.js
+++ b/deps/npm/lib/search.js
@@ -218,7 +218,7 @@ function addColorMarker (str, arg, i) {
if (arg.charAt(0) === "/") {
//arg = arg.replace(/\/$/, "")
- return str.replace( new RegExp(arg.substr(1, arg.length - 1), "gi")
+ return str.replace( new RegExp(arg.substr(1, arg.length - 2), "gi")
, function (bit) { return markStart + bit + markEnd } )
}
diff --git a/deps/npm/lib/shrinkwrap.js b/deps/npm/lib/shrinkwrap.js
index 5f8261d..a578383 100644
--- a/deps/npm/lib/shrinkwrap.js
+++ b/deps/npm/lib/shrinkwrap.js
@@ -6,6 +6,7 @@ module.exports = exports = shrinkwrap
var npm = require("./npm.js")
, log = require("npmlog")
, fs = require("fs")
+ , writeFileAtomic = require("write-file-atomic")
, path = require("path")
, readJson = require("read-package-json")
, sortedObject = require("sorted-object")
@@ -70,7 +71,7 @@ function save (pkginfo, silent, cb) {
var file = path.resolve(npm.prefix, "npm-shrinkwrap.json")
- fs.writeFile(file, swdata, function (er) {
+ writeFileAtomic(file, swdata, function (er) {
if (er) return cb(er)
if (silent) return cb(null, pkginfo)
console.log("wrote npm-shrinkwrap.json")
diff --git a/deps/npm/lib/submodule.js b/deps/npm/lib/submodule.js
deleted file mode 100644
index eab4d21..0000000
--- a/deps/npm/lib/submodule.js
+++ /dev/null
@@ -1,90 +0,0 @@
-// npm submodule
-// Check the package contents for a git repository url.
-// If there is one, then create a git submodule in the node_modules folder.
-
-module.exports = submodule
-
-var npm = require("./npm.js")
- , cache = require("./cache.js")
- , git = require("./utils/git.js")
- , asyncMap = require("slide").asyncMap
- , chain = require("slide").chain
-
-submodule.usage = "npm submodule "
-
-submodule.completion = require("./docs.js").completion
-
-function submodule (args, cb) {
- if (npm.config.get("global")) {
- return cb(new Error("Cannot use submodule command in global mode."))
- }
-
- if (args.length === 0) return cb(submodule.usage)
-
- asyncMap(args, function (arg, cb) {
- cache.add(arg, null, null, false, cb)
- }, function (er, pkgs) {
- if (er) return cb(er)
- chain(pkgs.map(function (pkg) { return function (cb) {
- submodule_(pkg, cb)
- }}), cb)
- })
-
-}
-
-function submodule_ (pkg, cb) {
- if (!pkg.repository
- || pkg.repository.type !== "git"
- || !pkg.repository.url) {
- return cb(new Error(pkg._id + ": No git repository listed"))
- }
-
- // prefer https:// github urls
- pkg.repository.url = pkg.repository.url
- .replace(/^(git:\/\/)?(git@)?github.com[:\/]/, "https://github.com/")
-
- // first get the list of submodules, and update if it's already there.
- getSubmodules(function (er, modules) {
- if (er) return cb(er)
- // if there's already a submodule, then just update it.
- if (modules.indexOf(pkg.name) !== -1) {
- return updateSubmodule(pkg.name, cb)
- }
- addSubmodule(pkg.name, pkg.repository.url, cb)
- })
-}
-
-function updateSubmodule (name, cb) {
- var args = [ "submodule", "update", "--init", "node_modules/", name ]
-
- git.whichAndExec(args, cb)
-}
-
-function addSubmodule (name, url, cb) {
- var args = [ "submodule", "add", url, "node_modules/", name ]
-
- git.whichAndExec(args, cb)
-}
-
-
-var getSubmodules = function (cb) {
- var args = [ "submodule", "status" ]
-
-
- git.whichAndExec(args, function _(er, stdout) {
- if (er) return cb(er)
- var res = stdout.trim().split(/\n/).map(function (line) {
- return line.trim().split(/\s+/)[1]
- }).filter(function (line) {
- // only care about submodules in the node_modules folder.
- return line && line.match(/^node_modules\//)
- }).map(function (line) {
- return line.replace(/^node_modules\//g, "")
- })
-
- // memoize.
- getSubmodules = function (cb) { return cb(null, res) }
-
- cb(null, res)
- })
-}
diff --git a/deps/npm/lib/unbuild.js b/deps/npm/lib/unbuild.js
index 7977624..8bd6e85 100644
--- a/deps/npm/lib/unbuild.js
+++ b/deps/npm/lib/unbuild.js
@@ -24,7 +24,7 @@ function unbuild_ (silent) { return function (folder, cb_) {
}
folder = path.resolve(folder)
delete build._didBuild[folder]
- log.verbose(folder.substr(npm.prefix.length + 1), "unbuild")
+ log.verbose("unbuild", folder.substr(npm.prefix.length + 1))
readJson(path.resolve(folder, "package.json"), function (er, pkg) {
// if no json, then just trash it, but no scripts or whatever.
if (er) return gentlyRm(folder, false, cb)
@@ -53,7 +53,8 @@ function rmStuff (pkg, folder, cb) {
readJson.cache.del(path.resolve(folder, "package.json"))
- log.verbose([top, gnm, parent], "unbuild " + pkg._id)
+ log.verbose("unbuild rmStuff", pkg._id, "from", gnm)
+ if (!top) log.verbose("unbuild rmStuff", "in", parent)
asyncMap([rmBins, rmMans], function (fn, cb) {
fn(pkg, folder, parent, top, cb)
}, cb)
diff --git a/deps/npm/lib/uninstall.js b/deps/npm/lib/uninstall.js
index 42a9a83..68869f5 100644
--- a/deps/npm/lib/uninstall.js
+++ b/deps/npm/lib/uninstall.js
@@ -9,6 +9,7 @@ uninstall.usage = "npm uninstall [@ [[@] ...]"
uninstall.completion = require("./utils/completion/installed-shallow.js")
var fs = require("graceful-fs")
+ , writeFileAtomic = require("write-file-atomic")
, log = require("npmlog")
, readJson = require("read-package-json")
, path = require("path")
@@ -120,7 +121,7 @@ function saver (args, nm, cb_) {
}
}
- fs.writeFile(pj, JSON.stringify(pkg, null, 2) + "\n", function (er) {
+ writeFileAtomic(pj, JSON.stringify(pkg, null, 2) + "\n", function (er) {
return cb_(er, data)
})
})
diff --git a/deps/npm/lib/utils/error-handler.js b/deps/npm/lib/utils/error-handler.js
index 788d3f8..95b78a8 100644
--- a/deps/npm/lib/utils/error-handler.js
+++ b/deps/npm/lib/utils/error-handler.js
@@ -11,6 +11,7 @@ var cbCalled = false
, exitCode = 0
, rollbacks = npm.rollbacks
, chain = require("slide").chain
+ , writeStream = require("fs-write-stream-atomic")
process.on("exit", function (code) {
@@ -66,17 +67,21 @@ function exit (code, noLog) {
if (er) {
log.error("error rolling back", er)
if (!code) errorHandler(er)
- else reallyExit(er)
+ else if (noLog) rm("npm-debug.log", reallyExit.bind(null, er))
+ else writeLogFile(reallyExit.bind(this, er))
} else {
- rm("npm-debug.log", reallyExit)
+ if (!noLog && code) writeLogFile(reallyExit)
+ else rm("npm-debug.log", reallyExit)
}
})
rollbacks.length = 0
}
else if (code && !noLog) writeLogFile(reallyExit)
- else reallyExit()
+ else rm("npm-debug.log", reallyExit)
+
+ function reallyExit (er) {
+ if (er && !code) code = typeof er.errno === "number" ? er.errno : 1
- function reallyExit() {
// truncate once it's been written.
log.record.length = 0
@@ -351,8 +356,7 @@ function writeLogFile (cb) {
writingLogFile = true
wroteLogFile = true
- var fs = require("graceful-fs")
- , fstr = fs.createWriteStream("npm-debug.log")
+ var fstr = writeStream("npm-debug.log")
, os = require("os")
, out = ""
diff --git a/deps/npm/lib/utils/git.js b/deps/npm/lib/utils/git.js
index 7e20151..db5cc7b 100644
--- a/deps/npm/lib/utils/git.js
+++ b/deps/npm/lib/utils/git.js
@@ -10,16 +10,20 @@ var exec = require("child_process").execFile
, npm = require("../npm.js")
, which = require("which")
, git = npm.config.get("git")
+ , assert = require("assert")
+ , log = require("npmlog")
function prefixGitArgs() {
return process.platform === "win32" ? ["-c", "core.longpaths=true"] : []
}
function execGit(args, options, cb) {
+ log.info("git", args)
return exec(git, prefixGitArgs().concat(args || []), options, cb)
}
function spawnGit(args, options, cb) {
+ log.info("git", args)
return spawn(git, prefixGitArgs().concat(args || []), options)
}
@@ -33,6 +37,7 @@ function whichGit(cb) {
}
function whichAndExec(args, options, cb) {
+ assert.equal(typeof cb, "function", "no callback provided")
// check for git
whichGit(function (err) {
if (err) {
diff --git a/deps/npm/lib/utils/locker.js b/deps/npm/lib/utils/locker.js
index 9e322d7..4479f24 100644
--- a/deps/npm/lib/utils/locker.js
+++ b/deps/npm/lib/utils/locker.js
@@ -1,52 +1,75 @@
var crypto = require("crypto")
-var path = require("path")
+var resolve = require("path").resolve
-var npm = require("../npm.js")
-var lockFile = require("lockfile")
+var lockfile = require("lockfile")
var log = require("npmlog")
-var getCacheStat = require("../cache/get-stat.js")
-
-function lockFileName (u) {
- var c = u.replace(/[^a-zA-Z0-9]+/g, "-").replace(/^-+|-+$/g, "")
- , h = crypto.createHash("sha1").update(u).digest("hex")
- h = h.substr(0, 8)
- c = c.substr(-32)
- log.silly("lockFile", h + "-" + c, u)
- return path.resolve(npm.config.get("cache"), h + "-" + c + ".lock")
+var mkdirp = require("mkdirp")
+
+var npm = require("../npm.js")
+var getStat = require("../cache/get-stat.js")
+
+var installLocks = {}
+
+function lockFileName (base, name) {
+ var c = name.replace(/[^a-zA-Z0-9]+/g, "-").replace(/^-+|-+$/g, "")
+ , p = resolve(base, name)
+ , h = crypto.createHash("sha1").update(p).digest("hex")
+ , l = resolve(npm.cache, "_locks")
+
+ return resolve(l, c.substr(0, 24)+"-"+h.substr(0, 16)+".lock")
}
-var myLocks = {}
-function lock (u, cb) {
- // the cache dir needs to exist already for this.
- getCacheStat(function (er, cs) {
- if (er) return cb(er)
- var opts = { stale: npm.config.get("cache-lock-stale")
- , retries: npm.config.get("cache-lock-retries")
- , wait: npm.config.get("cache-lock-wait") }
- var lf = lockFileName(u)
- log.verbose("lock", u, lf)
- lockFile.lock(lf, opts, function(er) {
- if (!er) myLocks[lf] = true
- cb(er)
+function lock (base, name, cb) {
+ getStat(function (er) {
+ var lockDir = resolve(npm.cache, "_locks")
+ mkdirp(lockDir, function () {
+ if (er) return cb(er)
+
+ var opts = { stale: npm.config.get("cache-lock-stale")
+ , retries: npm.config.get("cache-lock-retries")
+ , wait: npm.config.get("cache-lock-wait") }
+ var lf = lockFileName(base, name)
+ lockfile.lock(lf, opts, function (er) {
+ if (er) log.warn("locking", lf, "failed", er)
+
+ if (!er) {
+ log.verbose("lock", "using", lf, "for", resolve(base, name))
+ installLocks[lf] = true
+ }
+
+ cb(er)
+ })
})
})
}
-function unlock (u, cb) {
- var lf = lockFileName(u)
- , locked = myLocks[lf]
+function unlock (base, name, cb) {
+ var lf = lockFileName(base, name)
+ , locked = installLocks[lf]
if (locked === false) {
return process.nextTick(cb)
- } else if (locked === true) {
- myLocks[lf] = false
- lockFile.unlock(lockFileName(u), cb)
- } else {
- throw new Error("Attempt to unlock " + u + ", which hasn't been locked")
+ }
+ else if (locked === true) {
+ lockfile.unlock(lf, function (er) {
+ if (er) {
+ log.warn("unlocking", lf, "failed", er)
+ }
+ else {
+ installLocks[lf] = false
+ log.verbose("unlock", "done using", lf, "for", resolve(base, name))
+ }
+
+ cb(er)
+ })
+ }
+ else {
+ throw new Error(
+ "Attempt to unlock " + resolve(base, name) + ", which hasn't been locked"
+ )
}
}
module.exports = {
- lock: lock,
- unlock: unlock,
- _lockFileName: lockFileName
+ lock : lock,
+ unlock : unlock
}
diff --git a/deps/npm/lib/utils/tar.js b/deps/npm/lib/utils/tar.js
index 192de7a..ede49a1 100644
--- a/deps/npm/lib/utils/tar.js
+++ b/deps/npm/lib/utils/tar.js
@@ -3,6 +3,7 @@
var npm = require("../npm.js")
, fs = require("graceful-fs")
+ , writeFileAtomic = require("write-file-atomic")
, path = require("path")
, log = require("npmlog")
, uidNumber = require("uid-number")
@@ -15,15 +16,6 @@ var npm = require("../npm.js")
, fstream = require("fstream")
, Packer = require("fstream-npm")
, lifecycle = require("./lifecycle.js")
- , locker = require("./locker.js")
-
-function lock(path, cb) {
- return locker.lock('tar://' + path, cb)
-}
-
-function unlock(path, cb) {
- return locker.unlock('tar://' + path, cb)
-}
if (process.env.SUDO_UID && myUid === 0) {
if (!isNaN(process.env.SUDO_UID)) myUid = +process.env.SUDO_UID
@@ -51,73 +43,40 @@ function pack (tarball, folder, pkg, dfc, cb) {
}
}
-function pack_ (tarball, folder, pkg, cb_) {
- var tarballLock = false
- , folderLock = false
-
- function cb (er) {
- if (folderLock)
- unlock(folder, function() {
- folderLock = false
- cb(er)
- })
- else if (tarballLock)
- unlock(tarball, function() {
- tarballLock = false
- cb(er)
- })
- else
- cb_(er)
- }
-
- lock(folder, function(er) {
- if (er) return cb(er)
- folderLock = true
- next()
- })
-
- lock(tarball, function (er) {
- if (er) return cb(er)
- tarballLock = true
- next()
- })
-
- function next () {
- if (!tarballLock || !folderLock) return
-
- new Packer({ path: folder, type: "Directory", isDirectory: true })
- .on("error", function (er) {
- if (er) log.error("tar pack", "Error reading " + folder)
- return cb(er)
- })
+function pack_ (tarball, folder, pkg, cb) {
+ new Packer({ path: folder, type: "Directory", isDirectory: true })
+ .on("error", function (er) {
+ if (er) log.error("tar pack", "Error reading " + folder)
+ return cb(er)
+ })
- // By default, npm includes some proprietary attributes in the
- // package tarball. This is sane, and allowed by the spec.
- // However, npm *itself* excludes these from its own package,
- // so that it can be more easily bootstrapped using old and
- // non-compliant tar implementations.
- .pipe(tar.Pack({ noProprietary: !npm.config.get("proprietary-attribs") }))
- .on("error", function (er) {
- if (er) log.error("tar.pack", "tar creation error", tarball)
- cb(er)
- })
- .pipe(zlib.Gzip())
- .on("error", function (er) {
- if (er) log.error("tar.pack", "gzip error "+tarball)
- cb(er)
- })
- .pipe(fstream.Writer({ type: "File", path: tarball }))
- .on("error", function (er) {
- if (er) log.error("tar.pack", "Could not write "+tarball)
- cb(er)
- })
- .on("close", cb)
- }
+ // By default, npm includes some proprietary attributes in the
+ // package tarball. This is sane, and allowed by the spec.
+ // However, npm *itself* excludes these from its own package,
+ // so that it can be more easily bootstrapped using old and
+ // non-compliant tar implementations.
+ .pipe(tar.Pack({ noProprietary: !npm.config.get("proprietary-attribs") }))
+ .on("error", function (er) {
+ if (er) log.error("tar.pack", "tar creation error", tarball)
+ cb(er)
+ })
+ .pipe(zlib.Gzip())
+ .on("error", function (er) {
+ if (er) log.error("tar.pack", "gzip error "+tarball)
+ cb(er)
+ })
+ .pipe(fstream.Writer({ type: "File", path: tarball }))
+ .on("error", function (er) {
+ if (er) log.error("tar.pack", "Could not write "+tarball)
+ cb(er)
+ })
+ .on("close", cb)
}
function unpack (tarball, unpackTarget, dMode, fMode, uid, gid, cb) {
- log.verbose("tar unpack", tarball)
+ log.verbose("tar", "unpack", tarball)
+ log.verbose("tar", "unpacking to", unpackTarget)
if (typeof cb !== "function") cb = gid, gid = null
if (typeof cb !== "function") cb = uid, uid = null
if (typeof cb !== "function") cb = fMode, fMode = npm.modes.file
@@ -129,52 +88,9 @@ function unpack (tarball, unpackTarget, dMode, fMode, uid, gid, cb) {
})
}
-function unpack_ ( tarball, unpackTarget, dMode, fMode, uid, gid, cb_ ) {
- var parent = path.dirname(unpackTarget)
- , base = path.basename(unpackTarget)
- , folderLock
- , tarballLock
-
- function cb (er) {
- if (folderLock)
- unlock(unpackTarget, function() {
- folderLock = false
- cb(er)
- })
- else if (tarballLock)
- unlock(tarball, function() {
- tarballLock = false
- cb(er)
- })
- else
- cb_(er)
- }
-
- lock(unpackTarget, function (er) {
- if (er) return cb(er)
- folderLock = true
- next()
- })
-
- lock(tarball, function (er) {
+function unpack_ ( tarball, unpackTarget, dMode, fMode, uid, gid, cb ) {
+ rm(unpackTarget, function (er) {
if (er) return cb(er)
- tarballLock = true
- next()
- })
-
- function next() {
- if (!tarballLock || !folderLock) return
- rmGunz()
- }
-
- function rmGunz () {
- rm(unpackTarget, function (er) {
- if (er) return cb(er)
- gtp()
- })
- }
-
- function gtp () {
// gzip {tarball} --decompress --stdout \
// | tar -mvxpf - --strip-components=1 -C {unpackTarget}
gunzTarPerm( tarball, unpackTarget
@@ -184,7 +100,7 @@ function unpack_ ( tarball, unpackTarget, dMode, fMode, uid, gid, cb_ ) {
if (er) return cb(er)
readJson(path.resolve(folder, "package.json"), cb)
})
- }
+ })
}
@@ -202,6 +118,17 @@ function gunzTarPerm (tarball, target, dMode, fMode, uid, gid, cb_) {
var fst = fs.createReadStream(tarball)
+ fst.on("open", function (fd) {
+ fs.fstat(fd, function (er, st) {
+ if (er) return fst.emit("error", er)
+ if (st.size === 0) {
+ er = new Error("0-byte tarball\n" +
+ "Please run `npm cache clean`")
+ fst.emit("error", er)
+ }
+ })
+ })
+
// figure out who we're supposed to be, if we're not pretending
// to be a specific user.
if (npm.config.get("unsafe-perm") && process.platform !== "win32") {
@@ -275,73 +202,74 @@ function gunzTarPerm (tarball, target, dMode, fMode, uid, gid, cb_) {
}
- fst.on("error", function (er) {
- if (er) log.error("tar.unpack", "error reading "+tarball)
- cb(er)
- })
- fst.on("data", function OD (c) {
- // detect what it is.
- // Then, depending on that, we'll figure out whether it's
- // a single-file module, gzipped tarball, or naked tarball.
- // gzipped files all start with 1f8b08
- if (c[0] === 0x1F &&
- c[1] === 0x8B &&
- c[2] === 0x08) {
- fst
- .pipe(zlib.Unzip())
- .on("error", function (er) {
- if (er) log.error("tar.unpack", "unzip error "+tarball)
- cb(er)
- })
- .pipe(tar.Extract(extractOpts))
- .on("entry", extractEntry)
- .on("error", function (er) {
- if (er) log.error("tar.unpack", "untar error "+tarball)
- cb(er)
- })
- .on("close", cb)
- } else if (c.toString().match(/^package\//) ||
- c.toString().match(/^pax_global_header/)) {
- // naked tar
- fst
- .pipe(tar.Extract(extractOpts))
- .on("entry", extractEntry)
- .on("error", function (er) {
- if (er) log.error("tar.unpack", "untar error "+tarball)
- cb(er)
- })
- .on("close", cb)
- } else {
- // naked js file
- var jsOpts = { path: path.resolve(target, "index.js") }
-
- if (process.platform !== "win32" &&
- typeof uid === "number" &&
- typeof gid === "number") {
- jsOpts.uid = uid
- jsOpts.gid = gid
- }
+ fst
+ .on("error", function (er) {
+ if (er) log.error("tar.unpack", "error reading "+tarball)
+ cb(er)
+ })
+ .on("data", function OD (c) {
+ // detect what it is.
+ // Then, depending on that, we'll figure out whether it's
+ // a single-file module, gzipped tarball, or naked tarball.
+ // gzipped files all start with 1f8b08
+ if (c[0] === 0x1F &&
+ c[1] === 0x8B &&
+ c[2] === 0x08) {
+ fst
+ .pipe(zlib.Unzip())
+ .on("error", function (er) {
+ if (er) log.error("tar.unpack", "unzip error "+tarball)
+ cb(er)
+ })
+ .pipe(tar.Extract(extractOpts))
+ .on("entry", extractEntry)
+ .on("error", function (er) {
+ if (er) log.error("tar.unpack", "untar error "+tarball)
+ cb(er)
+ })
+ .on("close", cb)
+ } else if (c.toString().match(/^package\//) ||
+ c.toString().match(/^pax_global_header/)) {
+ // naked tar
+ fst
+ .pipe(tar.Extract(extractOpts))
+ .on("entry", extractEntry)
+ .on("error", function (er) {
+ if (er) log.error("tar.unpack", "untar error "+tarball)
+ cb(er)
+ })
+ .on("close", cb)
+ } else {
+ // naked js file
+ var jsOpts = { path: path.resolve(target, "index.js") }
+
+ if (process.platform !== "win32" &&
+ typeof uid === "number" &&
+ typeof gid === "number") {
+ jsOpts.uid = uid
+ jsOpts.gid = gid
+ }
- fst
- .pipe(fstream.Writer(jsOpts))
- .on("error", function (er) {
- if (er) log.error("tar.unpack", "copy error "+tarball)
- cb(er)
- })
- .on("close", function () {
- var j = path.resolve(target, "package.json")
- readJson(j, function (er, d) {
- if (er) {
- log.error("not a package", tarball)
- return cb(er)
- }
- fs.writeFile(j, JSON.stringify(d) + "\n", cb)
+ fst
+ .pipe(fstream.Writer(jsOpts))
+ .on("error", function (er) {
+ if (er) log.error("tar.unpack", "copy error "+tarball)
+ cb(er)
})
- })
- }
+ .on("close", function () {
+ var j = path.resolve(target, "package.json")
+ readJson(j, function (er, d) {
+ if (er) {
+ log.error("not a package", tarball)
+ return cb(er)
+ }
+ writeFileAtomic(j, JSON.stringify(d) + "\n", cb)
+ })
+ })
+ }
- // now un-hook, and re-emit the chunk
- fst.removeListener("data", OD)
- fst.emit("data", c)
- })
+ // now un-hook, and re-emit the chunk
+ fst.removeListener("data", OD)
+ fst.emit("data", c)
+ })
}
diff --git a/deps/npm/lib/version.js b/deps/npm/lib/version.js
index 5091ab9..a15e2c3 100644
--- a/deps/npm/lib/version.js
+++ b/deps/npm/lib/version.js
@@ -6,6 +6,7 @@ var exec = require("child_process").execFile
, semver = require("semver")
, path = require("path")
, fs = require("graceful-fs")
+ , writeFileAtomic = require("write-file-atomic")
, chain = require("slide").chain
, log = require("npmlog")
, which = require("which")
@@ -83,6 +84,15 @@ function checkGit (data, cb) {
// check for git
git.whichAndExec(args, options, function (er, stdout) {
+ if (er && er.code === "ENOGIT") {
+ log.warn(
+ "version",
+ "This is a Git checkout, but the git command was not found.",
+ "npm could not create a Git tag for this release!"
+ )
+ return write(data, cb)
+ }
+
var lines = stdout.trim().split("\n").filter(function (line) {
return line.trim() && !line.match(/^\?\? /)
}).map(function (line) {
@@ -111,7 +121,7 @@ function checkGit (data, cb) {
}
function write (data, cb) {
- fs.writeFile( path.join(npm.localPrefix, "package.json")
+ writeFileAtomic( path.join(npm.localPrefix, "package.json")
, new Buffer(JSON.stringify(data, null, 2) + "\n")
, cb )
}
diff --git a/deps/npm/lib/view.js b/deps/npm/lib/view.js
index 43d09cb..6b45cca 100644
--- a/deps/npm/lib/view.js
+++ b/deps/npm/lib/view.js
@@ -35,11 +35,12 @@ view.completion = function (opts, cb) {
var p = pref.concat(k).join(".")
f.push(p)
if (Array.isArray(d[k])) {
- return d[k].forEach(function (val, i) {
+ d[k].forEach(function (val, i) {
var pi = p + "[" + i + "]"
if (val && typeof val === "object") getFields(val, f, [p])
else f.push(pi)
})
+ return
}
if (typeof d[k] === "object") getFields(d[k], f, [p])
})
@@ -48,24 +49,54 @@ view.completion = function (opts, cb) {
}
var npm = require("./npm.js")
+ , readJson = require("read-package-json")
, registry = npm.registry
, log = require("npmlog")
, util = require("util")
, semver = require("semver")
, mapToRegistry = require("./utils/map-to-registry.js")
, npa = require("npm-package-arg")
+ , path = require("path")
function view (args, silent, cb) {
if (typeof cb !== "function") cb = silent, silent = false
- if (!args.length) return cb("Usage: "+view.usage)
+
+ if (!args.length) args = ["."]
+
var pkg = args.shift()
, nv = npa(pkg)
, name = nv.name
- , version = nv.rawSpec || npm.config.get("tag")
+ , local = (name === "." || !name)
+
+ if (npm.config.get("global") && local) {
+ return cb(new Error("Cannot use view command in global mode."))
+ }
+
+ if (local) {
+ var dir = npm.prefix
+ readJson(path.resolve(dir, "package.json"), function (er, d) {
+ d = d || {}
+ if (er && er.code !== "ENOENT" && er.code !== "ENOTDIR") return cb(er)
+ if (!d.name) return cb(new Error("Invalid package.json"))
- if (name === ".") return cb(view.usage)
+ var p = d.name
+ nv = npa(p)
+ if (pkg && ~pkg.indexOf("@")) {
+ nv.rawSpec = pkg.split("@")[pkg.indexOf("@")]
+ }
+ fetchAndRead(nv, args, silent, cb)
+ })
+ } else {
+ fetchAndRead(nv, args, silent, cb)
+ }
+}
+
+function fetchAndRead (nv, args, silent, cb) {
// get the data about this package
+ var name = nv.name
+ , version = nv.rawSpec || npm.config.get("tag")
+
mapToRegistry(name, npm.config, function (er, uri) {
if (er) return cb(er)
@@ -184,9 +215,7 @@ function search (data, fields, version, title) {
results = results.reduce(reducer, {})
return results
}
- if (!data.hasOwnProperty(field)) {
- return
- }
+ if (!data.hasOwnProperty(field)) return undefined
data = data[field]
if (tail.length) {
if (typeof data === "object") {
@@ -205,15 +234,15 @@ function search (data, fields, version, title) {
function printData (data, name, cb) {
var versions = Object.keys(data)
, msg = ""
- , showVersions = versions.length > 1
- , showFields
+ , includeVersions = versions.length > 1
+ , includeFields
versions.forEach(function (v) {
var fields = Object.keys(data[v])
- showFields = showFields || (fields.length > 1)
+ includeFields = includeFields || (fields.length > 1)
fields.forEach(function (f) {
var d = cleanup(data[v][f])
- if (showVersions || showFields || typeof d !== "string") {
+ if (includeVersions || includeFields || typeof d !== "string") {
d = cleanup(data[v][f])
d = npm.config.get("json")
? JSON.stringify(d, null, 2)
@@ -221,10 +250,10 @@ function printData (data, name, cb) {
} else if (typeof d === "string" && npm.config.get("json")) {
d = JSON.stringify(d)
}
- if (f && showFields) f += " = "
+ if (f && includeFields) f += " = "
if (d.indexOf("\n") !== -1) d = " \n" + d
- msg += (showVersions ? name + "@" + v + " " : "")
- + (showFields ? f : "") + d + "\n"
+ msg += (includeVersions ? name + "@" + v + " " : "")
+ + (includeFields ? f : "") + d + "\n"
})
})
@@ -268,4 +297,3 @@ function unparsePerson (d) {
+ (d.email ? " <"+d.email+">" : "")
+ (d.url ? " ("+d.url+")" : "")
}
-
diff --git a/deps/npm/man/man1/npm-README.1 b/deps/npm/man/man1/npm-README.1
index 8f7d01b..a7cf104 100644
--- a/deps/npm/man/man1/npm-README.1
+++ b/deps/npm/man/man1/npm-README.1
@@ -1,4 +1,4 @@
-.TH "NPM" "1" "September 2014" "" ""
+.TH "NPM" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm\fR \- node package manager
.P
@@ -37,26 +37,26 @@ https://www\.npmjs\.org/install\.sh\|\. You can download that and run it\.
Here's an example using curl:
.P
.RS 2
-.EX
+.nf
curl \-L https://npmjs\.org/install\.sh | sh
-.EE
+.fi
.RE
.SS Slightly Fancier
.P
You can set any npm configuration params with that script:
.P
.RS 2
-.EX
+.nf
npm_config_prefix=/some/path sh install\.sh
-.EE
+.fi
.RE
.P
Or, you can run it in uber\-debuggery mode:
.P
.RS 2
-.EX
+.nf
npm_debug=1 sh install\.sh
-.EE
+.fi
.RE
.SS Even Fancier
.P
@@ -102,9 +102,9 @@ If you would like to ensure that npm \fBalways\fR runs scripts as the
set the following configuration param:
.P
.RS 2
-.EX
+.nf
npm config set unsafe\-perm false
-.EE
+.fi
.RE
.P
This will prevent running in unsafe mode, even as non\-root users\.
@@ -113,17 +113,17 @@ This will prevent running in unsafe mode, even as non\-root users\.
So sad to see you go\.
.P
.RS 2
-.EX
+.nf
sudo npm uninstall npm \-g
-.EE
+.fi
.RE
.P
Or, if that fails,
.P
.RS 2
-.EX
+.nf
sudo make uninstall
-.EE
+.fi
.RE
.SH More Severe Uninstalling
.P
@@ -138,19 +138,19 @@ To remove cruft left behind by npm 0\.x, you can use the included
\fBclean\-old\.sh\fR script file\. You can run it conveniently like this:
.P
.RS 2
-.EX
+.nf
npm explore npm \-g \-\- sh scripts/clean\-old\.sh
-.EE
+.fi
.RE
.P
npm uses two configuration files, one for per\-user configs, and another
for global (every\-user) configs\. You can view them by doing:
.P
.RS 2
-.EX
+.nf
npm config get userconfig # defaults to ~/\.npmrc
npm config get globalconfig # defaults to /usr/local/etc/npmrc
-.EE
+.fi
.RE
.P
Uninstalling npm does not remove configuration files by default\. You
@@ -171,7 +171,7 @@ that it depends on, but for now, there are some things that you must
use npm itself to do\.
.P
.RS 2
-.EX
+.nf
var npm = require("npm")
npm\.load(myConfigObject, function (er) {
if (er) return handlError(er)
@@ -179,9 +179,9 @@ npm\.load(myConfigObject, function (er) {
if (er) return commandFailed(er)
// command succeeded, and data might have some info
})
- npm\.on("log", function (message) { \.\.\.\. })
+ npm\.registry\.log\.on("log", function (message) { \.\.\.\. })
})
-.EE
+.fi
.RE
.P
The \fBload\fR function takes an object hash of the command\-line configs\.
diff --git a/deps/npm/man/man1/npm-adduser.1 b/deps/npm/man/man1/npm-adduser.1
index 5db7ee2..6b85986 100644
--- a/deps/npm/man/man1/npm-adduser.1
+++ b/deps/npm/man/man1/npm-adduser.1
@@ -1,12 +1,12 @@
-.TH "NPM\-ADDUSER" "1" "September 2014" "" ""
+.TH "NPM\-ADDUSER" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-adduser\fR \- Add a registry user account
.SH SYNOPSIS
.P
.RS 2
-.EX
-npm adduser [\-\-registry=url] [\-\-scope=@orgname]
-.EE
+.nf
+npm adduser [\-\-registry=url] [\-\-scope=@orgname] [\-\-always\-auth]
+.fi
.RE
.SH DESCRIPTION
.P
@@ -41,13 +41,31 @@ with the specified scope\. See npm help 7 \fBnpm\-scope\fR\|\. You can use both
e\.g\.
.P
.RS 2
-.EX
+.nf
npm adduser \-\-registry=http://myregistry\.example\.com \-\-scope=@myco
-.EE
+.fi
.RE
.P
This will set a registry for the given scope and login or create a user for
that registry at the same time\.
+.SS always\-auth
+.P
+Default: false
+.P
+If specified, save configuration indicating that all requests to the given
+registry should include authorization information\. Useful for private
+registries\. Can be used with \fB\-\-registry\fR and / or \fB\-\-scope\fR, e\.g\.
+.P
+.RS 2
+.nf
+npm adduser \-\-registry=http://private\-registry\.example\.com \-\-always\-auth
+.fi
+.RE
+.P
+This will ensure that all requests to that registry (including for tarballs)
+include an authorization header\. See \fBalways\-auth\fR in npm help 7 \fBnpm\-config\fR for more
+details on always\-auth\. Registry\-specific configuaration of \fBalways\-auth\fR takes
+precedence over any global configuration\.
.SH SEE ALSO
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man1/npm-bin.1 b/deps/npm/man/man1/npm-bin.1
index b496391..6552d6c 100644
--- a/deps/npm/man/man1/npm-bin.1
+++ b/deps/npm/man/man1/npm-bin.1
@@ -1,12 +1,12 @@
-.TH "NPM\-BIN" "1" "September 2014" "" ""
+.TH "NPM\-BIN" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-bin\fR \- Display npm bin folder
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm bin
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-bugs.1 b/deps/npm/man/man1/npm-bugs.1
index 67c0a61..09c7659 100644
--- a/deps/npm/man/man1/npm-bugs.1
+++ b/deps/npm/man/man1/npm-bugs.1
@@ -1,13 +1,13 @@
-.TH "NPM\-BUGS" "1" "September 2014" "" ""
+.TH "NPM\-BUGS" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-bugs\fR \- Bugs for a package in a web browser maybe
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm bugs
npm bugs (with no args in a package dir)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-build.1 b/deps/npm/man/man1/npm-build.1
index ed530b3..0f21842 100644
--- a/deps/npm/man/man1/npm-build.1
+++ b/deps/npm/man/man1/npm-build.1
@@ -1,12 +1,12 @@
-.TH "NPM\-BUILD" "1" "September 2014" "" ""
+.TH "NPM\-BUILD" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-build\fR \- Build a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm build
-.EE
+.fi
.RE
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man1/npm-bundle.1 b/deps/npm/man/man1/npm-bundle.1
index 7a8355d..0748922 100644
--- a/deps/npm/man/man1/npm-bundle.1
+++ b/deps/npm/man/man1/npm-bundle.1
@@ -1,4 +1,4 @@
-.TH "NPM\-BUNDLE" "1" "September 2014" "" ""
+.TH "NPM\-BUNDLE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-bundle\fR \- REMOVED
.SH DESCRIPTION
diff --git a/deps/npm/man/man1/npm-cache.1 b/deps/npm/man/man1/npm-cache.1
index 5a99d11..c49015a 100644
--- a/deps/npm/man/man1/npm-cache.1
+++ b/deps/npm/man/man1/npm-cache.1
@@ -1,10 +1,10 @@
-.TH "NPM\-CACHE" "1" "September 2014" "" ""
+.TH "NPM\-CACHE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-cache\fR \- Manipulates packages cache
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm cache add
npm cache add
npm cache add
@@ -13,7 +13,7 @@ npm cache add @
npm cache ls []
npm cache clean []
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-completion.1 b/deps/npm/man/man1/npm-completion.1
index bbd224f..a89cc6f 100644
--- a/deps/npm/man/man1/npm-completion.1
+++ b/deps/npm/man/man1/npm-completion.1
@@ -1,12 +1,12 @@
-.TH "NPM\-COMPLETION" "1" "September 2014" "" ""
+.TH "NPM\-COMPLETION" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-completion\fR \- Tab Completion for npm
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
\|\. <(npm completion)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-config.1 b/deps/npm/man/man1/npm-config.1
index ca7d69d..a93ebac 100644
--- a/deps/npm/man/man1/npm-config.1
+++ b/deps/npm/man/man1/npm-config.1
@@ -1,10 +1,10 @@
-.TH "NPM\-CONFIG" "1" "September 2014" "" ""
+.TH "NPM\-CONFIG" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-config\fR \- Manage the npm configuration files
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm config set [\-\-global]
npm config get
npm config delete
@@ -13,7 +13,7 @@ npm config edit
npm c [set|get|delete|list]
npm get
npm set [\-\-global]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -33,9 +33,9 @@ Config supports the following sub\-commands:
.SS set
.P
.RS 2
-.EX
+.nf
npm config set key value
-.EE
+.fi
.RE
.P
Sets the config key to the value\.
@@ -44,36 +44,36 @@ If value is omitted, then it sets it to "true"\.
.SS get
.P
.RS 2
-.EX
+.nf
npm config get key
-.EE
+.fi
.RE
.P
Echo the config value to stdout\.
.SS list
.P
.RS 2
-.EX
+.nf
npm config list
-.EE
+.fi
.RE
.P
Show all the config settings\.
.SS delete
.P
.RS 2
-.EX
+.nf
npm config delete key
-.EE
+.fi
.RE
.P
Deletes the key from all configuration files\.
.SS edit
.P
.RS 2
-.EX
+.nf
npm config edit
-.EE
+.fi
.RE
.P
Opens the config file in an editor\. Use the \fB\-\-global\fR flag to edit the
diff --git a/deps/npm/man/man1/npm-dedupe.1 b/deps/npm/man/man1/npm-dedupe.1
index 58c01ca..2454807 100644
--- a/deps/npm/man/man1/npm-dedupe.1
+++ b/deps/npm/man/man1/npm-dedupe.1
@@ -1,13 +1,13 @@
-.TH "NPM\-DEDUPE" "1" "September 2014" "" ""
+.TH "NPM\-DEDUPE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-dedupe\fR \- Reduce duplication
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm dedupe [package names\.\.\.]
npm ddp [package names\.\.\.]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -18,24 +18,24 @@ be more effectively shared by multiple dependent packages\.
For example, consider this dependency graph:
.P
.RS 2
-.EX
+.nf
a
+\-\- b <\-\- depends on c@1\.0\.x
| `\-\- c@1\.0\.3
`\-\- d <\-\- depends on c@~1\.0\.9
`\-\- c@1\.0\.10
-.EE
+.fi
.RE
.P
In this case, npm help \fBnpm\-dedupe\fR will transform the tree to:
.P
.RS 2
-.EX
+.nf
a
+\-\- b
+\-\- d
`\-\- c@1\.0\.10
-.EE
+.fi
.RE
.P
Because of the hierarchical nature of node's module lookup, b and d
diff --git a/deps/npm/man/man1/npm-deprecate.1 b/deps/npm/man/man1/npm-deprecate.1
index 3ff2f88..581a589 100644
--- a/deps/npm/man/man1/npm-deprecate.1
+++ b/deps/npm/man/man1/npm-deprecate.1
@@ -1,12 +1,12 @@
-.TH "NPM\-DEPRECATE" "1" "September 2014" "" ""
+.TH "NPM\-DEPRECATE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-deprecate\fR \- Deprecate a version of a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm deprecate [@]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -17,9 +17,9 @@ It works on version ranges as well as specific versions, so you can do
something like this:
.P
.RS 2
-.EX
+.nf
npm deprecate my\-thing@"< 0\.2\.3" "critical bug fixed in v0\.2\.3"
-.EE
+.fi
.RE
.P
Note that you must be the package owner to deprecate something\. See the
diff --git a/deps/npm/man/man1/npm-docs.1 b/deps/npm/man/man1/npm-docs.1
index 0a55953..1e9e5c1 100644
--- a/deps/npm/man/man1/npm-docs.1
+++ b/deps/npm/man/man1/npm-docs.1
@@ -1,15 +1,15 @@
-.TH "NPM\-DOCS" "1" "September 2014" "" ""
+.TH "NPM\-DOCS" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-docs\fR \- Docs for a package in a web browser maybe
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm docs [ [ \.\.\.]]
npm docs (with no args in a package dir)
npm home [ [ \.\.\.]]
npm home (with no args in a package dir)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-edit.1 b/deps/npm/man/man1/npm-edit.1
index d7f4056..8a19d12 100644
--- a/deps/npm/man/man1/npm-edit.1
+++ b/deps/npm/man/man1/npm-edit.1
@@ -1,12 +1,12 @@
-.TH "NPM\-EDIT" "1" "September 2014" "" ""
+.TH "NPM\-EDIT" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-edit\fR \- Edit an installed package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm edit [@]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-explore.1 b/deps/npm/man/man1/npm-explore.1
index 01f91bf..0211aef 100644
--- a/deps/npm/man/man1/npm-explore.1
+++ b/deps/npm/man/man1/npm-explore.1
@@ -1,12 +1,12 @@
-.TH "NPM\-EXPLORE" "1" "September 2014" "" ""
+.TH "NPM\-EXPLORE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-explore\fR \- Browse an installed package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm explore [ \-\- ]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -19,9 +19,9 @@ This is particularly handy in the case of git submodules in the
\fBnode_modules\fR folder:
.P
.RS 2
-.EX
+.nf
npm explore some\-dependency \-\- git pull origin master
-.EE
+.fi
.RE
.P
Note that the package is \fInot\fR automatically rebuilt afterwards, so be
@@ -41,8 +41,6 @@ The shell to run for the \fBnpm explore\fR command\.
.SH SEE ALSO
.RS 0
.IP \(bu 2
-npm help submodule
-.IP \(bu 2
npm help 5 folders
.IP \(bu 2
npm help edit
diff --git a/deps/npm/man/man1/npm-help-search.1 b/deps/npm/man/man1/npm-help-search.1
index 7886469..a18a8e9 100644
--- a/deps/npm/man/man1/npm-help-search.1
+++ b/deps/npm/man/man1/npm-help-search.1
@@ -1,12 +1,12 @@
-.TH "NPM\-HELP\-SEARCH" "1" "September 2014" "" ""
+.TH "NPM\-HELP\-SEARCH" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-help-search\fR \- Search npm help documentation
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm help\-search some search terms
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-help.1 b/deps/npm/man/man1/npm-help.1
index b0456ef..556eeb5 100644
--- a/deps/npm/man/man1/npm-help.1
+++ b/deps/npm/man/man1/npm-help.1
@@ -1,13 +1,13 @@
-.TH "NPM\-HELP" "1" "September 2014" "" ""
+.TH "NPM\-HELP" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-help\fR \- Get help on npm
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm help
npm help some search terms
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-init.1 b/deps/npm/man/man1/npm-init.1
index 93e3845..3d4ed09 100644
--- a/deps/npm/man/man1/npm-init.1
+++ b/deps/npm/man/man1/npm-init.1
@@ -1,12 +1,12 @@
-.TH "NPM\-INIT" "1" "September 2014" "" ""
+.TH "NPM\-INIT" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-init\fR \- Interactively create a package\.json file
.SH SYNOPSIS
.P
.RS 2
-.EX
-npm init
-.EE
+.nf
+npm init [\-f|\-\-force|\-y|\-\-yes]
+.fi
.RE
.SH DESCRIPTION
.P
@@ -20,6 +20,9 @@ the options in there\.
.P
It is strictly additive, so it does not delete options from your package\.json
without a really good reason to do so\.
+.P
+If you invoke it with \fB\-f\fR, \fB\-\-force\fR, \fB\-y\fR, or \fB\-\-yes\fR, it will use only
+defaults and not prompt you for any options\.
.SH SEE ALSO
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man1/npm-install.1 b/deps/npm/man/man1/npm-install.1
index ad6bdf5..0df0197 100644
--- a/deps/npm/man/man1/npm-install.1
+++ b/deps/npm/man/man1/npm-install.1
@@ -1,10 +1,10 @@
-.TH "NPM\-INSTALL" "1" "September 2014" "" ""
+.TH "NPM\-INSTALL" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-install\fR \- Install a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm install (with no args in a package dir)
npm install
npm install
@@ -14,7 +14,7 @@ npm install [@/]@
npm install [@/]@
npm install [@/]@
npm i (with any of the previous argument usage)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -66,9 +66,9 @@ after packing it up into a tarball (b)\.
Example:
.P
.RS 2
-.EX
+.nf
npm install \./package\.tgz
-.EE
+.fi
.RE
.IP \(bu 2
\fBnpm install \fR:
@@ -77,9 +77,9 @@ after packing it up into a tarball (b)\.
Example:
.P
.RS 2
-.EX
+.nf
npm install https://github\.com/indexzero/forever/tarball/v0\.5\.6
-.EE
+.fi
.RE
.IP \(bu 2
\fBnpm install [@/] [\-\-save|\-\-save\-dev|\-\-save\-optional]\fR:
@@ -90,9 +90,9 @@ after packing it up into a tarball (b)\.
Example:
.P
.RS 2
-.EX
+.nf
npm install sax
-.EE
+.fi
.RE
\fBnpm install\fR takes 3 exclusive, optional flags which save or update
the package version in your main package\.json:
@@ -118,14 +118,14 @@ must also be followed by a slash\.
Examples:
.P
.RS 2
-.EX
+.nf
npm install sax \-\-save
npm install githubname/reponame
npm install @myorg/privatepackage
npm install node\-tap \-\-save\-dev
npm install dtrace\-provider \-\-save\-optional
npm install readable\-stream \-\-save \-\-save\-exact
-.EE
+.fi
.RE
.RE
@@ -133,11 +133,11 @@ npm install readable\-stream \-\-save \-\-save\-exact
.RE
.P
.RS 2
-.EX
+.nf
**Note**: If there is a file or folder named `` in the current
working directory, then it will try to install that, and only try to
fetch the package by name if it is not valid\.
-.EE
+.fi
.RE
.RS 0
.IP \(bu 2
@@ -148,10 +148,10 @@ fetch the package by name if it is not valid\.
Example:
.P
.RS 2
-.EX
+.nf
npm install sax@latest
npm install @myorg/mypackage@latest
-.EE
+.fi
.RE
.IP \(bu 2
\fBnpm install [@/]@\fR:
@@ -160,10 +160,10 @@ fetch the package by name if it is not valid\.
Example:
.P
.RS 2
-.EX
+.nf
npm install sax@0\.1\.1
npm install @myorg/privatepackage@1\.5\.0
-.EE
+.fi
.RE
.IP \(bu 2
\fBnpm install [@/]@\fR:
@@ -174,10 +174,10 @@ fetch the package by name if it is not valid\.
Example:
.P
.RS 2
-.EX
+.nf
npm install sax@">=0\.1\.0 <0\.2\.0"
npm install @myorg/privatepackage@">=0\.1\.0 <0\.2\.0"
-.EE
+.fi
.RE
.IP \(bu 2
\fBnpm install /\fR:
@@ -186,9 +186,9 @@ fetch the package by name if it is not valid\.
Example:
.P
.RS 2
-.EX
+.nf
npm install mygithubuser/myproject
-.EE
+.fi
.RE
To reference a package in a git repo that is not on GitHub, see git
remote urls below\.
@@ -198,9 +198,9 @@ fetch the package by name if it is not valid\.
url is:
.P
.RS 2
-.EX
+.nf
://[@][#]
-.EE
+.fi
.RE
\fB\fR is one of \fBgit\fR, \fBgit+ssh\fR, \fBgit+http\fR, or
\fBgit+https\fR\|\. If no \fB\fR is specified, then \fBmaster\fR is
@@ -208,11 +208,11 @@ fetch the package by name if it is not valid\.
Examples:
.P
.RS 2
-.EX
+.nf
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
-.EE
+.fi
.RE
.RE
@@ -221,9 +221,9 @@ You may combine multiple arguments, and even multiple types of arguments\.
For example:
.P
.RS 2
-.EX
+.nf
npm install sax@">=0\.1\.0 <0\.2\.0" bench supervisor
-.EE
+.fi
.RE
.P
The \fB\-\-tag\fR argument will apply to all of the specified install targets\. If a
@@ -234,9 +234,9 @@ The \fB\-\-force\fR argument will force npm to fetch remote resources even if a
local copy exists on disk\.
.P
.RS 2
-.EX
+.nf
npm install sax \-\-force
-.EE
+.fi
.RE
.P
The \fB\-\-global\fR argument will cause npm to install the package globally
@@ -264,7 +264,7 @@ effect on installation, since that's most of what npm does\.
To install a package, npm uses the following algorithm:
.P
.RS 2
-.EX
+.nf
install(where, what, family, ancestors)
fetch what, unpack to /node_modules/
for each dep in what\.dependencies
@@ -274,19 +274,19 @@ for each dep@version in what\.dependencies
and not in
add precise version deps to
install(/node_modules/, dep, family)
-.EE
+.fi
.RE
.P
For this \fBpackage{dep}\fR structure: \fBA{B,C}, B{C}, C{D}\fR,
this algorithm produces:
.P
.RS 2
-.EX
+.nf
A
+\-\- B
`\-\- C
`\-\- D
-.EE
+.fi
.RE
.P
That is, the dependency from B to C is satisfied by the fact that A
@@ -301,9 +301,9 @@ cause npm to try to install a never\-ending tree of packages\. Here is
the simplest case:
.P
.RS 2
-.EX
+.nf
A \-> B \-> A' \-> B' \-> A \-> B \-> A' \-> B' \-> A \-> \.\.\.
-.EE
+.fi
.RE
.P
where \fBA\fR is some version of a package, and \fBA'\fR is a different version
diff --git a/deps/npm/man/man1/npm-link.1 b/deps/npm/man/man1/npm-link.1
index 11ef2dc..62d7650 100644
--- a/deps/npm/man/man1/npm-link.1
+++ b/deps/npm/man/man1/npm-link.1
@@ -1,14 +1,14 @@
-.TH "NPM\-LINK" "1" "September 2014" "" ""
+.TH "NPM\-LINK" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-link\fR \- Symlink a package folder
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm link (in package folder)
npm link [@/]
npm ln (with any of the previous argument usage)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -36,12 +36,12 @@ test it iteratively without having to continually rebuild\.
For example:
.P
.RS 2
-.EX
+.nf
cd ~/projects/node\-redis # go into the package directory
npm link # creates global link
cd ~/projects/node\-bloggy # go into some other package directory\.
npm link redis # link\-install the package
-.EE
+.fi
.RE
.P
Now, any changes to ~/projects/node\-redis will be reflected in
@@ -51,19 +51,19 @@ You may also shortcut the two steps in one\. For example, to do the
above use\-case in a shorter way:
.P
.RS 2
-.EX
+.nf
cd ~/projects/node\-bloggy # go into the dir of your main project
npm link \.\./node\-redis # link the dir of your dependency
-.EE
+.fi
.RE
.P
The second line is the equivalent of doing:
.P
.RS 2
-.EX
+.nf
(cd \.\./node\-redis; npm link)
npm link redis
-.EE
+.fi
.RE
.P
That is, it first creates a global link, and then links the global
@@ -73,9 +73,9 @@ If your linked package is scoped (see npm help 7 \fBnpm\-scope\fR) your link com
include that scope, e\.g\.
.P
.RS 2
-.EX
+.nf
npm link @myorg/privatepackage
-.EE
+.fi
.RE
.SH SEE ALSO
.RS 0
diff --git a/deps/npm/man/man1/npm-ls.1 b/deps/npm/man/man1/npm-ls.1
index 64db5a4..9cf4823 100644
--- a/deps/npm/man/man1/npm-ls.1
+++ b/deps/npm/man/man1/npm-ls.1
@@ -1,15 +1,15 @@
-.TH "NPM\-LS" "1" "September 2014" "" ""
+.TH "NPM\-LS" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-ls\fR \- List installed packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm list [[@/] \.\.\.]
npm ls [[@/] \.\.\.]
npm la [[@/] \.\.\.]
npm ll [[@/] \.\.\.]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -22,11 +22,11 @@ nested packages will \fIalso\fR show the paths to the specified packages\.
For example, running \fBnpm ls promzard\fR in npm's source tree will show:
.P
.RS 2
-.EX
-npm@2.0.0 /path/to/npm
+.nf
+npm@2.1.6 /path/to/npm
ââ⬠init\-package\-json@0\.0\.4
âââ promzard@0\.1\.5
-.EE
+.fi
.RE
.P
It will print out extraneous, missing, and invalid packages\.
diff --git a/deps/npm/man/man1/npm-outdated.1 b/deps/npm/man/man1/npm-outdated.1
index 589bd6d..45433a8 100644
--- a/deps/npm/man/man1/npm-outdated.1
+++ b/deps/npm/man/man1/npm-outdated.1
@@ -1,12 +1,12 @@
-.TH "NPM\-OUTDATED" "1" "September 2014" "" ""
+.TH "NPM\-OUTDATED" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-outdated\fR \- Check for outdated packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm outdated [ [ \.\.\.]]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-owner.1 b/deps/npm/man/man1/npm-owner.1
index c073a8b..3ed5549 100644
--- a/deps/npm/man/man1/npm-owner.1
+++ b/deps/npm/man/man1/npm-owner.1
@@ -1,14 +1,14 @@
-.TH "NPM\-OWNER" "1" "September 2014" "" ""
+.TH "NPM\-OWNER" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-owner\fR \- Manage package owners
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm owner ls
npm owner add
npm owner rm
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-pack.1 b/deps/npm/man/man1/npm-pack.1
index e90f378..8b9408a 100644
--- a/deps/npm/man/man1/npm-pack.1
+++ b/deps/npm/man/man1/npm-pack.1
@@ -1,12 +1,12 @@
-.TH "NPM\-PACK" "1" "September 2014" "" ""
+.TH "NPM\-PACK" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-pack\fR \- Create a tarball from a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm pack [ [ \.\.\.]]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-prefix.1 b/deps/npm/man/man1/npm-prefix.1
index 373f5e4..b7bcac6 100644
--- a/deps/npm/man/man1/npm-prefix.1
+++ b/deps/npm/man/man1/npm-prefix.1
@@ -1,12 +1,12 @@
-.TH "NPM\-PREFIX" "1" "September 2014" "" ""
+.TH "NPM\-PREFIX" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-prefix\fR \- Display prefix
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm prefix [\-g]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-prune.1 b/deps/npm/man/man1/npm-prune.1
index 3c8a66a..1a8cc95 100644
--- a/deps/npm/man/man1/npm-prune.1
+++ b/deps/npm/man/man1/npm-prune.1
@@ -1,13 +1,13 @@
-.TH "NPM\-PRUNE" "1" "September 2014" "" ""
+.TH "NPM\-PRUNE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-prune\fR \- Remove extraneous packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm prune [ [ [ [\-\-tag ]
npm publish [\-\-tag ]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
-Publishes a package to the registry so that it can be installed by name\.
+Publishes a package to the registry so that it can be installed by name\. See
+npm help 7 \fBnpm\-developers\fR for details on what's included in the published package, as
+well as details on how the package is built\.
.P
By default npm will publish to the public registry\. This can be overridden by
specifying a different default registry or using a npm help 7 \fBnpm\-scope\fR in the name
diff --git a/deps/npm/man/man1/npm-rebuild.1 b/deps/npm/man/man1/npm-rebuild.1
index f8d52a9..0e04b9c 100644
--- a/deps/npm/man/man1/npm-rebuild.1
+++ b/deps/npm/man/man1/npm-rebuild.1
@@ -1,13 +1,13 @@
-.TH "NPM\-REBUILD" "1" "September 2014" "" ""
+.TH "NPM\-REBUILD" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-rebuild\fR \- Rebuild a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm rebuild [ [ \.\.\.]]
npm rb [ [ \.\.\.]]
-.EE
+.fi
.RE
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man1/npm-repo.1 b/deps/npm/man/man1/npm-repo.1
index 57c48fb..dc8428d 100644
--- a/deps/npm/man/man1/npm-repo.1
+++ b/deps/npm/man/man1/npm-repo.1
@@ -1,13 +1,13 @@
-.TH "NPM\-REPO" "1" "September 2014" "" ""
+.TH "NPM\-REPO" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-repo\fR \- Open package repository page in the browser
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm repo
npm repo (with no args in a package dir)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-restart.1 b/deps/npm/man/man1/npm-restart.1
index a4f95db..234d0aa 100644
--- a/deps/npm/man/man1/npm-restart.1
+++ b/deps/npm/man/man1/npm-restart.1
@@ -1,20 +1,17 @@
-.TH "NPM\-RESTART" "1" "September 2014" "" ""
+.TH "NPM\-RESTART" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-restart\fR \- Start a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm restart [\-\- ]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
-This runs a package's "restart" script, if one was provided\.
-Otherwise it runs package's "stop" script, if one was provided, and then
-the "start" script\.
-.P
-If no version is specified, then it restarts the "active" version\.
+This runs a package's "restart" script, if one was provided\. Otherwise it runs
+package's "stop" script, if one was provided, and then the "start" script\.
.SH SEE ALSO
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man1/npm-rm.1 b/deps/npm/man/man1/npm-rm.1
index e9df0ff..c7f92fb 100644
--- a/deps/npm/man/man1/npm-rm.1
+++ b/deps/npm/man/man1/npm-rm.1
@@ -1,15 +1,15 @@
-.TH "NPM\-RM" "1" "September 2014" "" ""
+.TH "NPM\-RM" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-rm\fR \- Remove a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm rm
npm r
npm uninstall
npm un
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-root.1 b/deps/npm/man/man1/npm-root.1
index b80a855..f85ebb9 100644
--- a/deps/npm/man/man1/npm-root.1
+++ b/deps/npm/man/man1/npm-root.1
@@ -1,12 +1,12 @@
-.TH "NPM\-ROOT" "1" "September 2014" "" ""
+.TH "NPM\-ROOT" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-root\fR \- Display npm root
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm root
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-run-script.1 b/deps/npm/man/man1/npm-run-script.1
index 7ee4fc7..905908a 100644
--- a/deps/npm/man/man1/npm-run-script.1
+++ b/deps/npm/man/man1/npm-run-script.1
@@ -1,13 +1,13 @@
-.TH "NPM\-RUN\-SCRIPT" "1" "September 2014" "" ""
+.TH "NPM\-RUN\-SCRIPT" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-run-script\fR \- Run arbitrary package scripts
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm run\-script [command] [\-\- ]
npm run [command] [\-\- ]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -18,6 +18,20 @@ is provided, it will list the available top level scripts\.
.P
It is used by the test, start, restart, and stop commands, but can be
called directly, as well\.
+.P
+As of \fBnpm@2\.0\.0\fR \fIhttp://blog\.npmjs\.org/post/98131109725/npm\-2\-0\-0\fR, you can
+use custom arguments when executing scripts\. The special option \fB\-\-\fR is used by
+getopt \fIhttp://goo\.gl/KxMmtG\fR to delimit the end of the options\. npm will pass
+all the arguments after the \fB\-\-\fR directly to your script:
+.P
+.RS 2
+.nf
+npm run test \-\- \-\-grep="pattern"
+.fi
+.RE
+.P
+The arguments will only be passed to the script specified after \fBnpm run\fR
+and not to any pre or post script\.
.SH SEE ALSO
.RS 0
.IP \(bu 2
diff --git a/deps/npm/man/man1/npm-search.1 b/deps/npm/man/man1/npm-search.1
index 16b3fa4..4ad5a67 100644
--- a/deps/npm/man/man1/npm-search.1
+++ b/deps/npm/man/man1/npm-search.1
@@ -1,14 +1,14 @@
-.TH "NPM\-SEARCH" "1" "September 2014" "" ""
+.TH "NPM\-SEARCH" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-search\fR \- Search for packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm search [\-\-long] [search terms \.\.\.]
npm s [search terms \.\.\.]
npm se [search terms \.\.\.]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-shrinkwrap.1 b/deps/npm/man/man1/npm-shrinkwrap.1
index e154851..fa2b313 100644
--- a/deps/npm/man/man1/npm-shrinkwrap.1
+++ b/deps/npm/man/man1/npm-shrinkwrap.1
@@ -1,12 +1,12 @@
-.TH "NPM\-SHRINKWRAP" "1" "September 2014" "" ""
+.TH "NPM\-SHRINKWRAP" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-shrinkwrap\fR \- Lock down dependency versions
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm shrinkwrap
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -31,7 +31,7 @@ but that may be undesirable for other reasons\.
As an example, consider package A:
.P
.RS 2
-.EX
+.nf
{
"name": "A",
"version": "0\.1\.0",
@@ -39,13 +39,13 @@ As an example, consider package A:
"B": "<0\.1\.0"
}
}
-.EE
+.fi
.RE
.P
package B:
.P
.RS 2
-.EX
+.nf
{
"name": "B",
"version": "0\.0\.1",
@@ -53,40 +53,40 @@ package B:
"C": "<0\.1\.0"
}
}
-.EE
+.fi
.RE
.P
and package C:
.P
.RS 2
-.EX
+.nf
{
"name": "C,
"version": "0\.0\.1"
}
-.EE
+.fi
.RE
.P
If these are the only versions of A, B, and C available in the
registry, then a normal "npm install A" will install:
.P
.RS 2
-.EX
+.nf
A@0\.1\.0
`\-\- B@0\.0\.1
`\-\- C@0\.0\.1
-.EE
+.fi
.RE
.P
However, if B@0\.0\.2 is published, then a fresh "npm install A" will
install:
.P
.RS 2
-.EX
+.nf
A@0\.1\.0
`\-\- B@0\.0\.2
`\-\- C@0\.0\.1
-.EE
+.fi
.RE
.P
assuming the new version did not modify B's dependencies\. Of course,
@@ -100,15 +100,15 @@ when B hasn't changed at all\.
In this case, A's author can run
.P
.RS 2
-.EX
+.nf
npm shrinkwrap
-.EE
+.fi
.RE
.P
This generates npm\-shrinkwrap\.json, which will look something like this:
.P
.RS 2
-.EX
+.nf
{
"name": "A",
"version": "0\.1\.0",
@@ -123,7 +123,7 @@ This generates npm\-shrinkwrap\.json, which will look something like this:
}
}
}
-.EE
+.fi
.RE
.P
The shrinkwrap command has locked down the dependencies based on
diff --git a/deps/npm/man/man1/npm-star.1 b/deps/npm/man/man1/npm-star.1
index 211225b..8dbc029 100644
--- a/deps/npm/man/man1/npm-star.1
+++ b/deps/npm/man/man1/npm-star.1
@@ -1,13 +1,13 @@
-.TH "NPM\-STAR" "1" "September 2014" "" ""
+.TH "NPM\-STAR" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-star\fR \- Mark your favorite packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm star [, \.\.\.]
npm unstar [, \.\.\.]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-stars.1 b/deps/npm/man/man1/npm-stars.1
index 455cf4f..1762a0f 100644
--- a/deps/npm/man/man1/npm-stars.1
+++ b/deps/npm/man/man1/npm-stars.1
@@ -1,13 +1,13 @@
-.TH "NPM\-STARS" "1" "September 2014" "" ""
+.TH "NPM\-STARS" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-stars\fR \- View packages marked as favorites
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm stars
npm stars [username]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-start.1 b/deps/npm/man/man1/npm-start.1
index 866cfd3..0a342ee 100644
--- a/deps/npm/man/man1/npm-start.1
+++ b/deps/npm/man/man1/npm-start.1
@@ -1,12 +1,12 @@
-.TH "NPM\-START" "1" "September 2014" "" ""
+.TH "NPM\-START" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-start\fR \- Start a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm start [\-\- ]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-stop.1 b/deps/npm/man/man1/npm-stop.1
index 1c4a6a6..8622d18 100644
--- a/deps/npm/man/man1/npm-stop.1
+++ b/deps/npm/man/man1/npm-stop.1
@@ -1,12 +1,12 @@
-.TH "NPM\-STOP" "1" "September 2014" "" ""
+.TH "NPM\-STOP" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-stop\fR \- Stop a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm stop [\-\- ]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-submodule.1 b/deps/npm/man/man1/npm-submodule.1
index bfb210d..4999ac6 100644
--- a/deps/npm/man/man1/npm-submodule.1
+++ b/deps/npm/man/man1/npm-submodule.1
@@ -1,12 +1,12 @@
-.TH "NPM\-SUBMODULE" "1" "September 2014" "" ""
+.TH "NPM\-SUBMODULE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-submodule\fR \- Add a package as a git submodule
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm submodule
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-tag.1 b/deps/npm/man/man1/npm-tag.1
index 03fdbdb..5aace75 100644
--- a/deps/npm/man/man1/npm-tag.1
+++ b/deps/npm/man/man1/npm-tag.1
@@ -1,12 +1,12 @@
-.TH "NPM\-TAG" "1" "September 2014" "" ""
+.TH "NPM\-TAG" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-tag\fR \- Tag a published version
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm tag @ []
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -17,17 +17,17 @@ A tag can be used when installing packages as a reference to a version instead
of using a specific version number:
.P
.RS 2
-.EX
+.nf
npm install @
-.EE
+.fi
.RE
.P
When installing dependencies, a preferred tagged version may be specified:
.P
.RS 2
-.EX
+.nf
npm install \-\-tag
-.EE
+.fi
.RE
.P
This also applies to \fBnpm dedupe\fR\|\.
diff --git a/deps/npm/man/man1/npm-test.1 b/deps/npm/man/man1/npm-test.1
index 8e92115..0b4a9f4 100644
--- a/deps/npm/man/man1/npm-test.1
+++ b/deps/npm/man/man1/npm-test.1
@@ -1,13 +1,13 @@
-.TH "NPM\-TEST" "1" "September 2014" "" ""
+.TH "NPM\-TEST" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-test\fR \- Test a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm test [\-\- ]
npm tst [\-\- ]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-uninstall.1 b/deps/npm/man/man1/npm-uninstall.1
index 2ade4ac..a56f8bb 100644
--- a/deps/npm/man/man1/npm-uninstall.1
+++ b/deps/npm/man/man1/npm-uninstall.1
@@ -1,13 +1,13 @@
-.TH "NPM\-RM" "1" "September 2014" "" ""
+.TH "NPM\-RM" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-rm\fR \- Remove a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm uninstall [@/] [\-\-save|\-\-save\-dev|\-\-save\-optional]
npm rm (with any of the previous argument usage)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -17,9 +17,9 @@ on its behalf\.
Example:
.P
.RS 2
-.EX
+.nf
npm uninstall sax
-.EE
+.fi
.RE
.P
In global mode (ie, with \fB\-g\fR or \fB\-\-global\fR appended to the command),
@@ -42,12 +42,12 @@ Scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fR\|\
Examples:
.P
.RS 2
-.EX
+.nf
npm uninstall sax \-\-save
npm uninstall @myorg/privatepackage \-\-save
npm uninstall node\-tap \-\-save\-dev
npm uninstall dtrace\-provider \-\-save\-optional
-.EE
+.fi
.RE
.SH SEE ALSO
.RS 0
diff --git a/deps/npm/man/man1/npm-unpublish.1 b/deps/npm/man/man1/npm-unpublish.1
index 9aec754..6cb1df7 100644
--- a/deps/npm/man/man1/npm-unpublish.1
+++ b/deps/npm/man/man1/npm-unpublish.1
@@ -1,12 +1,12 @@
-.TH "NPM\-UNPUBLISH" "1" "September 2014" "" ""
+.TH "NPM\-UNPUBLISH" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-unpublish\fR \- Remove a package from the registry
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm unpublish [@/][@]
-.EE
+.fi
.RE
.SH WARNING
.P
diff --git a/deps/npm/man/man1/npm-update.1 b/deps/npm/man/man1/npm-update.1
index 4edfab3..19adfc9 100644
--- a/deps/npm/man/man1/npm-update.1
+++ b/deps/npm/man/man1/npm-update.1
@@ -1,12 +1,12 @@
-.TH "NPM\-UPDATE" "1" "September 2014" "" ""
+.TH "NPM\-UPDATE" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-update\fR \- Update a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm update [\-g] [ [ \.\.\.]]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm-version.1 b/deps/npm/man/man1/npm-version.1
index 5c05aab..21fde34 100644
--- a/deps/npm/man/man1/npm-version.1
+++ b/deps/npm/man/man1/npm-version.1
@@ -1,12 +1,12 @@
-.TH "NPM\-VERSION" "1" "September 2014" "" ""
+.TH "NPM\-VERSION" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-version\fR \- Bump a package version
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm version [ | major | minor | patch | premajor | preminor | prepatch | prerelease]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -27,9 +27,9 @@ use it as a commit message when creating a version commit\. If the
resulting version number\. For example:
.P
.RS 2
-.EX
+.nf
npm version patch \-m "Upgrade to %s for reasons"
-.EE
+.fi
.RE
.P
If the \fBsign\-git\-tag\fR config is set, then the tag will be signed using
@@ -37,7 +37,7 @@ the \fB\-s\fR flag to git\. Note that you must have a default GPG key set up
in your git config for this to work properly\. For example:
.P
.RS 2
-.EX
+.nf
$ npm config set sign\-git\-tag true
$ npm version patch
@@ -46,7 +46,7 @@ user: "isaacs (http://blog\.izs\.me/) "
2048\-bit RSA key, ID 6C481CF6, created 2010\-08\-31
Enter passphrase:
-.EE
+.fi
.RE
.SH SEE ALSO
.RS 0
diff --git a/deps/npm/man/man1/npm-view.1 b/deps/npm/man/man1/npm-view.1
index af435f0..35ef045 100644
--- a/deps/npm/man/man1/npm-view.1
+++ b/deps/npm/man/man1/npm-view.1
@@ -1,13 +1,13 @@
-.TH "NPM\-VIEW" "1" "September 2014" "" ""
+.TH "NPM\-VIEW" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-view\fR \- View registry info
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm view [@/][@] [[\.]\.\.\.]
npm v [@/][@] [[\.]\.\.\.]
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -18,9 +18,9 @@ To show the package registry entry for the \fBconnect\fR package, you can do
this:
.P
.RS 2
-.EX
+.nf
npm view connect
-.EE
+.fi
.RE
.P
The default version is "latest" if unspecified\.
@@ -30,9 +30,9 @@ For example, to show the dependencies of the \fBronn\fR package at version
0\.3\.5, you could do the following:
.P
.RS 2
-.EX
+.nf
npm view ronn@0\.3\.5 dependencies
-.EE
+.fi
.RE
.P
You can view child field by separating them with a period\.
@@ -40,9 +40,9 @@ To view the git repository URL for the latest version of npm, you could
do this:
.P
.RS 2
-.EX
+.nf
npm view npm repository\.url
-.EE
+.fi
.RE
.P
This makes it easy to view information about a dependency with a bit of
@@ -50,9 +50,9 @@ shell scripting\. For example, to view all the data about the version of
opts that ronn depends on, you can do this:
.P
.RS 2
-.EX
+.nf
npm view opts@$(npm view ronn dependencies\.opts)
-.EE
+.fi
.RE
.P
For fields that are arrays, requesting a non\-numeric field will return
@@ -60,9 +60,9 @@ all of the values from the objects in the list\. For example, to get all
the contributor names for the "express" project, you can do this:
.P
.RS 2
-.EX
+.nf
npm view express contributors\.email
-.EE
+.fi
.RE
.P
You may also use numeric indices in square braces to specifically select
@@ -70,9 +70,9 @@ an item in an array field\. To just get the email address of the first
contributor in the list, you can do this:
.P
.RS 2
-.EX
+.nf
npm view express contributors[0]\.email
-.EE
+.fi
.RE
.P
Multiple fields may be specified, and will be printed one after another\.
@@ -80,9 +80,9 @@ For exampls, to get all the contributor names and email addresses, you
can do this:
.P
.RS 2
-.EX
+.nf
npm view express contributors\.name contributors\.email
-.EE
+.fi
.RE
.P
"Person" fields are shown as a string if they would be shown as an
@@ -90,9 +90,9 @@ object\. So, for example, this will show the list of npm contributors in
the shortened string format\. (See npm help 5 \fBpackage\.json\fR for more on this\.)
.P
.RS 2
-.EX
+.nf
npm view npm contributors
-.EE
+.fi
.RE
.P
If a version range is provided, then data will be printed for every
@@ -100,9 +100,9 @@ matching version of the package\. This will show which version of jsdom
was required by each matching version of yui3:
.P
.RS 2
-.EX
+.nf
npm view yui3@'>0\.5\.4' dependencies\.jsdom
-.EE
+.fi
.RE
.SH OUTPUT
.P
diff --git a/deps/npm/man/man1/npm-whoami.1 b/deps/npm/man/man1/npm-whoami.1
index 0d44c8b..34a3f04 100644
--- a/deps/npm/man/man1/npm-whoami.1
+++ b/deps/npm/man/man1/npm-whoami.1
@@ -1,12 +1,12 @@
-.TH "NPM\-WHOAMI" "1" "September 2014" "" ""
+.TH "NPM\-WHOAMI" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-whoami\fR \- Display npm username
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm whoami
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man1/npm.1 b/deps/npm/man/man1/npm.1
index a44acfe..a275e47 100644
--- a/deps/npm/man/man1/npm.1
+++ b/deps/npm/man/man1/npm.1
@@ -1,16 +1,16 @@
-.TH "NPM" "1" "September 2014" "" ""
+.TH "NPM" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm\fR \- node package manager
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm [args]
-.EE
+.fi
.RE
.SH VERSION
.P
-2.0.0
+2.1.6
.SH DESCRIPTION
.P
npm is the package manager for the Node JavaScript platform\. It puts
diff --git a/deps/npm/man/man3/npm-bin.3 b/deps/npm/man/man3/npm-bin.3
index 704b17c..4c76b8a 100644
--- a/deps/npm/man/man3/npm-bin.3
+++ b/deps/npm/man/man3/npm-bin.3
@@ -1,17 +1,17 @@
-.TH "NPM\-BIN" "3" "September 2014" "" ""
+.TH "NPM\-BIN" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-bin\fR \- Display npm bin folder
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.bin(args, cb)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
Print the folder where npm will install executables\.
.P
This function should not be used programmatically\. Instead, just refer
-to the \fBnpm\.bin\fR member\.
+to the \fBnpm\.bin\fR property\.
diff --git a/deps/npm/man/man3/npm-bugs.3 b/deps/npm/man/man3/npm-bugs.3
index c0809e6..cd8dda6 100644
--- a/deps/npm/man/man3/npm-bugs.3
+++ b/deps/npm/man/man3/npm-bugs.3
@@ -1,12 +1,12 @@
-.TH "NPM\-BUGS" "3" "September 2014" "" ""
+.TH "NPM\-BUGS" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-bugs\fR \- Bugs for a package in a web browser maybe
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.bugs(package, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-cache.3 b/deps/npm/man/man3/npm-cache.3
index 125fcf7..1dccd8f 100644
--- a/deps/npm/man/man3/npm-cache.3
+++ b/deps/npm/man/man3/npm-cache.3
@@ -1,17 +1,17 @@
-.TH "NPM\-CACHE" "3" "September 2014" "" ""
+.TH "NPM\-CACHE" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-cache\fR \- manage the npm cache programmatically
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.cache([args], callback)
// helpers
npm\.commands\.cache\.clean([args], callback)
npm\.commands\.cache\.add([args], callback)
npm\.commands\.cache\.read(name, version, forceBypass, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-commands.3 b/deps/npm/man/man3/npm-commands.3
index 396b1c7..87ad325 100644
--- a/deps/npm/man/man3/npm-commands.3
+++ b/deps/npm/man/man3/npm-commands.3
@@ -1,12 +1,12 @@
-.TH "NPM\-COMMANDS" "3" "September 2014" "" ""
+.TH "NPM\-COMMANDS" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-commands\fR \- npm commands
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands[](args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-config.3 b/deps/npm/man/man3/npm-config.3
index 0e8e364..763e225 100644
--- a/deps/npm/man/man3/npm-config.3
+++ b/deps/npm/man/man3/npm-config.3
@@ -1,14 +1,14 @@
-.TH "NPM\-CONFIG" "3" "September 2014" "" ""
+.TH "NPM\-CONFIG" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-config\fR \- Manage the npm configuration files
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.config(args, callback)
var val = npm\.config\.get(key)
npm\.config\.set(key, val)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-deprecate.3 b/deps/npm/man/man3/npm-deprecate.3
index ba5ffbd..9b543d3 100644
--- a/deps/npm/man/man3/npm-deprecate.3
+++ b/deps/npm/man/man3/npm-deprecate.3
@@ -1,12 +1,12 @@
-.TH "NPM\-DEPRECATE" "3" "September 2014" "" ""
+.TH "NPM\-DEPRECATE" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-deprecate\fR \- Deprecate a version of a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.deprecate(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-docs.3 b/deps/npm/man/man3/npm-docs.3
index 6aec6d7..ad93e30 100644
--- a/deps/npm/man/man3/npm-docs.3
+++ b/deps/npm/man/man3/npm-docs.3
@@ -1,12 +1,12 @@
-.TH "NPM\-DOCS" "3" "September 2014" "" ""
+.TH "NPM\-DOCS" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-docs\fR \- Docs for a package in a web browser maybe
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.docs(package, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-edit.3 b/deps/npm/man/man3/npm-edit.3
index 0c52d96..82767c8 100644
--- a/deps/npm/man/man3/npm-edit.3
+++ b/deps/npm/man/man3/npm-edit.3
@@ -1,12 +1,12 @@
-.TH "NPM\-EDIT" "3" "September 2014" "" ""
+.TH "NPM\-EDIT" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-edit\fR \- Edit an installed package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.edit(package, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-explore.3 b/deps/npm/man/man3/npm-explore.3
index 8b0cb72..54948ea 100644
--- a/deps/npm/man/man3/npm-explore.3
+++ b/deps/npm/man/man3/npm-explore.3
@@ -1,12 +1,12 @@
-.TH "NPM\-EXPLORE" "3" "September 2014" "" ""
+.TH "NPM\-EXPLORE" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-explore\fR \- Browse an installed package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.explore(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-help-search.3 b/deps/npm/man/man3/npm-help-search.3
index 8b92f90..8f4f346 100644
--- a/deps/npm/man/man3/npm-help-search.3
+++ b/deps/npm/man/man3/npm-help-search.3
@@ -1,12 +1,12 @@
-.TH "NPM\-HELP\-SEARCH" "3" "September 2014" "" ""
+.TH "NPM\-HELP\-SEARCH" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-help-search\fR \- Search the help pages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.helpSearch(args, [silent,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -37,5 +37,5 @@ Name of the file that matched
.RE
.P
-The silent parameter is not neccessary not used, but it may in the future\.
+The silent parameter is not necessary not used, but it may in the future\.
diff --git a/deps/npm/man/man3/npm-init.3 b/deps/npm/man/man3/npm-init.3
index 87059d9..d5da00d 100644
--- a/deps/npm/man/man3/npm-init.3
+++ b/deps/npm/man/man3/npm-init.3
@@ -1,12 +1,12 @@
-.TH "NPM" "" "September 2014" "" ""
+.TH "NPM" "" "October 2014" "" ""
.SH "NAME"
\fBnpm\fR
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.init(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-install.3 b/deps/npm/man/man3/npm-install.3
index 3202bdf..ec98278 100644
--- a/deps/npm/man/man3/npm-install.3
+++ b/deps/npm/man/man3/npm-install.3
@@ -1,12 +1,12 @@
-.TH "NPM\-INSTALL" "3" "September 2014" "" ""
+.TH "NPM\-INSTALL" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-install\fR \- install a package programmatically
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.install([where,] packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-link.3 b/deps/npm/man/man3/npm-link.3
index ff5ea0f..0c379a4 100644
--- a/deps/npm/man/man3/npm-link.3
+++ b/deps/npm/man/man3/npm-link.3
@@ -1,13 +1,13 @@
-.TH "NPM\-LINK" "3" "September 2014" "" ""
+.TH "NPM\-LINK" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-link\fR \- Symlink a package folder
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.link(callback)
npm\.commands\.link(packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -29,11 +29,11 @@ iteratively without having to continually rebuild\.
For example:
.P
.RS 2
-.EX
+.nf
npm\.commands\.link(cb) # creates global link from the cwd
# (say redis package)
npm\.commands\.link('redis', cb) # link\-install the package
-.EE
+.fi
.RE
.P
Now, any changes to the redis package will be reflected in
diff --git a/deps/npm/man/man3/npm-load.3 b/deps/npm/man/man3/npm-load.3
index 8189b5a..61fac42 100644
--- a/deps/npm/man/man3/npm-load.3
+++ b/deps/npm/man/man3/npm-load.3
@@ -1,21 +1,21 @@
-.TH "NPM\-LOAD" "3" "September 2014" "" ""
+.TH "NPM\-LOAD" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-load\fR \- Load config settings
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.load(conf, cb)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
npm\.load() must be called before any other function call\. Both parameters are
optional, but the second is recommended\.
.P
-The first parameter is an object hash of command\-line config params, and the
-second parameter is a callback that will be called when npm is loaded and
-ready to serve\.
+The first parameter is an object containing command\-line config params, and the
+second parameter is a callback that will be called when npm is loaded and ready
+to serve\.
.P
The first parameter should follow a similar structure as the package\.json
config object\.
@@ -23,11 +23,11 @@ config object\.
For example, to emulate the \-\-dev flag, pass an object that looks like this:
.P
.RS 2
-.EX
+.nf
{
"dev": true
}
-.EE
+.fi
.RE
.P
For a list of all the available command\-line configs, see \fBnpm help config\fR
diff --git a/deps/npm/man/man3/npm-ls.3 b/deps/npm/man/man3/npm-ls.3
index a8ce7f7..84558ab 100644
--- a/deps/npm/man/man3/npm-ls.3
+++ b/deps/npm/man/man3/npm-ls.3
@@ -1,12 +1,12 @@
-.TH "NPM\-LS" "3" "September 2014" "" ""
+.TH "NPM\-LS" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-ls\fR \- List installed packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.ls(args, [silent,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-outdated.3 b/deps/npm/man/man3/npm-outdated.3
index ac653f9..2bba846 100644
--- a/deps/npm/man/man3/npm-outdated.3
+++ b/deps/npm/man/man3/npm-outdated.3
@@ -1,12 +1,12 @@
-.TH "NPM\-OUTDATED" "3" "September 2014" "" ""
+.TH "NPM\-OUTDATED" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-outdated\fR \- Check for outdated packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.outdated([packages,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-owner.3 b/deps/npm/man/man3/npm-owner.3
index ac4ad14..101b752 100644
--- a/deps/npm/man/man3/npm-owner.3
+++ b/deps/npm/man/man3/npm-owner.3
@@ -1,12 +1,12 @@
-.TH "NPM\-OWNER" "3" "September 2014" "" ""
+.TH "NPM\-OWNER" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-owner\fR \- Manage package owners
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.owner(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-pack.3 b/deps/npm/man/man3/npm-pack.3
index 07b6399..d9da93e 100644
--- a/deps/npm/man/man3/npm-pack.3
+++ b/deps/npm/man/man3/npm-pack.3
@@ -1,12 +1,12 @@
-.TH "NPM\-PACK" "3" "September 2014" "" ""
+.TH "NPM\-PACK" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-pack\fR \- Create a tarball from a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.pack([packages,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-prefix.3 b/deps/npm/man/man3/npm-prefix.3
index d83aea1..e2da6d6 100644
--- a/deps/npm/man/man3/npm-prefix.3
+++ b/deps/npm/man/man3/npm-prefix.3
@@ -1,12 +1,12 @@
-.TH "NPM\-PREFIX" "3" "September 2014" "" ""
+.TH "NPM\-PREFIX" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-prefix\fR \- Display prefix
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.prefix(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-prune.3 b/deps/npm/man/man3/npm-prune.3
index 7ad7ebc..48a06c9 100644
--- a/deps/npm/man/man3/npm-prune.3
+++ b/deps/npm/man/man3/npm-prune.3
@@ -1,12 +1,12 @@
-.TH "NPM\-PRUNE" "3" "September 2014" "" ""
+.TH "NPM\-PRUNE" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-prune\fR \- Remove extraneous packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.prune([packages,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-publish.3 b/deps/npm/man/man3/npm-publish.3
index 877ab41..13dbd95 100644
--- a/deps/npm/man/man3/npm-publish.3
+++ b/deps/npm/man/man3/npm-publish.3
@@ -1,12 +1,12 @@
-.TH "NPM\-PUBLISH" "3" "September 2014" "" ""
+.TH "NPM\-PUBLISH" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-publish\fR \- Publish a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.publish([packages,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-rebuild.3 b/deps/npm/man/man3/npm-rebuild.3
index 1a0387f..21a5aba 100644
--- a/deps/npm/man/man3/npm-rebuild.3
+++ b/deps/npm/man/man3/npm-rebuild.3
@@ -1,12 +1,12 @@
-.TH "NPM\-REBUILD" "3" "September 2014" "" ""
+.TH "NPM\-REBUILD" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-rebuild\fR \- Rebuild a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.rebuild([packages,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-repo.3 b/deps/npm/man/man3/npm-repo.3
index e889528..5638d43 100644
--- a/deps/npm/man/man3/npm-repo.3
+++ b/deps/npm/man/man3/npm-repo.3
@@ -1,12 +1,12 @@
-.TH "NPM\-REPO" "3" "September 2014" "" ""
+.TH "NPM\-REPO" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-repo\fR \- Open package repository page in the browser
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.repo(package, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-restart.3 b/deps/npm/man/man3/npm-restart.3
index 9085436..be94833 100644
--- a/deps/npm/man/man3/npm-restart.3
+++ b/deps/npm/man/man3/npm-restart.3
@@ -1,12 +1,12 @@
-.TH "NPM\-RESTART" "3" "September 2014" "" ""
+.TH "NPM\-RESTART" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-restart\fR \- Start a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.restart(packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-root.3 b/deps/npm/man/man3/npm-root.3
index 36ce001..68bac79 100644
--- a/deps/npm/man/man3/npm-root.3
+++ b/deps/npm/man/man3/npm-root.3
@@ -1,12 +1,12 @@
-.TH "NPM\-ROOT" "3" "September 2014" "" ""
+.TH "NPM\-ROOT" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-root\fR \- Display npm root
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.root(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-run-script.3 b/deps/npm/man/man3/npm-run-script.3
index 2ec3a67..866f1e0 100644
--- a/deps/npm/man/man3/npm-run-script.3
+++ b/deps/npm/man/man3/npm-run-script.3
@@ -1,12 +1,12 @@
-.TH "NPM\-RUN\-SCRIPT" "3" "September 2014" "" ""
+.TH "NPM\-RUN\-SCRIPT" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-run-script\fR \- Run arbitrary package scripts
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.run\-script(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-search.3 b/deps/npm/man/man3/npm-search.3
index e508a01..ba0cc5f 100644
--- a/deps/npm/man/man3/npm-search.3
+++ b/deps/npm/man/man3/npm-search.3
@@ -1,12 +1,12 @@
-.TH "NPM\-SEARCH" "3" "September 2014" "" ""
+.TH "NPM\-SEARCH" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-search\fR \- Search for packages
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.search(searchTerms, [silent,] [staleness,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-shrinkwrap.3 b/deps/npm/man/man3/npm-shrinkwrap.3
index d7e4ba8..0f87c50 100644
--- a/deps/npm/man/man3/npm-shrinkwrap.3
+++ b/deps/npm/man/man3/npm-shrinkwrap.3
@@ -1,12 +1,12 @@
-.TH "NPM\-SHRINKWRAP" "3" "September 2014" "" ""
+.TH "NPM\-SHRINKWRAP" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-shrinkwrap\fR \- programmatically generate package shrinkwrap file
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.shrinkwrap(args, [silent,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-start.3 b/deps/npm/man/man3/npm-start.3
index 7942fbd..4eabb36 100644
--- a/deps/npm/man/man3/npm-start.3
+++ b/deps/npm/man/man3/npm-start.3
@@ -1,12 +1,12 @@
-.TH "NPM\-START" "3" "September 2014" "" ""
+.TH "NPM\-START" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-start\fR \- Start a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.start(packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-stop.3 b/deps/npm/man/man3/npm-stop.3
index b7d2d6d..aa55b84 100644
--- a/deps/npm/man/man3/npm-stop.3
+++ b/deps/npm/man/man3/npm-stop.3
@@ -1,12 +1,12 @@
-.TH "NPM\-STOP" "3" "September 2014" "" ""
+.TH "NPM\-STOP" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-stop\fR \- Stop a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.stop(packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-submodule.3 b/deps/npm/man/man3/npm-submodule.3
index 7ade6d2..378862a 100644
--- a/deps/npm/man/man3/npm-submodule.3
+++ b/deps/npm/man/man3/npm-submodule.3
@@ -1,12 +1,12 @@
-.TH "NPM\-SUBMODULE" "3" "September 2014" "" ""
+.TH "NPM\-SUBMODULE" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-submodule\fR \- Add a package as a git submodule
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.submodule(packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-tag.3 b/deps/npm/man/man3/npm-tag.3
index a6d3476..4da1376 100644
--- a/deps/npm/man/man3/npm-tag.3
+++ b/deps/npm/man/man3/npm-tag.3
@@ -1,12 +1,12 @@
-.TH "NPM\-TAG" "3" "September 2014" "" ""
+.TH "NPM\-TAG" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-tag\fR \- Tag a published version
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.tag(package@version, tag, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-test.3 b/deps/npm/man/man3/npm-test.3
index 02f4de0..f6d0f6d 100644
--- a/deps/npm/man/man3/npm-test.3
+++ b/deps/npm/man/man3/npm-test.3
@@ -1,12 +1,12 @@
-.TH "NPM\-TEST" "3" "September 2014" "" ""
+.TH "NPM\-TEST" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-test\fR \- Test a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.test(packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-uninstall.3 b/deps/npm/man/man3/npm-uninstall.3
index 883deaf..8505f39 100644
--- a/deps/npm/man/man3/npm-uninstall.3
+++ b/deps/npm/man/man3/npm-uninstall.3
@@ -1,12 +1,12 @@
-.TH "NPM\-UNINSTALL" "3" "September 2014" "" ""
+.TH "NPM\-UNINSTALL" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-uninstall\fR \- uninstall a package programmatically
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.uninstall(packages, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-unpublish.3 b/deps/npm/man/man3/npm-unpublish.3
index 8420247..9b4ab46 100644
--- a/deps/npm/man/man3/npm-unpublish.3
+++ b/deps/npm/man/man3/npm-unpublish.3
@@ -1,12 +1,12 @@
-.TH "NPM\-UNPUBLISH" "3" "September 2014" "" ""
+.TH "NPM\-UNPUBLISH" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-unpublish\fR \- Remove a package from the registry
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.unpublish(package, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-update.3 b/deps/npm/man/man3/npm-update.3
index 55fb3d1..3f40eb0 100644
--- a/deps/npm/man/man3/npm-update.3
+++ b/deps/npm/man/man3/npm-update.3
@@ -1,14 +1,14 @@
-.TH "NPM\-UPDATE" "3" "September 2014" "" ""
+.TH "NPM\-UPDATE" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-update\fR \- Update a package
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.update(packages, callback)
-.EE
+.fi
.RE
-.TH "DESCRIPTION" "" "September 2014" "" ""
+.TH "DESCRIPTION" "" "October 2014" "" ""
.SH "NAME"
\fBDESCRIPTION\fR
.P
diff --git a/deps/npm/man/man3/npm-version.3 b/deps/npm/man/man3/npm-version.3
index 0cbf79c..1697924 100644
--- a/deps/npm/man/man3/npm-version.3
+++ b/deps/npm/man/man3/npm-version.3
@@ -1,12 +1,12 @@
-.TH "NPM\-VERSION" "3" "September 2014" "" ""
+.TH "NPM\-VERSION" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-version\fR \- Bump a package version
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.version(newversion, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm-view.3 b/deps/npm/man/man3/npm-view.3
index 2201f54..e49f28d 100644
--- a/deps/npm/man/man3/npm-view.3
+++ b/deps/npm/man/man3/npm-view.3
@@ -1,12 +1,12 @@
-.TH "NPM\-VIEW" "3" "September 2014" "" ""
+.TH "NPM\-VIEW" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-view\fR \- View registry info
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(args, [silent,] callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
@@ -25,9 +25,9 @@ For example, to get the package registry entry for the \fBconnect\fR package,
you can do this:
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["connect"], callback)
-.EE
+.fi
.RE
.P
If no version is specified, "latest" is assumed\.
@@ -37,9 +37,9 @@ For example, to show the dependencies of the \fBronn\fR package at version
0\.3\.5, you could do the following:
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["ronn@0\.3\.5", "dependencies"], callback)
-.EE
+.fi
.RE
.P
You can view child field by separating them with a period\.
@@ -47,9 +47,9 @@ To view the git repository URL for the latest version of npm, you could
do this:
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["npm", "repository\.url"], callback)
-.EE
+.fi
.RE
.P
For fields that are arrays, requesting a non\-numeric field will return
@@ -57,9 +57,9 @@ all of the values from the objects in the list\. For example, to get all
the contributor names for the "express" project, you can do this:
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["express", "contributors\.email"], callback)
-.EE
+.fi
.RE
.P
You may also use numeric indices in square braces to specifically select
@@ -67,9 +67,9 @@ an item in an array field\. To just get the email address of the first
contributor in the list, you can do this:
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["express", "contributors[0]\.email"], callback)
-.EE
+.fi
.RE
.P
Multiple fields may be specified, and will be printed one after another\.
@@ -77,9 +77,9 @@ For exampls, to get all the contributor names and email addresses, you
can do this:
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["express", "contributors\.name", "contributors\.email"], callback)
-.EE
+.fi
.RE
.P
"Person" fields are shown as a string if they would be shown as an
@@ -87,9 +87,9 @@ object\. So, for example, this will show the list of npm contributors in
the shortened string format\. (See \fBnpm help json\fR for more on this\.)
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["npm", "contributors"], callback)
-.EE
+.fi
.RE
.P
If a version range is provided, then data will be printed for every
@@ -97,9 +97,9 @@ matching version of the package\. This will show which version of jsdom
was required by each matching version of yui3:
.P
.RS 2
-.EX
+.nf
npm\.commands\.view(["yui3@'>0\.5\.4'", "dependencies\.jsdom"], callback)
-.EE
+.fi
.RE
.SH OUTPUT
.P
@@ -119,12 +119,12 @@ Console output can be disabled by setting the 'silent' parameter to true\.
The data returned will be an object in this formation:
.P
.RS 2
-.EX
+.nf
{ :
{ :
, \.\.\. }
, \.\.\. }
-.EE
+.fi
.RE
.P
corresponding to the list of fields selected\.
diff --git a/deps/npm/man/man3/npm-whoami.3 b/deps/npm/man/man3/npm-whoami.3
index 272d6b1..2d32507 100644
--- a/deps/npm/man/man3/npm-whoami.3
+++ b/deps/npm/man/man3/npm-whoami.3
@@ -1,12 +1,12 @@
-.TH "NPM\-WHOAMI" "3" "September 2014" "" ""
+.TH "NPM\-WHOAMI" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm-whoami\fR \- Display npm username
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
npm\.commands\.whoami(args, callback)
-.EE
+.fi
.RE
.SH DESCRIPTION
.P
diff --git a/deps/npm/man/man3/npm.3 b/deps/npm/man/man3/npm.3
index 41103a0..71bbc58 100644
--- a/deps/npm/man/man3/npm.3
+++ b/deps/npm/man/man3/npm.3
@@ -1,10 +1,10 @@
-.TH "NPM" "3" "September 2014" "" ""
+.TH "NPM" "3" "October 2014" "" ""
.SH "NAME"
\fBnpm\fR \- node package manager
.SH SYNOPSIS
.P
.RS 2
-.EX
+.nf
var npm = require("npm")
npm\.load([configObject, ]function (er, npm) {
// use the npm object, now that it's loaded\.
@@ -16,24 +16,23 @@ npm\.load([configObject, ]function (er, npm) {
npm\.commands\.install(["package"], cb)
})
-.EE
+.fi
.RE
.SH VERSION
.P
-2.0.0
+2.1.6
.SH DESCRIPTION
.P
This is the API documentation for npm\.
To find documentation of the command line
client, see npm help \fBnpm\fR\|\.
.P
-Prior to using npm's commands, \fBnpm\.load()\fR must be called\.
-If you provide \fBconfigObject\fR as an object hash of top\-level
-configs, they override the values stored in the various config
-locations\. In the npm command line client, this set of configs
-is parsed from the command line options\. Additional configuration
-params are loaded from two configuration files\. See npm help \fBnpm\-config\fR,
-npm help 7 \fBnpm\-config\fR, and npm help 5 \fBnpmrc\fR for more information\.
+Prior to using npm's commands, \fBnpm\.load()\fR must be called\. If you provide
+\fBconfigObject\fR as an object map of top\-level configs, they override the values
+stored in the various config locations\. In the npm command line client, this
+set of configs is parsed from the command line options\. Additional
+configuration params are loaded from two configuration files\. See
+npm help \fBnpm\-config\fR, npm help 7 \fBnpm\-config\fR, and npm help 5 \fBnpmrc\fR for more information\.
.P
After that, each of the functions are accessible in the
commands object: \fBnpm\.commands\.\fR\|\. See npm help 7 \fBnpm\-index\fR for a list of
@@ -89,9 +88,9 @@ command\.
.RE
.SH MAGIC
.P
-For each of the methods in the \fBnpm\.commands\fR hash, a method is added to
-the npm object, which takes a set of positional string arguments rather
-than an array and a callback\.
+For each of the methods in the \fBnpm\.commands\fR object, a method is added to the
+npm object, which takes a set of positional string arguments rather than an
+array and a callback\.
.P
If the last argument is a callback, then it will use the supplied
callback\. However, if no callback is provided, then it will print out
@@ -100,11 +99,11 @@ the error or results\.
For example, this would work in a node repl:
.P
.RS 2
-.EX
+.nf
> npm = require("npm")
> npm\.load() // wait a sec\.\.\.
> npm\.install("dnode", "express")
-.EE
+.fi
.RE
.P
Note that that \fIwon't\fR work in a node program, since the \fBinstall\fR
@@ -118,8 +117,8 @@ method names\. Use the \fBnpm\.deref\fR method to find the real name\.
For example:
.P
.RS 2
-.EX
+.nf
var cmd = npm\.deref("unp") // cmd === "unpublish"
-.EE
+.fi
.RE
diff --git a/deps/npm/man/man5/npm-folders.5 b/deps/npm/man/man5/npm-folders.5
index 4f4d2cc..9cd3436 100644
--- a/deps/npm/man/man5/npm-folders.5
+++ b/deps/npm/man/man5/npm-folders.5
@@ -1,4 +1,4 @@
-.TH "NPM\-FOLDERS" "5" "September 2014" "" ""
+.TH "NPM\-FOLDERS" "5" "October 2014" "" ""
.SH "NAME"
\fBnpm-folders\fR \- Folder Structures Used by npm
.SH DESCRIPTION
@@ -142,7 +142,7 @@ highest level possible, below the localized "target" folder\.
Consider this dependency graph:
.P
.RS 2
-.EX
+.nf
foo
+\-\- blerg@1\.2\.5
+\-\- bar@1\.2\.3
@@ -154,13 +154,13 @@ foo
`\-\- baz@1\.2\.3
`\-\- quux@3\.x
`\-\- bar
-.EE
+.fi
.RE
.P
In this case, we might expect a folder structure like this:
.P
.RS 2
-.EX
+.nf
foo
+\-\- node_modules
+\-\- blerg (1\.2\.5) <\-\-\-[A]
@@ -173,7 +173,7 @@ foo
`\-\- baz (1\.2\.3) <\-\-\-[D]
`\-\- node_modules
`\-\- quux (3\.2\.0) <\-\-\-[E]
-.EE
+.fi
.RE
.P
Since foo depends directly on \fBbar@1\.2\.3\fR and \fBbaz@1\.2\.3\fR, those are
diff --git a/deps/npm/man/man5/npm-global.5 b/deps/npm/man/man5/npm-global.5
index 4f4d2cc..9cd3436 100644
--- a/deps/npm/man/man5/npm-global.5
+++ b/deps/npm/man/man5/npm-global.5
@@ -1,4 +1,4 @@
-.TH "NPM\-FOLDERS" "5" "September 2014" "" ""
+.TH "NPM\-FOLDERS" "5" "October 2014" "" ""
.SH "NAME"
\fBnpm-folders\fR \- Folder Structures Used by npm
.SH DESCRIPTION
@@ -142,7 +142,7 @@ highest level possible, below the localized "target" folder\.
Consider this dependency graph:
.P
.RS 2
-.EX
+.nf
foo
+\-\- blerg@1\.2\.5
+\-\- bar@1\.2\.3
@@ -154,13 +154,13 @@ foo
`\-\- baz@1\.2\.3
`\-\- quux@3\.x
`\-\- bar
-.EE
+.fi
.RE
.P
In this case, we might expect a folder structure like this:
.P
.RS 2
-.EX
+.nf
foo
+\-\- node_modules
+\-\- blerg (1\.2\.5) <\-\-\-[A]
@@ -173,7 +173,7 @@ foo
`\-\- baz (1\.2\.3) <\-\-\-[D]
`\-\- node_modules
`\-\- quux (3\.2\.0) <\-\-\-[E]
-.EE
+.fi
.RE
.P
Since foo depends directly on \fBbar@1\.2\.3\fR and \fBbaz@1\.2\.3\fR, those are
diff --git a/deps/npm/man/man5/npm-json.5 b/deps/npm/man/man5/npm-json.5
index 8ab713c..fa9ef95 100644
--- a/deps/npm/man/man5/npm-json.5
+++ b/deps/npm/man/man5/npm-json.5
@@ -1,4 +1,4 @@
-.TH "PACKAGE\.JSON" "5" "September 2014" "" ""
+.TH "PACKAGE\.JSON" "5" "October 2014" "" ""
.SH "NAME"
\fBpackage.json\fR \- Specifics of npm's package\.json handling
.SH DESCRIPTION
@@ -76,11 +76,11 @@ with your package\.
It should look like this:
.P
.RS 2
-.EX
+.nf
{ "url" : "http://github\.com/owner/project/issues"
, "email" : "project@hostname\.com"
}
-.EE
+.fi
.RE
.P
You can specify either one or both values\. If you want to provide only a url,
@@ -97,9 +97,9 @@ or MIT, is to just specify the standard SPDX ID of the license you're using,
like this:
.P
.RS 2
-.EX
+.nf
{ "license" : "BSD\-3\-Clause" }
-.EE
+.fi
.RE
.P
You can check the full list of SPDX license IDs \fIhttps://spdx\.org/licenses/\fR\|\.
@@ -114,20 +114,20 @@ The "author" is one person\. "contributors" is an array of people\. A "person"
is an object with a "name" field and optionally "url" and "email", like this:
.P
.RS 2
-.EX
+.nf
{ "name" : "Barney Rubble"
, "email" : "b@rubble\.com"
, "url" : "http://barnyrubble\.tumblr\.com/"
}
-.EE
+.fi
.RE
.P
Or you can shorten that all into a single string, and npm will parse it for you:
.P
.RS 2
-.EX
+.nf
"Barney Rubble (http://barnyrubble\.tumblr\.com/)
-.EE
+.fi
.RE
.P
Both email and url are optional either way\.
@@ -167,9 +167,9 @@ installs\.
For example, npm has this:
.P
.RS 2
-.EX
+.nf
{ "bin" : { "npm" : "\./cli\.js" } }
-.EE
+.fi
.RE
.P
So, when you install npm, it'll create a symlink from the \fBcli\.js\fR script to
@@ -179,21 +179,21 @@ If you have a single executable, and its name should be the name
of the package, then you can just supply it as a string\. For example:
.P
.RS 2
-.EX
+.nf
{ "name": "my\-program"
, "version": "1\.2\.5"
, "bin": "\./path/to/program" }
-.EE
+.fi
.RE
.P
would be the same as this:
.P
.RS 2
-.EX
+.nf
{ "name": "my\-program"
, "version": "1\.2\.5"
, "bin" : { "my\-program" : "\./path/to/program" } }
-.EE
+.fi
.RE
.SH man
.P
@@ -204,14 +204,14 @@ If only a single file is provided, then it's installed such that it is the
result from \fBman \fR, regardless of its actual filename\. For example:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "version" : "1\.2\.3"
, "description" : "A packaged foo fooer for fooing foos"
, "main" : "foo\.js"
, "man" : "\./man/doc\.1"
}
-.EE
+.fi
.RE
.P
would link the \fB\|\./man/doc\.1\fR file in such that it is the target for \fBman foo\fR
@@ -220,14 +220,14 @@ If the filename doesn't start with the package name, then it's prefixed\.
So, this:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "version" : "1\.2\.3"
, "description" : "A packaged foo fooer for fooing foos"
, "main" : "foo\.js"
, "man" : [ "\./man/foo\.1", "\./man/bar\.1" ]
}
-.EE
+.fi
.RE
.P
will create files to do \fBman foo\fR and \fBman foo\-bar\fR\|\.
@@ -236,14 +236,14 @@ Man files must end with a number, and optionally a \fB\|\.gz\fR suffix if they a
compressed\. The number dictates which man section the file is installed into\.
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "version" : "1\.2\.3"
, "description" : "A packaged foo fooer for fooing foos"
, "main" : "foo\.js"
, "man" : [ "\./man/foo\.1", "\./man/foo\.2" ]
}
-.EE
+.fi
.RE
.P
will create entries for \fBman foo\fR and \fBman 2 foo\fR
@@ -251,7 +251,7 @@ will create entries for \fBman foo\fR and \fBman 2 foo\fR
.P
The CommonJS Packages \fIhttp://wiki\.commonjs\.org/wiki/Packages/1\.0\fR spec details a
few ways that you can indicate the structure of your package using a \fBdirectories\fR
-hash\. If you look at npm's package\.json \fIhttp://registry\.npmjs\.org/npm/latest\fR,
+object\. If you look at npm's package\.json \fIhttp://registry\.npmjs\.org/npm/latest\fR,
you'll see that it has directories for doc, lib, and man\.
.P
In the future, this information may be used in other creative ways\.
@@ -261,10 +261,10 @@ Tell people where the bulk of your library is\. Nothing special is done
with the lib folder in any way, but it's useful meta info\.
.SS directories\.bin
.P
-If you specify a "bin" directory, then all the files in that folder will
-be used as the "bin" hash\.
+If you specify a \fBbin\fR directory, then all the files in that folder will
+be added as children of the \fBbin\fR path\.
.P
-If you have a "bin" hash already, then this has no effect\.
+If you have a \fBbin\fR path already, then this has no effect\.
.SS directories\.man
.P
A folder that is full of man pages\. Sugar to generate a "man" array by
@@ -285,7 +285,7 @@ command will be able to find you\.
Do it like this:
.P
.RS 2
-.EX
+.nf
"repository" :
{ "type" : "git"
, "url" : "http://github\.com/npm/npm\.git"
@@ -295,7 +295,7 @@ Do it like this:
{ "type" : "svn"
, "url" : "http://v8\.googlecode\.com/svn/trunk/"
}
-.EE
+.fi
.RE
.P
The URL should be a publicly available (perhaps read\-only) url that can be handed
@@ -303,22 +303,22 @@ directly to a VCS program without any modification\. It should not be a url to
html project page that you put in your browser\. It's for computers\.
.SH scripts
.P
-The "scripts" member is an object hash of script commands that are run
+The "scripts" property is a dictionary containing script commands that are run
at various times in the lifecycle of your package\. The key is the lifecycle
event, and the value is the command to run at that point\.
.P
See npm help 7 \fBnpm\-scripts\fR to find out more about writing package scripts\.
.SH config
.P
-A "config" hash can be used to set configuration
-parameters used in package scripts that persist across upgrades\. For
-instance, if a package had the following:
+A "config" object can be used to set configuration parameters used in package
+scripts that persist across upgrades\. For instance, if a package had the
+following:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "config" : { "port" : "8080" } }
-.EE
+.fi
.RE
.P
and then had a "start" command that then referenced the
@@ -329,13 +329,13 @@ See npm help 7 \fBnpm\-config\fR and npm help 7 \fBnpm\-scripts\fR for more on p
configs\.
.SH dependencies
.P
-Dependencies are specified with a simple hash of package name to
+Dependencies are specified in a simple object that maps a package name to a
version range\. The version range is a string which has one or more
-space\-separated descriptors\. Dependencies can also be identified with
-a tarball or git URL\.
+space\-separated descriptors\. Dependencies can also be identified with a
+tarball or git URL\.
.P
\fBPlease do not put test harnesses or transpilers in your
-\fBdependencies\fR hash\.\fR See \fBdevDependencies\fR, below\.
+\fBdependencies\fR object\.\fR See \fBdevDependencies\fR, below\.
.P
See npm help 7 semver for more details about specifying version ranges\.
.RS 0
@@ -379,7 +379,7 @@ See npm help 7 semver for more details about specifying version ranges\.
For example, these are all valid:
.P
.RS 2
-.EX
+.nf
{ "dependencies" :
{ "foo" : "1\.0\.0 \- 2\.9999\.9999"
, "bar" : ">=1\.0\.2 <2\.1\.2"
@@ -392,10 +392,10 @@ For example, these are all valid:
, "two" : "2\.x"
, "thr" : "3\.3\.x"
, "lat" : "latest"
- , "dyl" : "~/projects/dyl"
+ , "dyl" : "file:\.\./dyl"
}
}
-.EE
+.fi
.RE
.SS URLs as Dependencies
.P
@@ -408,13 +408,13 @@ install time\.
Git urls can be of the form:
.P
.RS 2
-.EX
+.nf
git://github\.com/user/project\.git#commit\-ish
git+ssh://user@hostname:project\.git#commit\-ish
git+ssh://user@hostname/project\.git#commit\-ish
git+http://user@hostname/project/blah\.git#commit\-ish
git+https://user@hostname/project/blah\.git#commit\-ish
-.EE
+.fi
.RE
.P
The \fBcommit\-ish\fR can be any tag, sha, or branch which can be supplied as
@@ -424,7 +424,7 @@ an argument to \fBgit checkout\fR\|\. The default is \fBmaster\fR\|\.
As of version 1\.1\.65, you can refer to GitHub urls as just "foo": "user/foo\-project"\. For example:
.P
.RS 2
-.EX
+.nf
{
"name": "foo",
"version": "0\.0\.0",
@@ -432,20 +432,35 @@ As of version 1\.1\.65, you can refer to GitHub urls as just "foo": "user/foo\-p
"express": "visionmedia/express"
}
}
-.EE
+.fi
.RE
.SH Local Paths
.P
-As of version 2\.0\.0 you can provide a path to a local directory that
-contains a package\. Local paths can be in the form:
+As of version 2\.0\.0 you can provide a path to a local directory that contains a
+package\. Local paths can be saved using \fBnpm install \-\-save\fR, using any of
+these forms:
.P
.RS 2
-.EX
+.nf
\|\.\./foo/bar
~/foo/bar
\|\./foo/bar
/foo/bar
-.EE
+.fi
+.RE
+.P
+in which case they will be normalized to a relative path and added to your
+\fBpackage\.json\fR\|\. For example:
+.P
+.RS 2
+.nf
+{
+ "name": "baz",
+ "dependencies": {
+ "bar": "file:\.\./foo/bar"
+ }
+}
+.fi
.RE
.P
This feature is helpful for local offline development and creating
@@ -458,8 +473,8 @@ If someone is planning on downloading and using your module in their
program, then they probably don't want or need to download and build
the external test or documentation framework that you use\.
.P
-In this case, it's best to list these additional items in a
-\fBdevDependencies\fR hash\.
+In this case, it's best to map these additional items in a \fBdevDependencies\fR
+object\.
.P
These things will be installed when doing \fBnpm link\fR or \fBnpm install\fR
from the root of a package, and can be managed like any other npm
@@ -472,7 +487,7 @@ script to do this, and make the required package a devDependency\.
For example:
.P
.RS 2
-.EX
+.nf
{ "name": "ethopia\-waza",
"description": "a delightfully fruity coffee varietal",
"version": "1\.2\.3",
@@ -484,7 +499,7 @@ For example:
},
"main": "lib/waza\.js"
}
-.EE
+.fi
.RE
.P
The \fBprepublish\fR script will be run before publishing, so that users
@@ -501,7 +516,7 @@ a specific interface, expected and specified by the host documentation\.
For example:
.P
.RS 2
-.EX
+.nf
{
"name": "tea\-latte",
"version": "1\.3\.5"
@@ -509,7 +524,7 @@ For example:
"tea": "2\.x"
}
}
-.EE
+.fi
.RE
.P
This ensures your package \fBtea\-latte\fR can be installed \fIalong\fR with the second
@@ -518,10 +533,10 @@ installed if needed\. \fBnpm install tea\-latte\fR could possibly yield the foll
dependency graph:
.P
.RS 2
-.EX
+.nf
âââ tea\-latte@1\.3\.5
âââ tea@2\.2\.0
-.EE
+.fi
.RE
.P
Trying to install another plugin with a conflicting requirement will cause an
@@ -539,17 +554,17 @@ Array of package names that will be bundled when publishing the package\.
If this is spelled \fB"bundleDependencies"\fR, then that is also honorable\.
.SH optionalDependencies
.P
-If a dependency can be used, but you would like npm to proceed if it
-cannot be found or fails to install, then you may put it in the
-\fBoptionalDependencies\fR hash\. This is a map of package name to version
-or url, just like the \fBdependencies\fR hash\. The difference is that
-failure is tolerated\.
+If a dependency can be used, but you would like npm to proceed if it cannot be
+found or fails to install, then you may put it in the \fBoptionalDependencies\fR
+object\. This is a map of package name to version or url, just like the
+\fBdependencies\fR object\. The difference is that build failures do not cause
+installation to fail\.
.P
It is still your program's responsibility to handle the lack of the
dependency\. For example, something like this:
.P
.RS 2
-.EX
+.nf
try {
var foo = require('foo')
var fooVersion = require('foo/package\.json')\.version
@@ -565,7 +580,7 @@ if ( notGoodFooVersion(fooVersion) ) {
if (foo) {
foo\.doFooThings()
}
-.EE
+.fi
.RE
.P
Entries in \fBoptionalDependencies\fR will override entries of the same name in
@@ -575,9 +590,9 @@ Entries in \fBoptionalDependencies\fR will override entries of the same name in
You can specify the version of node that your stuff works on:
.P
.RS 2
-.EX
+.nf
{ "engines" : { "node" : ">=0\.10\.3 <0\.12" } }
-.EE
+.fi
.RE
.P
And, like with dependencies, if you don't specify the version (or if you
@@ -591,9 +606,9 @@ You can also use the "engines" field to specify which versions of npm
are capable of properly installing your program\. For example:
.P
.RS 2
-.EX
+.nf
{ "engines" : { "npm" : "~1\.0\.20" } }
-.EE
+.fi
.RE
.P
Note that, unless the user has set the \fBengine\-strict\fR config flag, this
@@ -601,12 +616,12 @@ field is advisory only\.
.SH engineStrict
.P
If you are sure that your module will \fIdefinitely not\fR run properly on
-versions of Node/npm other than those specified in the \fBengines\fR hash,
+versions of Node/npm other than those specified in the \fBengines\fR object,
then you can set \fB"engineStrict": true\fR in your package\.json file\.
This will override the user's \fBengine\-strict\fR config setting\.
.P
Please do not do this unless you are really very very sure\. If your
-engines hash is something overly restrictive, you can quite easily and
+engines object is something overly restrictive, you can quite easily and
inadvertently lock yourself into obscurity and prevent your users from
updating to new versions of Node\. Consider this choice carefully\. If
people abuse it, it will be removed in a future version of npm\.
@@ -616,18 +631,18 @@ You can specify which operating systems your
module will run on:
.P
.RS 2
-.EX
+.nf
"os" : [ "darwin", "linux" ]
-.EE
+.fi
.RE
.P
You can also blacklist instead of whitelist operating systems,
just prepend the blacklisted os with a '!':
.P
.RS 2
-.EX
+.nf
"os" : [ "!win32" ]
-.EE
+.fi
.RE
.P
The host operating system is determined by \fBprocess\.platform\fR
@@ -640,17 +655,17 @@ If your code only runs on certain cpu architectures,
you can specify which ones\.
.P
.RS 2
-.EX
+.nf
"cpu" : [ "x64", "ia32" ]
-.EE
+.fi
.RE
.P
Like the \fBos\fR option, you can also blacklist architectures:
.P
.RS 2
-.EX
+.nf
"cpu" : [ "!arm", "!mips" ]
-.EE
+.fi
.RE
.P
The host architecture is determined by \fBprocess\.arch\fR
@@ -667,11 +682,11 @@ does help prevent some confusion if it doesn't work as expected\.
If you set \fB"private": true\fR in your package\.json, then npm will refuse
to publish it\.
.P
-This is a way to prevent accidental publication of private repositories\.
-If you would like to ensure that a given package is only ever published
-to a specific registry (for example, an internal registry),
-then use the \fBpublishConfig\fR hash described below
-to override the \fBregistry\fR config param at publish\-time\.
+This is a way to prevent accidental publication of private repositories\. If
+you would like to ensure that a given package is only ever published to a
+specific registry (for example, an internal registry), then use the
+\fBpublishConfig\fR dictionary described below to override the \fBregistry\fR config
+param at publish\-time\.
.SH publishConfig
.P
This is a set of config values that will be used at publish\-time\. It's
diff --git a/deps/npm/man/man5/npmrc.5 b/deps/npm/man/man5/npmrc.5
index 569b7c5..d284686 100644
--- a/deps/npm/man/man5/npmrc.5
+++ b/deps/npm/man/man5/npmrc.5
@@ -1,4 +1,4 @@
-.TH "NPMRC" "5" "September 2014" "" ""
+.TH "NPMRC" "5" "October 2014" "" ""
.SH "NAME"
\fBnpmrc\fR \- The npm config files
.SH DESCRIPTION
@@ -30,9 +30,9 @@ parameters\. Environment variables can be replaced using
\fB${VARIABLE_NAME}\fR\|\. For example:
.P
.RS 2
-.EX
+.nf
prefix = ${HOME}/\.npm\-packages
-.EE
+.fi
.RE
.P
Each of these files is loaded, and config options are resolved in
diff --git a/deps/npm/man/man5/package.json.5 b/deps/npm/man/man5/package.json.5
index 8ab713c..fa9ef95 100644
--- a/deps/npm/man/man5/package.json.5
+++ b/deps/npm/man/man5/package.json.5
@@ -1,4 +1,4 @@
-.TH "PACKAGE\.JSON" "5" "September 2014" "" ""
+.TH "PACKAGE\.JSON" "5" "October 2014" "" ""
.SH "NAME"
\fBpackage.json\fR \- Specifics of npm's package\.json handling
.SH DESCRIPTION
@@ -76,11 +76,11 @@ with your package\.
It should look like this:
.P
.RS 2
-.EX
+.nf
{ "url" : "http://github\.com/owner/project/issues"
, "email" : "project@hostname\.com"
}
-.EE
+.fi
.RE
.P
You can specify either one or both values\. If you want to provide only a url,
@@ -97,9 +97,9 @@ or MIT, is to just specify the standard SPDX ID of the license you're using,
like this:
.P
.RS 2
-.EX
+.nf
{ "license" : "BSD\-3\-Clause" }
-.EE
+.fi
.RE
.P
You can check the full list of SPDX license IDs \fIhttps://spdx\.org/licenses/\fR\|\.
@@ -114,20 +114,20 @@ The "author" is one person\. "contributors" is an array of people\. A "person"
is an object with a "name" field and optionally "url" and "email", like this:
.P
.RS 2
-.EX
+.nf
{ "name" : "Barney Rubble"
, "email" : "b@rubble\.com"
, "url" : "http://barnyrubble\.tumblr\.com/"
}
-.EE
+.fi
.RE
.P
Or you can shorten that all into a single string, and npm will parse it for you:
.P
.RS 2
-.EX
+.nf
"Barney Rubble (http://barnyrubble\.tumblr\.com/)
-.EE
+.fi
.RE
.P
Both email and url are optional either way\.
@@ -167,9 +167,9 @@ installs\.
For example, npm has this:
.P
.RS 2
-.EX
+.nf
{ "bin" : { "npm" : "\./cli\.js" } }
-.EE
+.fi
.RE
.P
So, when you install npm, it'll create a symlink from the \fBcli\.js\fR script to
@@ -179,21 +179,21 @@ If you have a single executable, and its name should be the name
of the package, then you can just supply it as a string\. For example:
.P
.RS 2
-.EX
+.nf
{ "name": "my\-program"
, "version": "1\.2\.5"
, "bin": "\./path/to/program" }
-.EE
+.fi
.RE
.P
would be the same as this:
.P
.RS 2
-.EX
+.nf
{ "name": "my\-program"
, "version": "1\.2\.5"
, "bin" : { "my\-program" : "\./path/to/program" } }
-.EE
+.fi
.RE
.SH man
.P
@@ -204,14 +204,14 @@ If only a single file is provided, then it's installed such that it is the
result from \fBman \fR, regardless of its actual filename\. For example:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "version" : "1\.2\.3"
, "description" : "A packaged foo fooer for fooing foos"
, "main" : "foo\.js"
, "man" : "\./man/doc\.1"
}
-.EE
+.fi
.RE
.P
would link the \fB\|\./man/doc\.1\fR file in such that it is the target for \fBman foo\fR
@@ -220,14 +220,14 @@ If the filename doesn't start with the package name, then it's prefixed\.
So, this:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "version" : "1\.2\.3"
, "description" : "A packaged foo fooer for fooing foos"
, "main" : "foo\.js"
, "man" : [ "\./man/foo\.1", "\./man/bar\.1" ]
}
-.EE
+.fi
.RE
.P
will create files to do \fBman foo\fR and \fBman foo\-bar\fR\|\.
@@ -236,14 +236,14 @@ Man files must end with a number, and optionally a \fB\|\.gz\fR suffix if they a
compressed\. The number dictates which man section the file is installed into\.
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "version" : "1\.2\.3"
, "description" : "A packaged foo fooer for fooing foos"
, "main" : "foo\.js"
, "man" : [ "\./man/foo\.1", "\./man/foo\.2" ]
}
-.EE
+.fi
.RE
.P
will create entries for \fBman foo\fR and \fBman 2 foo\fR
@@ -251,7 +251,7 @@ will create entries for \fBman foo\fR and \fBman 2 foo\fR
.P
The CommonJS Packages \fIhttp://wiki\.commonjs\.org/wiki/Packages/1\.0\fR spec details a
few ways that you can indicate the structure of your package using a \fBdirectories\fR
-hash\. If you look at npm's package\.json \fIhttp://registry\.npmjs\.org/npm/latest\fR,
+object\. If you look at npm's package\.json \fIhttp://registry\.npmjs\.org/npm/latest\fR,
you'll see that it has directories for doc, lib, and man\.
.P
In the future, this information may be used in other creative ways\.
@@ -261,10 +261,10 @@ Tell people where the bulk of your library is\. Nothing special is done
with the lib folder in any way, but it's useful meta info\.
.SS directories\.bin
.P
-If you specify a "bin" directory, then all the files in that folder will
-be used as the "bin" hash\.
+If you specify a \fBbin\fR directory, then all the files in that folder will
+be added as children of the \fBbin\fR path\.
.P
-If you have a "bin" hash already, then this has no effect\.
+If you have a \fBbin\fR path already, then this has no effect\.
.SS directories\.man
.P
A folder that is full of man pages\. Sugar to generate a "man" array by
@@ -285,7 +285,7 @@ command will be able to find you\.
Do it like this:
.P
.RS 2
-.EX
+.nf
"repository" :
{ "type" : "git"
, "url" : "http://github\.com/npm/npm\.git"
@@ -295,7 +295,7 @@ Do it like this:
{ "type" : "svn"
, "url" : "http://v8\.googlecode\.com/svn/trunk/"
}
-.EE
+.fi
.RE
.P
The URL should be a publicly available (perhaps read\-only) url that can be handed
@@ -303,22 +303,22 @@ directly to a VCS program without any modification\. It should not be a url to
html project page that you put in your browser\. It's for computers\.
.SH scripts
.P
-The "scripts" member is an object hash of script commands that are run
+The "scripts" property is a dictionary containing script commands that are run
at various times in the lifecycle of your package\. The key is the lifecycle
event, and the value is the command to run at that point\.
.P
See npm help 7 \fBnpm\-scripts\fR to find out more about writing package scripts\.
.SH config
.P
-A "config" hash can be used to set configuration
-parameters used in package scripts that persist across upgrades\. For
-instance, if a package had the following:
+A "config" object can be used to set configuration parameters used in package
+scripts that persist across upgrades\. For instance, if a package had the
+following:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "config" : { "port" : "8080" } }
-.EE
+.fi
.RE
.P
and then had a "start" command that then referenced the
@@ -329,13 +329,13 @@ See npm help 7 \fBnpm\-config\fR and npm help 7 \fBnpm\-scripts\fR for more on p
configs\.
.SH dependencies
.P
-Dependencies are specified with a simple hash of package name to
+Dependencies are specified in a simple object that maps a package name to a
version range\. The version range is a string which has one or more
-space\-separated descriptors\. Dependencies can also be identified with
-a tarball or git URL\.
+space\-separated descriptors\. Dependencies can also be identified with a
+tarball or git URL\.
.P
\fBPlease do not put test harnesses or transpilers in your
-\fBdependencies\fR hash\.\fR See \fBdevDependencies\fR, below\.
+\fBdependencies\fR object\.\fR See \fBdevDependencies\fR, below\.
.P
See npm help 7 semver for more details about specifying version ranges\.
.RS 0
@@ -379,7 +379,7 @@ See npm help 7 semver for more details about specifying version ranges\.
For example, these are all valid:
.P
.RS 2
-.EX
+.nf
{ "dependencies" :
{ "foo" : "1\.0\.0 \- 2\.9999\.9999"
, "bar" : ">=1\.0\.2 <2\.1\.2"
@@ -392,10 +392,10 @@ For example, these are all valid:
, "two" : "2\.x"
, "thr" : "3\.3\.x"
, "lat" : "latest"
- , "dyl" : "~/projects/dyl"
+ , "dyl" : "file:\.\./dyl"
}
}
-.EE
+.fi
.RE
.SS URLs as Dependencies
.P
@@ -408,13 +408,13 @@ install time\.
Git urls can be of the form:
.P
.RS 2
-.EX
+.nf
git://github\.com/user/project\.git#commit\-ish
git+ssh://user@hostname:project\.git#commit\-ish
git+ssh://user@hostname/project\.git#commit\-ish
git+http://user@hostname/project/blah\.git#commit\-ish
git+https://user@hostname/project/blah\.git#commit\-ish
-.EE
+.fi
.RE
.P
The \fBcommit\-ish\fR can be any tag, sha, or branch which can be supplied as
@@ -424,7 +424,7 @@ an argument to \fBgit checkout\fR\|\. The default is \fBmaster\fR\|\.
As of version 1\.1\.65, you can refer to GitHub urls as just "foo": "user/foo\-project"\. For example:
.P
.RS 2
-.EX
+.nf
{
"name": "foo",
"version": "0\.0\.0",
@@ -432,20 +432,35 @@ As of version 1\.1\.65, you can refer to GitHub urls as just "foo": "user/foo\-p
"express": "visionmedia/express"
}
}
-.EE
+.fi
.RE
.SH Local Paths
.P
-As of version 2\.0\.0 you can provide a path to a local directory that
-contains a package\. Local paths can be in the form:
+As of version 2\.0\.0 you can provide a path to a local directory that contains a
+package\. Local paths can be saved using \fBnpm install \-\-save\fR, using any of
+these forms:
.P
.RS 2
-.EX
+.nf
\|\.\./foo/bar
~/foo/bar
\|\./foo/bar
/foo/bar
-.EE
+.fi
+.RE
+.P
+in which case they will be normalized to a relative path and added to your
+\fBpackage\.json\fR\|\. For example:
+.P
+.RS 2
+.nf
+{
+ "name": "baz",
+ "dependencies": {
+ "bar": "file:\.\./foo/bar"
+ }
+}
+.fi
.RE
.P
This feature is helpful for local offline development and creating
@@ -458,8 +473,8 @@ If someone is planning on downloading and using your module in their
program, then they probably don't want or need to download and build
the external test or documentation framework that you use\.
.P
-In this case, it's best to list these additional items in a
-\fBdevDependencies\fR hash\.
+In this case, it's best to map these additional items in a \fBdevDependencies\fR
+object\.
.P
These things will be installed when doing \fBnpm link\fR or \fBnpm install\fR
from the root of a package, and can be managed like any other npm
@@ -472,7 +487,7 @@ script to do this, and make the required package a devDependency\.
For example:
.P
.RS 2
-.EX
+.nf
{ "name": "ethopia\-waza",
"description": "a delightfully fruity coffee varietal",
"version": "1\.2\.3",
@@ -484,7 +499,7 @@ For example:
},
"main": "lib/waza\.js"
}
-.EE
+.fi
.RE
.P
The \fBprepublish\fR script will be run before publishing, so that users
@@ -501,7 +516,7 @@ a specific interface, expected and specified by the host documentation\.
For example:
.P
.RS 2
-.EX
+.nf
{
"name": "tea\-latte",
"version": "1\.3\.5"
@@ -509,7 +524,7 @@ For example:
"tea": "2\.x"
}
}
-.EE
+.fi
.RE
.P
This ensures your package \fBtea\-latte\fR can be installed \fIalong\fR with the second
@@ -518,10 +533,10 @@ installed if needed\. \fBnpm install tea\-latte\fR could possibly yield the foll
dependency graph:
.P
.RS 2
-.EX
+.nf
âââ tea\-latte@1\.3\.5
âââ tea@2\.2\.0
-.EE
+.fi
.RE
.P
Trying to install another plugin with a conflicting requirement will cause an
@@ -539,17 +554,17 @@ Array of package names that will be bundled when publishing the package\.
If this is spelled \fB"bundleDependencies"\fR, then that is also honorable\.
.SH optionalDependencies
.P
-If a dependency can be used, but you would like npm to proceed if it
-cannot be found or fails to install, then you may put it in the
-\fBoptionalDependencies\fR hash\. This is a map of package name to version
-or url, just like the \fBdependencies\fR hash\. The difference is that
-failure is tolerated\.
+If a dependency can be used, but you would like npm to proceed if it cannot be
+found or fails to install, then you may put it in the \fBoptionalDependencies\fR
+object\. This is a map of package name to version or url, just like the
+\fBdependencies\fR object\. The difference is that build failures do not cause
+installation to fail\.
.P
It is still your program's responsibility to handle the lack of the
dependency\. For example, something like this:
.P
.RS 2
-.EX
+.nf
try {
var foo = require('foo')
var fooVersion = require('foo/package\.json')\.version
@@ -565,7 +580,7 @@ if ( notGoodFooVersion(fooVersion) ) {
if (foo) {
foo\.doFooThings()
}
-.EE
+.fi
.RE
.P
Entries in \fBoptionalDependencies\fR will override entries of the same name in
@@ -575,9 +590,9 @@ Entries in \fBoptionalDependencies\fR will override entries of the same name in
You can specify the version of node that your stuff works on:
.P
.RS 2
-.EX
+.nf
{ "engines" : { "node" : ">=0\.10\.3 <0\.12" } }
-.EE
+.fi
.RE
.P
And, like with dependencies, if you don't specify the version (or if you
@@ -591,9 +606,9 @@ You can also use the "engines" field to specify which versions of npm
are capable of properly installing your program\. For example:
.P
.RS 2
-.EX
+.nf
{ "engines" : { "npm" : "~1\.0\.20" } }
-.EE
+.fi
.RE
.P
Note that, unless the user has set the \fBengine\-strict\fR config flag, this
@@ -601,12 +616,12 @@ field is advisory only\.
.SH engineStrict
.P
If you are sure that your module will \fIdefinitely not\fR run properly on
-versions of Node/npm other than those specified in the \fBengines\fR hash,
+versions of Node/npm other than those specified in the \fBengines\fR object,
then you can set \fB"engineStrict": true\fR in your package\.json file\.
This will override the user's \fBengine\-strict\fR config setting\.
.P
Please do not do this unless you are really very very sure\. If your
-engines hash is something overly restrictive, you can quite easily and
+engines object is something overly restrictive, you can quite easily and
inadvertently lock yourself into obscurity and prevent your users from
updating to new versions of Node\. Consider this choice carefully\. If
people abuse it, it will be removed in a future version of npm\.
@@ -616,18 +631,18 @@ You can specify which operating systems your
module will run on:
.P
.RS 2
-.EX
+.nf
"os" : [ "darwin", "linux" ]
-.EE
+.fi
.RE
.P
You can also blacklist instead of whitelist operating systems,
just prepend the blacklisted os with a '!':
.P
.RS 2
-.EX
+.nf
"os" : [ "!win32" ]
-.EE
+.fi
.RE
.P
The host operating system is determined by \fBprocess\.platform\fR
@@ -640,17 +655,17 @@ If your code only runs on certain cpu architectures,
you can specify which ones\.
.P
.RS 2
-.EX
+.nf
"cpu" : [ "x64", "ia32" ]
-.EE
+.fi
.RE
.P
Like the \fBos\fR option, you can also blacklist architectures:
.P
.RS 2
-.EX
+.nf
"cpu" : [ "!arm", "!mips" ]
-.EE
+.fi
.RE
.P
The host architecture is determined by \fBprocess\.arch\fR
@@ -667,11 +682,11 @@ does help prevent some confusion if it doesn't work as expected\.
If you set \fB"private": true\fR in your package\.json, then npm will refuse
to publish it\.
.P
-This is a way to prevent accidental publication of private repositories\.
-If you would like to ensure that a given package is only ever published
-to a specific registry (for example, an internal registry),
-then use the \fBpublishConfig\fR hash described below
-to override the \fBregistry\fR config param at publish\-time\.
+This is a way to prevent accidental publication of private repositories\. If
+you would like to ensure that a given package is only ever published to a
+specific registry (for example, an internal registry), then use the
+\fBpublishConfig\fR dictionary described below to override the \fBregistry\fR config
+param at publish\-time\.
.SH publishConfig
.P
This is a set of config values that will be used at publish\-time\. It's
diff --git a/deps/npm/man/man7/npm-coding-style.7 b/deps/npm/man/man7/npm-coding-style.7
index 304dd49..0dc1531 100644
--- a/deps/npm/man/man7/npm-coding-style.7
+++ b/deps/npm/man/man7/npm-coding-style.7
@@ -1,4 +1,4 @@
-.TH "NPM\-CODING\-STYLE" "7" "September 2014" "" ""
+.TH "NPM\-CODING\-STYLE" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-coding-style\fR \- npm's "funny" coding style
.SH DESCRIPTION
@@ -29,18 +29,18 @@ Curly braces belong on the same line as the thing that necessitates them\.
Bad:
.P
.RS 2
-.EX
+.nf
function ()
{
-.EE
+.fi
.RE
.P
Good:
.P
.RS 2
-.EX
+.nf
function () {
-.EE
+.fi
.RE
.P
If a block needs to wrap to the next line, use a curly brace\. Don't
@@ -49,22 +49,22 @@ use it if it doesn't\.
Bad:
.P
.RS 2
-.EX
+.nf
if (foo) { bar() }
while (foo)
bar()
-.EE
+.fi
.RE
.P
Good:
.P
.RS 2
-.EX
+.nf
if (foo) bar()
while (foo) {
bar()
}
-.EE
+.fi
.RE
.SH Semicolons
.P
@@ -87,7 +87,7 @@ as a function call or property access, respectively\.
Some examples of good semicolon usage:
.P
.RS 2
-.EX
+.nf
;(x || y)\.doSomething()
;[a, b, c]\.forEach(doSomething)
for (var i = 0; i < 10; i ++) {
@@ -98,7 +98,7 @@ for (var i = 0; i < 10; i ++) {
}
end()
}
-.EE
+.fi
.RE
.P
Note that starting lines with \fB\-\fR and \fB+\fR also should be prefixed
@@ -111,7 +111,7 @@ line, directly below the token that starts the list\. Put the
final token in the list on a line by itself\. For example:
.P
.RS 2
-.EX
+.nf
var magicWords = [ "abracadabra"
, "gesundheit"
, "ventrilo"
@@ -123,7 +123,7 @@ var magicWords = [ "abracadabra"
, b = "abc"
, etc
, somethingElse
-.EE
+.fi
.RE
.SH Whitespace
.P
@@ -166,7 +166,7 @@ Use appropriate log levels\. See npm help 7 \fBnpm\-config\fR and search for
.SH Case, naming, etc\.
.P
Use \fBlowerCamelCase\fR for multiword identifiers when they refer to objects,
-functions, methods, members, or anything not specified in this section\.
+functions, methods, properties, or anything not specified in this section\.
.P
Use \fBUpperCamelCase\fR for class names (things that you'd pass to "new")\.
.P
diff --git a/deps/npm/man/man7/npm-config.7 b/deps/npm/man/man7/npm-config.7
index f759d94..e3b4c5c 100644
--- a/deps/npm/man/man7/npm-config.7
+++ b/deps/npm/man/man7/npm-config.7
@@ -1,4 +1,4 @@
-.TH "NPM\-CONFIG" "7" "September 2014" "" ""
+.TH "NPM\-CONFIG" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-config\fR \- More than you probably want to know about npm configuration
.SH DESCRIPTION
@@ -99,11 +99,11 @@ configuration parameter, then it is expanded to that configuration
parameter\. For example:
.P
.RS 2
-.EX
+.nf
npm ls \-\-par
# same as:
npm ls \-\-parseable
-.EE
+.fi
.RE
.P
If multiple single\-character shorthands are strung together, and the
@@ -112,11 +112,11 @@ param, then it is expanded to its various component pieces\. For
example:
.P
.RS 2
-.EX
+.nf
npm ls \-gpld
# same as:
npm ls \-\-global \-\-parseable \-\-long \-\-loglevel info
-.EE
+.fi
.RE
.SH Per\-Package Config Settings
.P
@@ -126,27 +126,27 @@ keys are overwritten in the environment if there is a config param of
this:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "config" : { "port" : "8080" }
, "scripts" : { "start" : "node server\.js" } }
-.EE
+.fi
.RE
.P
and the server\.js is this:
.P
.RS 2
-.EX
+.nf
http\.createServer(\.\.\.)\.listen(process\.env\.npm_package_config_port)
-.EE
+.fi
.RE
.P
then the user could change the behavior by doing:
.P
.RS 2
-.EX
+.nf
npm config set foo:port 80
-.EE
+.fi
.RE
.P
See npm help 5 package\.json for more information\.
@@ -535,7 +535,7 @@ A module that will be loaded by the \fBnpm init\fR command\. See the
documentation for the
init\-package\-json \fIhttps://github\.com/isaacs/init\-package\-json\fR module
for more information, or npm help init\.
-.SS init\.author\.name
+.SS init\-author\-name
.RS 0
.IP \(bu 2
Default: ""
@@ -545,7 +545,7 @@ Type: String
.RE
.P
The value \fBnpm init\fR should use by default for the package author's name\.
-.SS init\.author\.email
+.SS init\-author\-email
.RS 0
.IP \(bu 2
Default: ""
@@ -555,7 +555,7 @@ Type: String
.RE
.P
The value \fBnpm init\fR should use by default for the package author's email\.
-.SS init\.author\.url
+.SS init\-author\-url
.RS 0
.IP \(bu 2
Default: ""
@@ -565,7 +565,7 @@ Type: String
.RE
.P
The value \fBnpm init\fR should use by default for the package author's homepage\.
-.SS init\.license
+.SS init\-license
.RS 0
.IP \(bu 2
Default: "ISC"
@@ -575,7 +575,7 @@ Type: String
.RE
.P
The value \fBnpm init\fR should use by default for the package license\.
-.SS init\.version
+.SS init\-version
.RS 0
.IP \(bu 2
Default: "0\.0\.0"
@@ -647,7 +647,7 @@ to the npm registry\. Must be IPv4 in versions of Node prior to 0\.12\.
.SS loglevel
.RS 0
.IP \(bu 2
-Default: "http"
+Default: "warn"
.IP \(bu 2
Type: String
.IP \(bu 2
@@ -659,7 +659,7 @@ What level of logs to report\. On failure, \fIall\fR logs are written to
\fBnpm\-debug\.log\fR in the current working directory\.
.P
Any logs of a higher level than the setting are shown\.
-The default is "http", which shows http, warn, and error output\.
+The default is "warn", which shows warn and error output\.
.SS logstream
.RS 0
.IP \(bu 2
@@ -709,7 +709,7 @@ Type: semver or false
.RE
.P
-The node version to use when checking package's "engines" hash\.
+The node version to use when checking a package's \fBengines\fR map\.
.SS npat
.RS 0
.IP \(bu 2
@@ -740,7 +740,7 @@ Type: Boolean
.RE
.P
-Attempt to install packages in the \fBoptionalDependencies\fR hash\. Note
+Attempt to install packages in the \fBoptionalDependencies\fR object\. Note
that if these packages fail to install, the overall installation
process is not aborted\.
.SS parseable
@@ -849,8 +849,8 @@ Type: Boolean
.P
Save installed packages to a package\.json file as dependencies\.
.P
-When used with the \fBnpm rm\fR command, it removes it from the dependencies
-hash\.
+When used with the \fBnpm rm\fR command, it removes it from the \fBdependencies\fR
+object\.
.P
Only works if there is already a package\.json file present\.
.SS save\-bundle
@@ -877,10 +877,10 @@ Type: Boolean
.RE
.P
-Save installed packages to a package\.json file as devDependencies\.
+Save installed packages to a package\.json file as \fBdevDependencies\fR\|\.
.P
When used with the \fBnpm rm\fR command, it removes it from the
-devDependencies hash\.
+\fBdevDependencies\fR object\.
.P
Only works if there is already a package\.json file present\.
.SS save\-exact
@@ -908,7 +908,7 @@ Save installed packages to a package\.json file as
optionalDependencies\.
.P
When used with the \fBnpm rm\fR command, it removes it from the
-devDependencies hash\.
+\fBdevDependencies\fR object\.
.P
Only works if there is already a package\.json file present\.
.SS save\-prefix
@@ -1163,8 +1163,8 @@ Type: boolean
.RE
.P
-If true, output the npm version as well as node's \fBprocess\.versions\fR
-hash, and exit successfully\.
+If true, output the npm version as well as node's \fBprocess\.versions\fR map, and
+exit successfully\.
.P
Only relevant when specified explicitly on the command line\.
.SS viewer
diff --git a/deps/npm/man/man7/npm-developers.7 b/deps/npm/man/man7/npm-developers.7
index fbf7a3c..bf8edb2 100644
--- a/deps/npm/man/man7/npm-developers.7
+++ b/deps/npm/man/man7/npm-developers.7
@@ -1,4 +1,4 @@
-.TH "NPM\-DEVELOPERS" "7" "September 2014" "" ""
+.TH "NPM\-DEVELOPERS" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-developers\fR \- Developer Guide
.SH DESCRIPTION
@@ -44,12 +44,12 @@ after packing it up into a tarball (b)\.
Git urls can be of the form:
.P
.RS 2
-.EX
+.nf
git://github\.com/user/project\.git#commit\-ish
git+ssh://user@hostname:project\.git#commit\-ish
git+http://user@hostname/project/blah\.git#commit\-ish
git+https://user@hostname/project/blah\.git#commit\-ish
-.EE
+.fi
.RE
.P
The \fBcommit\-ish\fR can be any tag, sha, or branch which can be supplied as
@@ -85,7 +85,7 @@ Take some credit\.
.IP \(bu 2
scripts:
If you have a special compilation or installation script, then you
-should put it in the \fBscripts\fR hash\. You should definitely have at
+should put it in the \fBscripts\fR object\. You should definitely have at
least a basic smoke\-test command as the "scripts\.test" field\.
See npm help 7 scripts\.
.IP \(bu 2
@@ -95,8 +95,8 @@ program (like what the "foo" package gives you at require("foo")),
then you need to specify that in the "main" field\.
.IP \(bu 2
directories:
-This is a hash of folders\. The best ones to include are "lib" and
-"doc", but if you specify a folder full of man pages in "man", then
+This is an object mapping names to folders\. The best ones to include are
+"lib" and "doc", but if you use "man" to specify a folder full of man pages,
they'll get installed just like these ones\.
.RE
@@ -171,18 +171,18 @@ So don't do that\.
In the root of your package, do this:
.P
.RS 2
-.EX
+.nf
npm install \. \-g
-.EE
+.fi
.RE
.P
That'll show you that it's working\. If you'd rather just create a symlink
package that points to your working directory, then do this:
.P
.RS 2
-.EX
+.nf
npm link
-.EE
+.fi
.RE
.P
Use \fBnpm ls \-g\fR to see if it's there\.
@@ -190,10 +190,10 @@ Use \fBnpm ls \-g\fR to see if it's there\.
To test a local install, go into some other folder, and then do:
.P
.RS 2
-.EX
+.nf
cd \.\./some\-other\-folder
npm install \.\./my\-package
-.EE
+.fi
.RE
.P
to install it locally into the node_modules folder in that other place\.
@@ -205,9 +205,9 @@ bring in your module's main module\.
Create a user with the adduser command\. It works like this:
.P
.RS 2
-.EX
+.nf
npm adduser
-.EE
+.fi
.RE
.P
and then follow the prompts\.
@@ -218,9 +218,9 @@ This is documented better in npm help adduser\.
This part's easy\. IN the root of your folder, do this:
.P
.RS 2
-.EX
+.nf
npm publish
-.EE
+.fi
.RE
.P
You can give publish a url to a tarball, or a filename of a tarball,
diff --git a/deps/npm/man/man7/npm-disputes.7 b/deps/npm/man/man7/npm-disputes.7
index fb7fd25..9cf7009 100644
--- a/deps/npm/man/man7/npm-disputes.7
+++ b/deps/npm/man/man7/npm-disputes.7
@@ -1,4 +1,4 @@
-.TH "NPM\-DISPUTES" "7" "September 2014" "" ""
+.TH "NPM\-DISPUTES" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-disputes\fR \- Handling Module Name Disputes
.SH SYNOPSIS
diff --git a/deps/npm/man/man7/npm-faq.7 b/deps/npm/man/man7/npm-faq.7
index 942d3c0..563509a 100644
--- a/deps/npm/man/man7/npm-faq.7
+++ b/deps/npm/man/man7/npm-faq.7
@@ -1,4 +1,4 @@
-.TH "NPM\-FAQ" "7" "September 2014" "" ""
+.TH "NPM\-FAQ" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-faq\fR \- Frequently Asked Questions
.SH Where can I find these docs in HTML?
@@ -6,9 +6,9 @@
https://www\.npmjs\.org/doc/, or run:
.P
.RS 2
-.EX
+.nf
npm config set viewer browser
-.EE
+.fi
.RE
.P
to open these documents in your default web browser rather than \fBman\fR\|\.
@@ -131,9 +131,9 @@ Arguments are greps\. \fBnpm search jsdom\fR shows jsdom packages\.
.SH How do I update npm?
.P
.RS 2
-.EX
-npm update npm \-g
-.EE
+.nf
+npm install npm \-g
+.fi
.RE
.P
You can also update all outdated local packages by doing \fBnpm update\fR without
@@ -147,9 +147,9 @@ command\.)
In those cases, you can do this:
.P
.RS 2
-.EX
+.nf
curl https://www\.npmjs\.org/install\.sh | sh
-.EE
+.fi
.RE
.SH What is a \fBpackage\fR?
.P
@@ -180,12 +180,12 @@ after packing it up into a tarball (b)\.
Git urls can be of the form:
.P
.RS 2
-.EX
+.nf
git://github\.com/user/project\.git#commit\-ish
git+ssh://user@hostname:project\.git#commit\-ish
git+http://user@hostname/project/blah\.git#commit\-ish
git+https://user@hostname/project/blah\.git#commit\-ish
-.EE
+.fi
.RE
.P
The \fBcommit\-ish\fR can be any tag, sha, or branch which can be supplied as
@@ -218,9 +218,9 @@ In the context of a Node program, the \fBmodule\fR is also the thing that
was loaded \fIfrom\fR a file\. For example, in the following program:
.P
.RS 2
-.EX
+.nf
var req = require('request')
-.EE
+.fi
.RE
.P
we might say that "The variable \fBreq\fR refers to the \fBrequest\fR module"\.
diff --git a/deps/npm/man/man7/npm-index.7 b/deps/npm/man/man7/npm-index.7
index 5667722..442815a 100644
--- a/deps/npm/man/man7/npm-index.7
+++ b/deps/npm/man/man7/npm-index.7
@@ -1,4 +1,4 @@
-.TH "NPM\-INDEX" "7" "September 2014" "" ""
+.TH "NPM\-INDEX" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-index\fR \- Index of all npm documentation
.SS npm help README
@@ -121,9 +121,6 @@ Start a package
.SS npm help stop
.P
Stop a package
-.SS npm help submodule
-.P
-Add a package as a git submodule
.SS npm help tag
.P
Tag a published version
@@ -244,9 +241,6 @@ Start a package
.SS npm apihelp stop
.P
Stop a package
-.SS npm apihelp submodule
-.P
-Add a package as a git submodule
.SS npm apihelp tag
.P
Tag a published version
diff --git a/deps/npm/man/man7/npm-registry.7 b/deps/npm/man/man7/npm-registry.7
index ac3059c..9de209d 100644
--- a/deps/npm/man/man7/npm-registry.7
+++ b/deps/npm/man/man7/npm-registry.7
@@ -1,4 +1,4 @@
-.TH "NPM\-REGISTRY" "7" "September 2014" "" ""
+.TH "NPM\-REGISTRY" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-registry\fR \- The JavaScript Package Registry
.SH DESCRIPTION
diff --git a/deps/npm/man/man7/npm-scope.7 b/deps/npm/man/man7/npm-scope.7
index ef8d251..f876e4e 100644
--- a/deps/npm/man/man7/npm-scope.7
+++ b/deps/npm/man/man7/npm-scope.7
@@ -1,4 +1,4 @@
-.TH "NPM\-SCOPE" "7" "September 2014" "" ""
+.TH "NPM\-SCOPE" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-scope\fR \- Scoped packages
.SH DESCRIPTION
@@ -9,9 +9,9 @@ or underscores)\. When used in package names, preceded by an @\-symbol and
followed by a slash, e\.g\.
.P
.RS 2
-.EX
+.nf
@somescope/somepackagename
-.EE
+.fi
.RE
.P
Scopes are a way of grouping related packages together, and also affect a few
@@ -28,23 +28,23 @@ scoped modules will be in \fBnode_modules/@myorg/packagename\fR\|\. The scope fo
(\fB@myorg\fR) is simply the name of the scope preceded by an @\-symbol, and can
contain any number of scoped packages\.
.P
-A scoped package is install by referencing it by name, preceded by an @\-symbol,
-in \fBnpm install\fR:
+A scoped package is installed by referencing it by name, preceded by an
+@\-symbol, in \fBnpm install\fR:
.P
.RS 2
-.EX
+.nf
npm install @myorg/mypackage
-.EE
+.fi
.RE
.P
Or in \fBpackage\.json\fR:
.P
.RS 2
-.EX
+.nf
"dependencies": {
"@myorg/mypackage": "^1\.3\.0"
}
-.EE
+.fi
.RE
.P
Note that if the @\-symbol is omitted in either case npm will instead attempt to
@@ -55,9 +55,9 @@ Because scoped packages are installed into a scope folder, you have to
include the name of the scope when requiring them in your code, e\.g\.
.P
.RS 2
-.EX
+.nf
require('@myorg/mypackage')
-.EE
+.fi
.RE
.P
There is nothing special about the way Node treats scope folders, this is
@@ -77,9 +77,9 @@ private registries, such as npm Enterprise\.
You can associate a scope with a registry at login, e\.g\.
.P
.RS 2
-.EX
+.nf
npm login \-\-registry=http://reg\.example\.com \-\-scope=@myco
-.EE
+.fi
.RE
.P
Scopes have a many\-to\-one relationship with registries: one registry can
@@ -88,9 +88,9 @@ host multiple scopes, but a scope only ever points to one registry\.
You can also associate a scope with a registry using \fBnpm config\fR:
.P
.RS 2
-.EX
+.nf
npm config set @myco:registry http://reg\.example\.com
-.EE
+.fi
.RE
.P
Once a scope is associated with a registry, any \fBnpm install\fR for a package
diff --git a/deps/npm/man/man7/npm-scripts.7 b/deps/npm/man/man7/npm-scripts.7
index 4cc93a6..9d11f46 100644
--- a/deps/npm/man/man7/npm-scripts.7
+++ b/deps/npm/man/man7/npm-scripts.7
@@ -1,9 +1,9 @@
-.TH "NPM\-SCRIPTS" "7" "September 2014" "" ""
+.TH "NPM\-SCRIPTS" "7" "October 2014" "" ""
.SH "NAME"
\fBnpm-scripts\fR \- How npm handles the "scripts" field
.SH DESCRIPTION
.P
-npm supports the "scripts" member of the package\.json script, for the
+npm supports the "scripts" property of the package\.json script, for the
following scripts:
.RS 0
.IP \(bu 2
@@ -47,10 +47,10 @@ stop and start scripts if no \fBrestart\fR script is provided\.
.RE
.P
-Additionally, arbitrary scripts can be executed by running `npm run\-script
-.P
-\fB\|\. *Pre* and *post* commands with matching names will be run for
-those as well (e\.g\.\fRpremyscript\fB,\fRmyscript\fB,\fRpostmyscript`)\.
+Additionally, arbitrary scripts can be executed by running \fBnpm
+run\-script \fR\|\. \fIPre\fR and \fIpost\fR commands with matching
+names will be run for those as well (e\.g\. \fBpremyscript\fR, \fBmyscript\fR,
+\fBpostmyscript\fR)\.
.SH NOTE: INSTALL SCRIPTS ARE AN ANTIPATTERN
.P
\fBtl;dr\fR Don't use \fBinstall\fR\|\. Use a \fB\|\.gyp\fR file for compilation, and
@@ -136,11 +136,11 @@ suites, then those executables will be added to the \fBPATH\fR for
executing the scripts\. So, if your package\.json has this:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "dependencies" : { "bar" : "0\.1\.x" }
, "scripts": { "start" : "bar \./test" } }
-.EE
+.fi
.RE
.P
then you could run \fBnpm start\fR to execute the \fBbar\fR script, which is
@@ -157,34 +157,34 @@ package\.json file, then your package scripts would have the
Configuration parameters are put in the environment with the
\fBnpm_config_\fR prefix\. For instance, you can view the effective \fBroot\fR
config by checking the \fBnpm_config_root\fR environment variable\.
-.SS Special: package\.json "config" hash
+.SS Special: package\.json "config" object
.P
The package\.json "config" keys are overwritten in the environment if
there is a config param of \fB[@]:\fR\|\. For example,
if the package\.json has this:
.P
.RS 2
-.EX
+.nf
{ "name" : "foo"
, "config" : { "port" : "8080" }
, "scripts" : { "start" : "node server\.js" } }
-.EE
+.fi
.RE
.P
and the server\.js is this:
.P
.RS 2
-.EX
+.nf
http\.createServer(\.\.\.)\.listen(process\.env\.npm_package_config_port)
-.EE
+.fi
.RE
.P
then the user could change the behavior by doing:
.P
.RS 2
-.EX
+.nf
npm config set foo:port 80
-.EE
+.fi
.RE
.SS current lifecycle event
.P
@@ -198,23 +198,23 @@ Objects are flattened following this format, so if you had
see this in the script:
.P
.RS 2
-.EX
+.nf
process\.env\.npm_package_scripts_install === "foo\.js"
-.EE
+.fi
.RE
.SH EXAMPLES
.P
For example, if your package\.json contains this:
.P
.RS 2
-.EX
+.nf
{ "scripts" :
{ "install" : "scripts/install\.js"
, "postinstall" : "scripts/install\.js"
, "uninstall" : "scripts/uninstall\.js"
}
}
-.EE
+.fi
.RE
.P
then the \fBscripts/install\.js\fR will be called for the install,
@@ -228,14 +228,14 @@ If you want to run a make command, you can do so\. This works just
fine:
.P
.RS 2
-.EX
+.nf
{ "scripts" :
{ "preinstall" : "\./configure"
, "install" : "make && make install"
, "test" : "make test"
}
}
-.EE
+.fi
.RE
.SH EXITING
.P
diff --git a/deps/npm/man/man7/removing-npm.7 b/deps/npm/man/man7/removing-npm.7
index ae3513c..b0a4fca 100644
--- a/deps/npm/man/man7/removing-npm.7
+++ b/deps/npm/man/man7/removing-npm.7
@@ -1,4 +1,4 @@
-.TH "NPM\-REMOVAL" "1" "September 2014" "" ""
+.TH "NPM\-REMOVAL" "1" "October 2014" "" ""
.SH "NAME"
\fBnpm-removal\fR \- Cleaning the Slate
.SH SYNOPSIS
@@ -6,17 +6,17 @@
So sad to see you go\.
.P
.RS 2
-.EX
+.nf
sudo npm uninstall npm \-g
-.EE
+.fi
.RE
.P
Or, if that fails, get the npm source code, and do:
.P
.RS 2
-.EX
+.nf
sudo make uninstall
-.EE
+.fi
.RE
.SH More Severe Uninstalling
.P
@@ -39,9 +39,9 @@ different prefix setting, then adjust the paths accordingly, replacing
To remove everything npm\-related manually:
.P
.RS 2
-.EX
+.nf
rm \-rf /usr/local/{lib/node{,/\.npm,_modules},bin,share/man}/npm*
-.EE
+.fi
.RE
.P
If you installed things \fIwith\fR npm, then your best bet is to uninstall
@@ -50,18 +50,18 @@ proper install\. This can help find any symlinks that are lying
around:
.P
.RS 2
-.EX
+.nf
ls \-laF /usr/local/{lib/node{,/\.npm},bin,share/man} | grep npm
-.EE
+.fi
.RE
.P
Prior to version 0\.3, npm used shim files for executables and node
modules\. To track those down, you can do the following:
.P
.RS 2
-.EX
+.nf
find /usr/local/{lib/node,bin} \-exec grep \-l npm \\{\\} \\; ;
-.EE
+.fi
.RE
.P
(This is also in the README file\.)
diff --git a/deps/npm/man/man7/semver.7 b/deps/npm/man/man7/semver.7
index c2efd3d..a6be932 100644
--- a/deps/npm/man/man7/semver.7
+++ b/deps/npm/man/man7/semver.7
@@ -1,10 +1,10 @@
-.TH "SEMVER" "7" "September 2014" "" ""
+.TH "SEMVER" "7" "October 2014" "" ""
.SH "NAME"
\fBsemver\fR \- The semantic versioner for npm
.SH Usage
.P
.RS 2
-.EX
+.nf
$ npm install semver
semver\.valid('1\.2\.3') // '1\.2\.3'
@@ -13,13 +13,13 @@ semver\.clean(' =v1\.2\.3 ') // '1\.2\.3'
semver\.satisfies('1\.2\.3', '1\.x || >=2\.5\.0 || 5\.0\.0 \- 7\.2\.3') // true
semver\.gt('1\.2\.3', '9\.8\.7') // false
semver\.lt('1\.2\.3', '9\.8\.7') // true
-.EE
+.fi
.RE
.P
As a command\-line utility:
.P
.RS 2
-.EX
+.nf
$ semver \-h
Usage: semver [ [\.\.\.]] [\-r | \-i | \-d ]
@@ -37,7 +37,7 @@ then exits failure\.
Versions are printed in ascending order, so supplying
multiple versions to the utility will just sort them\.
-.EE
+.fi
.RE
.SH Versions
.P
@@ -165,7 +165,7 @@ A partial version range is treated as an X\-Range, so the special
character is in fact optional\.
.RS 0
.IP \(bu 2
-\fB` (empty string) :=\fR*\fB:=\fR>=0\.0\.0`
+\fB""\fR (empty string) := \fB*\fR := \fB>=0\.0\.0\fR
.IP \(bu 2
\fB1\fR := \fB1\.x\.x\fR := \fB>=1\.0\.0 <2\.0\.0\fR
.IP \(bu 2
diff --git a/deps/npm/node_modules/archy/LICENSE b/deps/npm/node_modules/archy/LICENSE
new file mode 100644
index 0000000..ee27ba4
--- /dev/null
+++ b/deps/npm/node_modules/archy/LICENSE
@@ -0,0 +1,18 @@
+This software is released under the MIT license:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/deps/npm/node_modules/archy/README.markdown b/deps/npm/node_modules/archy/README.markdown
index deaba0f..ef7a5cf 100644
--- a/deps/npm/node_modules/archy/README.markdown
+++ b/deps/npm/node_modules/archy/README.markdown
@@ -1,12 +1,12 @@
-archy
-=====
+# archy
Render nested hierarchies `npm ls` style with unicode pipes.
+[![browser support](http://ci.testling.com/substack/node-archy.png)](http://ci.testling.com/substack/node-archy)
+
[![build status](https://secure.travis-ci.org/substack/node-archy.png)](http://travis-ci.org/substack/node-archy)
-example
-=======
+# example
``` js
var archy = require('archy');
@@ -50,13 +50,11 @@ beep
time!
```
-methods
-=======
+# methods
var archy = require('archy')
-archy(obj, prefix='', opts={})
-------------------------------
+## archy(obj, prefix='', opts={})
Return a string representation of `obj` with unicode pipe characters like how
`npm ls` looks.
@@ -77,8 +75,7 @@ with the current prefix.
To disable unicode results in favor of all-ansi output set `opts.unicode` to
`false`.
-install
-=======
+# install
With [npm](http://npmjs.org) do:
@@ -86,7 +83,6 @@ With [npm](http://npmjs.org) do:
npm install archy
```
-license
-=======
+# license
-MIT/X11
+MIT
diff --git a/deps/npm/node_modules/archy/examples/beep.js b/deps/npm/node_modules/archy/examples/beep.js
new file mode 100644
index 0000000..9c07047
--- /dev/null
+++ b/deps/npm/node_modules/archy/examples/beep.js
@@ -0,0 +1,24 @@
+var archy = require('../');
+var s = archy({
+ label : 'beep',
+ nodes : [
+ 'ity',
+ {
+ label : 'boop',
+ nodes : [
+ {
+ label : 'o_O',
+ nodes : [
+ {
+ label : 'oh',
+ nodes : [ 'hello', 'puny' ]
+ },
+ 'human'
+ ]
+ },
+ 'party\ntime!'
+ ]
+ }
+ ]
+});
+console.log(s);
diff --git a/deps/npm/node_modules/archy/examples/multi_line.js b/deps/npm/node_modules/archy/examples/multi_line.js
new file mode 100644
index 0000000..8afdfad
--- /dev/null
+++ b/deps/npm/node_modules/archy/examples/multi_line.js
@@ -0,0 +1,25 @@
+var archy = require('../');
+
+var s = archy({
+ label : 'beep\none\ntwo',
+ nodes : [
+ 'ity',
+ {
+ label : 'boop',
+ nodes : [
+ {
+ label : 'o_O\nwheee',
+ nodes : [
+ {
+ label : 'oh',
+ nodes : [ 'hello', 'puny\nmeat' ]
+ },
+ 'creature'
+ ]
+ },
+ 'party\ntime!'
+ ]
+ }
+ ]
+});
+console.log(s);
diff --git a/deps/npm/node_modules/archy/package.json b/deps/npm/node_modules/archy/package.json
index 81c3e26..4b3da66 100644
--- a/deps/npm/node_modules/archy/package.json
+++ b/deps/npm/node_modules/archy/package.json
@@ -1,22 +1,42 @@
{
"name": "archy",
- "version": "0.0.2",
+ "version": "1.0.0",
"description": "render nested hierarchies `npm ls` style with unicode pipes",
"main": "index.js",
- "directories": {
- "lib": ".",
- "example": "example",
- "test": "test"
- },
"devDependencies": {
- "tap": "~0.2.3"
+ "tap": "~0.3.3",
+ "tape": "~0.1.1"
},
"scripts": {
"test": "tap test"
},
+ "testling": {
+ "files": "test/*.js",
+ "browsers": {
+ "iexplore": [
+ "6.0",
+ "7.0",
+ "8.0",
+ "9.0"
+ ],
+ "chrome": [
+ "20.0"
+ ],
+ "firefox": [
+ "10.0",
+ "15.0"
+ ],
+ "safari": [
+ "5.1"
+ ],
+ "opera": [
+ "12.0"
+ ]
+ }
+ },
"repository": {
"type": "git",
- "url": "git://github.com/substack/node-archy.git"
+ "url": "http://github.com/substack/node-archy.git"
},
"keywords": [
"hierarchy",
@@ -30,23 +50,30 @@
"email": "mail@substack.net",
"url": "http://substack.net"
},
- "license": "MIT/X11",
- "engine": {
- "node": ">=0.4"
+ "license": "MIT",
+ "gitHead": "30223c16191e877bf027b15b12daf077b9b55b84",
+ "bugs": {
+ "url": "https://github.com/substack/node-archy/issues"
},
+ "homepage": "https://github.com/substack/node-archy",
+ "_id": "archy@1.0.0",
+ "_shasum": "f9c8c13757cc1dd7bc379ac77b2c62a5c2868c40",
+ "_from": "archy@>=1.0.0 <2.0.0",
+ "_npmVersion": "1.4.25",
"_npmUser": {
- "name": "isaacs",
- "email": "i@izs.me"
- },
- "_id": "archy@0.0.2",
- "dependencies": {},
- "optionalDependencies": {},
- "engines": {
- "node": "*"
- },
- "_engineSupported": true,
- "_npmVersion": "1.1.13",
- "_nodeVersion": "v0.7.7-pre",
- "_defaultsLoaded": true,
- "_from": "archy@0.0.2"
+ "name": "substack",
+ "email": "mail@substack.net"
+ },
+ "maintainers": [
+ {
+ "name": "substack",
+ "email": "mail@substack.net"
+ }
+ ],
+ "dist": {
+ "shasum": "f9c8c13757cc1dd7bc379ac77b2c62a5c2868c40",
+ "tarball": "http://registry.npmjs.org/archy/-/archy-1.0.0.tgz"
+ },
+ "directories": {},
+ "_resolved": "https://registry.npmjs.org/archy/-/archy-1.0.0.tgz"
}
diff --git a/deps/npm/node_modules/archy/test/beep.js b/deps/npm/node_modules/archy/test/beep.js
new file mode 100644
index 0000000..4ea74f9
--- /dev/null
+++ b/deps/npm/node_modules/archy/test/beep.js
@@ -0,0 +1,40 @@
+var test = require('tape');
+var archy = require('../');
+
+test('beep', function (t) {
+ var s = archy({
+ label : 'beep',
+ nodes : [
+ 'ity',
+ {
+ label : 'boop',
+ nodes : [
+ {
+ label : 'o_O',
+ nodes : [
+ {
+ label : 'oh',
+ nodes : [ 'hello', 'puny' ]
+ },
+ 'human'
+ ]
+ },
+ 'party!'
+ ]
+ }
+ ]
+ });
+ t.equal(s, [
+ 'beep',
+ 'âââ ity',
+ 'ââ⬠boop',
+ ' ââ⬠o_O',
+ ' â ââ⬠oh',
+ ' â â âââ hello',
+ ' â â âââ puny',
+ ' â âââ human',
+ ' âââ party!',
+ ''
+ ].join('\n'));
+ t.end();
+});
diff --git a/deps/npm/node_modules/archy/test/multi_line.js b/deps/npm/node_modules/archy/test/multi_line.js
new file mode 100644
index 0000000..2cf2154
--- /dev/null
+++ b/deps/npm/node_modules/archy/test/multi_line.js
@@ -0,0 +1,45 @@
+var test = require('tape');
+var archy = require('../');
+
+test('multi-line', function (t) {
+ var s = archy({
+ label : 'beep\none\ntwo',
+ nodes : [
+ 'ity',
+ {
+ label : 'boop',
+ nodes : [
+ {
+ label : 'o_O\nwheee',
+ nodes : [
+ {
+ label : 'oh',
+ nodes : [ 'hello', 'puny\nmeat' ]
+ },
+ 'creature'
+ ]
+ },
+ 'party\ntime!'
+ ]
+ }
+ ]
+ });
+ t.equal(s, [
+ 'beep',
+ 'â one',
+ 'â two',
+ 'âââ ity',
+ 'ââ⬠boop',
+ ' ââ⬠o_O',
+ ' â â wheee',
+ ' â ââ⬠oh',
+ ' â â âââ hello',
+ ' â â âââ puny',
+ ' â â meat',
+ ' â âââ creature',
+ ' âââ party',
+ ' time!',
+ ''
+ ].join('\n'));
+ t.end();
+});
diff --git a/deps/npm/node_modules/archy/test/non_unicode.js b/deps/npm/node_modules/archy/test/non_unicode.js
new file mode 100644
index 0000000..7204d33
--- /dev/null
+++ b/deps/npm/node_modules/archy/test/non_unicode.js
@@ -0,0 +1,40 @@
+var test = require('tape');
+var archy = require('../');
+
+test('beep', function (t) {
+ var s = archy({
+ label : 'beep',
+ nodes : [
+ 'ity',
+ {
+ label : 'boop',
+ nodes : [
+ {
+ label : 'o_O',
+ nodes : [
+ {
+ label : 'oh',
+ nodes : [ 'hello', 'puny' ]
+ },
+ 'human'
+ ]
+ },
+ 'party!'
+ ]
+ }
+ ]
+ }, '', { unicode : false });
+ t.equal(s, [
+ 'beep',
+ '+-- ity',
+ '`-- boop',
+ ' +-- o_O',
+ ' | +-- oh',
+ ' | | +-- hello',
+ ' | | `-- puny',
+ ' | `-- human',
+ ' `-- party!',
+ ''
+ ].join('\n'));
+ t.end();
+});
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/.npmignore b/deps/npm/node_modules/config-chain/.npmignore
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/.npmignore
rename to deps/npm/node_modules/config-chain/.npmignore
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/LICENCE b/deps/npm/node_modules/config-chain/LICENCE
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/LICENCE
rename to deps/npm/node_modules/config-chain/LICENCE
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/index.js b/deps/npm/node_modules/config-chain/index.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/index.js
rename to deps/npm/node_modules/config-chain/index.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/LICENSE b/deps/npm/node_modules/config-chain/node_modules/proto-list/LICENSE
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/LICENSE
rename to deps/npm/node_modules/config-chain/node_modules/proto-list/LICENSE
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/README.md b/deps/npm/node_modules/config-chain/node_modules/proto-list/README.md
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/README.md
rename to deps/npm/node_modules/config-chain/node_modules/proto-list/README.md
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/package.json b/deps/npm/node_modules/config-chain/node_modules/proto-list/package.json
similarity index 93%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/package.json
rename to deps/npm/node_modules/config-chain/node_modules/proto-list/package.json
index 391d876..2dff291 100644
--- a/deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/package.json
+++ b/deps/npm/node_modules/config-chain/node_modules/proto-list/package.json
@@ -29,7 +29,7 @@
"homepage": "https://github.com/isaacs/proto-list",
"_id": "proto-list@1.2.3",
"_shasum": "6235554a1bca1f0d15e3ca12ca7329d5def42bd9",
- "_from": "proto-list@>=1.2.1-0 <1.3.0-0",
+ "_from": "proto-list@~1.2.1",
"_npmVersion": "1.4.14",
"_npmUser": {
"name": "isaacs",
@@ -46,5 +46,6 @@
"tarball": "http://registry.npmjs.org/proto-list/-/proto-list-1.2.3.tgz"
},
"directories": {},
- "_resolved": "https://registry.npmjs.org/proto-list/-/proto-list-1.2.3.tgz"
+ "_resolved": "https://registry.npmjs.org/proto-list/-/proto-list-1.2.3.tgz",
+ "readme": "ERROR: No README data found!"
}
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/proto-list.js b/deps/npm/node_modules/config-chain/node_modules/proto-list/proto-list.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/proto-list.js
rename to deps/npm/node_modules/config-chain/node_modules/proto-list/proto-list.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/test/basic.js b/deps/npm/node_modules/config-chain/node_modules/proto-list/test/basic.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/node_modules/proto-list/test/basic.js
rename to deps/npm/node_modules/config-chain/node_modules/proto-list/test/basic.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/package.json b/deps/npm/node_modules/config-chain/package.json
similarity index 99%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/package.json
rename to deps/npm/node_modules/config-chain/package.json
index bec4626..a07f2f4 100644
--- a/deps/npm/node_modules/npmconf/node_modules/config-chain/package.json
+++ b/deps/npm/node_modules/config-chain/package.json
@@ -32,7 +32,7 @@
"shasum": "0943d0b7227213a20d4eaff4434f4a1c0a052cad",
"tarball": "http://registry.npmjs.org/config-chain/-/config-chain-1.1.8.tgz"
},
- "_from": "config-chain@>=1.1.8-0 <1.2.0-0",
+ "_from": "config-chain@^1.1.8",
"_npmVersion": "1.3.6",
"_npmUser": {
"name": "dominictarr",
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/readme.markdown b/deps/npm/node_modules/config-chain/readme.markdown
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/readme.markdown
rename to deps/npm/node_modules/config-chain/readme.markdown
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/broken.js b/deps/npm/node_modules/config-chain/test/broken.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/broken.js
rename to deps/npm/node_modules/config-chain/test/broken.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/broken.json b/deps/npm/node_modules/config-chain/test/broken.json
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/broken.json
rename to deps/npm/node_modules/config-chain/test/broken.json
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/chain-class.js b/deps/npm/node_modules/config-chain/test/chain-class.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/chain-class.js
rename to deps/npm/node_modules/config-chain/test/chain-class.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/env.js b/deps/npm/node_modules/config-chain/test/env.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/env.js
rename to deps/npm/node_modules/config-chain/test/env.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/find-file.js b/deps/npm/node_modules/config-chain/test/find-file.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/find-file.js
rename to deps/npm/node_modules/config-chain/test/find-file.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/get.js b/deps/npm/node_modules/config-chain/test/get.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/get.js
rename to deps/npm/node_modules/config-chain/test/get.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/ignore-unfound-file.js b/deps/npm/node_modules/config-chain/test/ignore-unfound-file.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/ignore-unfound-file.js
rename to deps/npm/node_modules/config-chain/test/ignore-unfound-file.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/ini.js b/deps/npm/node_modules/config-chain/test/ini.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/ini.js
rename to deps/npm/node_modules/config-chain/test/ini.js
diff --git a/deps/npm/node_modules/npmconf/node_modules/config-chain/test/save.js b/deps/npm/node_modules/config-chain/test/save.js
similarity index 100%
rename from deps/npm/node_modules/npmconf/node_modules/config-chain/test/save.js
rename to deps/npm/node_modules/config-chain/test/save.js
diff --git a/deps/npm/node_modules/dezalgo/dezalgo.js b/deps/npm/node_modules/dezalgo/dezalgo.js
index cdc48ae..04fd3ba 100644
--- a/deps/npm/node_modules/dezalgo/dezalgo.js
+++ b/deps/npm/node_modules/dezalgo/dezalgo.js
@@ -1,4 +1,5 @@
-module.exports = dezalgo
+var wrappy = require('wrappy')
+module.exports = wrappy(dezalgo)
var asap = require('asap')
diff --git a/deps/npm/node_modules/dezalgo/node_modules/asap/package.json b/deps/npm/node_modules/dezalgo/node_modules/asap/package.json
index 1237784..311f9fc 100644
--- a/deps/npm/node_modules/dezalgo/node_modules/asap/package.json
+++ b/deps/npm/node_modules/dezalgo/node_modules/asap/package.json
@@ -21,7 +21,7 @@
"shasum": "b2a45da5fdfa20b0496fc3768cc27c12fa916a7d",
"tarball": "http://registry.npmjs.org/asap/-/asap-1.0.0.tgz"
},
- "_from": "asap@>=1.0.0-0 <2.0.0-0",
+ "_from": "asap@>=1.0.0 <2.0.0",
"_npmVersion": "1.2.15",
"_npmUser": {
"name": "kriskowal",
diff --git a/deps/npm/node_modules/dezalgo/package.json b/deps/npm/node_modules/dezalgo/package.json
index 072e2ad..1f63e83 100644
--- a/deps/npm/node_modules/dezalgo/package.json
+++ b/deps/npm/node_modules/dezalgo/package.json
@@ -1,13 +1,14 @@
{
"name": "dezalgo",
- "version": "1.0.0",
+ "version": "1.0.1",
"description": "Contain async insanity so that the dark pony lord doesn't eat souls",
"main": "dezalgo.js",
"directories": {
"test": "test"
},
"dependencies": {
- "asap": "^1.0.0"
+ "asap": "^1.0.0",
+ "wrappy": "1"
},
"devDependencies": {
"tap": "^0.4.11"
@@ -42,11 +43,12 @@
"url": "https://github.com/npm/dezalgo/issues"
},
"homepage": "https://github.com/npm/dezalgo",
- "gitHead": "b10ea8ae0096d0e60c1acaa88d5334a9b372e4b0",
- "_id": "dezalgo@1.0.0",
- "_shasum": "050bb723f18b5617b309f26c2dc8fe6f2573b6fc",
- "_from": "dezalgo@1.0.0",
- "_npmVersion": "1.4.18",
+ "gitHead": "0a5eee75c179611f8b67f663015d68bb517e57d2",
+ "_id": "dezalgo@1.0.1",
+ "_shasum": "12bde135060807900d5a7aebb607c2abb7c76937",
+ "_from": "dezalgo@latest",
+ "_npmVersion": "2.0.0",
+ "_nodeVersion": "0.10.31",
"_npmUser": {
"name": "isaacs",
"email": "i@izs.me"
@@ -58,9 +60,8 @@
}
],
"dist": {
- "shasum": "050bb723f18b5617b309f26c2dc8fe6f2573b6fc",
- "tarball": "http://registry.npmjs.org/dezalgo/-/dezalgo-1.0.0.tgz"
+ "shasum": "12bde135060807900d5a7aebb607c2abb7c76937",
+ "tarball": "http://registry.npmjs.org/dezalgo/-/dezalgo-1.0.1.tgz"
},
- "_resolved": "https://registry.npmjs.org/dezalgo/-/dezalgo-1.0.0.tgz",
- "readme": "ERROR: No README data found!"
+ "_resolved": "https://registry.npmjs.org/dezalgo/-/dezalgo-1.0.1.tgz"
}
diff --git a/deps/npm/node_modules/dezalgo/test/basic.js b/deps/npm/node_modules/dezalgo/test/basic.js
index cc10336..da09e72 100644
--- a/deps/npm/node_modules/dezalgo/test/basic.js
+++ b/deps/npm/node_modules/dezalgo/test/basic.js
@@ -4,15 +4,19 @@ var dz = require('../dezalgo.js')
test('the dark pony', function(t) {
var n = 0
- function foo(cb) {
+ function foo(i, cb) {
cb = dz(cb)
- if (++n % 2) cb()
- else process.nextTick(cb)
+ if (++n % 2) cb(true, i)
+ else process.nextTick(cb.bind(null, false, i))
}
var called = 0
+ var order = [0, 2, 4, 6, 8, 1, 3, 5, 7, 9]
+ var o = 0
for (var i = 0; i < 10; i++) {
- foo(function() {
+ foo(i, function(cached, i) {
+ t.equal(i, order[o++])
+ t.equal(i % 2, cached ? 0 : 1)
called++
})
t.equal(called, 0)
diff --git a/deps/npm/node_modules/fs-write-stream-atomic/LICENSE b/deps/npm/node_modules/fs-write-stream-atomic/LICENSE
new file mode 100644
index 0000000..19129e3
--- /dev/null
+++ b/deps/npm/node_modules/fs-write-stream-atomic/LICENSE
@@ -0,0 +1,15 @@
+The ISC License
+
+Copyright (c) Isaac Z. Schlueter and Contributors
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
+IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
diff --git a/deps/npm/node_modules/fs-write-stream-atomic/README.md b/deps/npm/node_modules/fs-write-stream-atomic/README.md
new file mode 100644
index 0000000..9a15d05
--- /dev/null
+++ b/deps/npm/node_modules/fs-write-stream-atomic/README.md
@@ -0,0 +1,35 @@
+# fs-write-stream-atomic
+
+Like `fs.createWriteStream(...)`, but atomic.
+
+Writes to a tmp file and does an atomic `fs.rename` to move it into
+place when it's done.
+
+First rule of debugging: **It's always a race condition.**
+
+## USAGE
+
+```javascript
+var fsWriteStreamAtomic = require('fs-write-stream-atomic')
+// options are optional.
+var write = fsWriteStreamAtomic('output.txt', options)
+var read = fs.createReadStream('input.txt')
+read.pipe(write)
+
+// When the write stream emits a 'finish' or 'close' event,
+// you can be sure that it is moved into place, and contains
+// all the bytes that were written to it, even if something else
+// was writing to `output.txt` at the same time.
+```
+
+### `fsWriteStreamAtomic(filename, [options])`
+
+* `filename` {String} The file we want to write to
+* `options` {Object}
+ * `chown` {Object} User and group to set ownership after write
+ * `uid` {Number}
+ * `gid` {Number}
+ * `encoding` {String} default = 'utf8'
+ * `mode` {Number} default = `0666`
+ * `flags` {String} default = `'w'`
+
diff --git a/deps/npm/node_modules/fs-write-stream-atomic/index.js b/deps/npm/node_modules/fs-write-stream-atomic/index.js
new file mode 100644
index 0000000..42a9a88
--- /dev/null
+++ b/deps/npm/node_modules/fs-write-stream-atomic/index.js
@@ -0,0 +1,96 @@
+var fs = require('graceful-fs')
+var util = require('util')
+var crypto = require('crypto')
+
+function md5hex () {
+ var hash = crypto.createHash('md5')
+ for (var ii=0; ii=1.0.2 <1.1.0",
+ "_npmVersion": "2.1.0",
+ "_nodeVersion": "0.10.31",
+ "_npmUser": {
+ "name": "isaacs",
+ "email": "i@izs.me"
+ },
+ "maintainers": [
+ {
+ "name": "isaacs",
+ "email": "i@izs.me"
+ }
+ ],
+ "dist": {
+ "shasum": "fe0c6cec75256072b2fef8180d97e309fe3f5efb",
+ "tarball": "http://registry.npmjs.org/fs-write-stream-atomic/-/fs-write-stream-atomic-1.0.2.tgz"
+ },
+ "_resolved": "https://registry.npmjs.org/fs-write-stream-atomic/-/fs-write-stream-atomic-1.0.2.tgz"
+}
diff --git a/deps/npm/node_modules/fs-write-stream-atomic/test/basic.js b/deps/npm/node_modules/fs-write-stream-atomic/test/basic.js
new file mode 100644
index 0000000..159c596
--- /dev/null
+++ b/deps/npm/node_modules/fs-write-stream-atomic/test/basic.js
@@ -0,0 +1,89 @@
+var test = require('tap').test
+var writeStream = require('../index.js')
+var fs = require('fs')
+var path = require('path')
+
+test('basic', function (t) {
+ // open 10 write streams to the same file.
+ // then write to each of them, and to the target
+ // and verify at the end that each of them does their thing
+ var target = path.resolve(__dirname, 'test.txt')
+ var n = 10
+
+ var streams = []
+ for (var i = 0; i < n; i++) {
+ var s = writeStream(target)
+ s.on('finish', verifier('finish'))
+ s.on('close', verifier('close'))
+ streams.push(s)
+ }
+
+ var verifierCalled = 0
+ function verifier (ev) { return function () {
+ if (ev === 'close')
+ t.equal(this.__emittedFinish, true)
+ else {
+ this.__emittedFinish = true
+ t.equal(ev, 'finish')
+ }
+
+ // make sure that one of the atomic streams won.
+ var res = fs.readFileSync(target, 'utf8')
+ var lines = res.trim().split(/\n/)
+ lines.forEach(function (line) {
+ var first = lines[0].match(/\d+$/)[0]
+ var cur = line.match(/\d+$/)[0]
+ t.equal(cur, first)
+ })
+
+ var resExpr = /^first write \d+\nsecond write \d+\nthird write \d+\nfinal write \d+\n$/
+ t.similar(res, resExpr)
+
+ // should be called once for each close, and each finish
+ if (++verifierCalled === n * 2) {
+ t.end()
+ }
+ }}
+
+ // now write something to each stream.
+ streams.forEach(function (stream, i) {
+ stream.write('first write ' + i + '\n')
+ })
+
+ // wait a sec for those writes to go out.
+ setTimeout(function () {
+ // write something else to the target.
+ fs.writeFileSync(target, 'brutality!\n')
+
+ // write some more stuff.
+ streams.forEach(function (stream, i) {
+ stream.write('second write ' + i + '\n')
+ })
+
+ setTimeout(function () {
+ // Oops! Deleted the file!
+ fs.unlinkSync(target)
+
+ // write some more stuff.
+ streams.forEach(function (stream, i) {
+ stream.write('third write ' + i + '\n')
+ })
+
+ setTimeout(function () {
+ fs.writeFileSync(target, 'brutality TWO!\n')
+ streams.forEach(function (stream, i) {
+ stream.end('final write ' + i + '\n')
+ })
+ }, 50)
+ }, 50)
+ }, 50)
+})
+
+test('cleanup', function (t) {
+ fs.readdirSync(__dirname).filter(function (f) {
+ return f.match(/^test.txt/)
+ }).forEach(function (file) {
+ fs.unlinkSync(path.resolve(__dirname, file))
+ })
+ t.end()
+})
diff --git a/deps/npm/node_modules/fstream-npm/fstream-npm.js b/deps/npm/node_modules/fstream-npm/fstream-npm.js
index ca05880..863f588 100644
--- a/deps/npm/node_modules/fstream-npm/fstream-npm.js
+++ b/deps/npm/node_modules/fstream-npm/fstream-npm.js
@@ -93,6 +93,12 @@ Packer.prototype.applyIgnores = function (entry, partial, entryObj) {
// readme files should never be ignored.
if (entry.match(/^readme(\.[^\.]*)$/i)) return true
+ // license files should never be ignored.
+ if (entry.match(/^(license|licence)(\.[^\.]*)?$/i)) return true
+
+ // changelogs should never be ignored.
+ if (entry.match(/^(changes|changelog|history)(\.[^\.]*)?$/i)) return true
+
// special rules. see below.
if (entry === "node_modules" && this.packageRoot) return true
diff --git a/deps/npm/node_modules/fstream-npm/node_modules/fstream-ignore/package.json b/deps/npm/node_modules/fstream-npm/node_modules/fstream-ignore/package.json
index 558d3dc..29e5086 100644
--- a/deps/npm/node_modules/fstream-npm/node_modules/fstream-ignore/package.json
+++ b/deps/npm/node_modules/fstream-npm/node_modules/fstream-ignore/package.json
@@ -26,8 +26,6 @@
"mkdirp": ""
},
"license": "ISC",
- "readme": "# fstream-ignore\n\nA fstream DirReader that filters out files that match globs in `.ignore`\nfiles throughout the tree, like how git ignores files based on a\n`.gitignore` file.\n\nHere's an example:\n\n```javascript\nvar Ignore = require(\"fstream-ignore\")\nIgnore({ path: __dirname\n , ignoreFiles: [\".ignore\", \".gitignore\"]\n })\n .on(\"child\", function (c) {\n console.error(c.path.substr(c.root.path.length + 1))\n })\n .pipe(tar.Pack())\n .pipe(fs.createWriteStream(\"foo.tar\"))\n```\n\nThis will tar up the files in __dirname into `foo.tar`, ignoring\nanything matched by the globs in any .iginore or .gitignore file.\n",
- "readmeFilename": "README.md",
"gitHead": "290f2b621fa4f8fe3eec97307d22527fa2065375",
"bugs": {
"url": "https://github.com/isaacs/fstream-ignore/issues"
@@ -35,5 +33,23 @@
"homepage": "https://github.com/isaacs/fstream-ignore",
"_id": "fstream-ignore@1.0.1",
"_shasum": "153df36c4fa2cb006fb915dc71ac9d75f6a17c82",
- "_from": "fstream-ignore@^1.0.0"
+ "_from": "fstream-ignore@>=1.0.0 <2.0.0",
+ "_npmVersion": "1.4.22",
+ "_npmUser": {
+ "name": "isaacs",
+ "email": "i@izs.me"
+ },
+ "maintainers": [
+ {
+ "name": "isaacs",
+ "email": "i@izs.me"
+ }
+ ],
+ "dist": {
+ "shasum": "153df36c4fa2cb006fb915dc71ac9d75f6a17c82",
+ "tarball": "http://registry.npmjs.org/fstream-ignore/-/fstream-ignore-1.0.1.tgz"
+ },
+ "directories": {},
+ "_resolved": "https://registry.npmjs.org/fstream-ignore/-/fstream-ignore-1.0.1.tgz",
+ "readme": "ERROR: No README data found!"
}
diff --git a/deps/npm/node_modules/fstream-npm/package.json b/deps/npm/node_modules/fstream-npm/package.json
index 31a5af5..e7de770 100644
--- a/deps/npm/node_modules/fstream-npm/package.json
+++ b/deps/npm/node_modules/fstream-npm/package.json
@@ -6,7 +6,7 @@
},
"name": "fstream-npm",
"description": "fstream class for creating npm packages",
- "version": "1.0.0",
+ "version": "1.0.1",
"repository": {
"type": "git",
"url": "git://github.com/isaacs/fstream-npm.git"
@@ -17,15 +17,31 @@
"inherits": "2"
},
"license": "ISC",
- "readme": "# fstream-npm\n\nThis is an fstream DirReader class that will read a directory and filter\nthings according to the semantics of what goes in an npm package.\n\nFor example:\n\n```javascript\n// This will print out all the files that would be included\n// by 'npm publish' or 'npm install' of this directory.\n\nvar FN = require(\"fstream-npm\")\nFN({ path: \"./\" })\n .on(\"child\", function (e) {\n console.error(e.path.substr(e.root.path.length + 1))\n })\n```\n\n",
- "readmeFilename": "README.md",
- "gitHead": "807e0a8653ab793dc2e1b3b798e6256d09f972e7",
+ "gitHead": "4a95e1903f93dc122320349bb55e367ddd08ad6b",
"bugs": {
"url": "https://github.com/isaacs/fstream-npm/issues"
},
"homepage": "https://github.com/isaacs/fstream-npm",
- "_id": "fstream-npm@1.0.0",
+ "_id": "fstream-npm@1.0.1",
"scripts": {},
- "_shasum": "0262c95c771d393e7cf59fcfeabce621703f3d27",
- "_from": "fstream-npm@latest"
+ "_shasum": "1e35c77f0fa24f5d6367e6d447ae7d6ddb482db2",
+ "_from": "fstream-npm@>=1.0.1 <1.1.0",
+ "_npmVersion": "2.1.3",
+ "_nodeVersion": "0.10.31",
+ "_npmUser": {
+ "name": "isaacs",
+ "email": "i@izs.me"
+ },
+ "maintainers": [
+ {
+ "name": "isaacs",
+ "email": "i@izs.me"
+ }
+ ],
+ "dist": {
+ "shasum": "1e35c77f0fa24f5d6367e6d447ae7d6ddb482db2",
+ "tarball": "http://registry.npmjs.org/fstream-npm/-/fstream-npm-1.0.1.tgz"
+ },
+ "directories": {},
+ "_resolved": "https://registry.npmjs.org/fstream-npm/-/fstream-npm-1.0.1.tgz"
}
diff --git a/deps/npm/node_modules/glob/README.md b/deps/npm/node_modules/glob/README.md
index cc69164..82b7ef6 100644
--- a/deps/npm/node_modules/glob/README.md
+++ b/deps/npm/node_modules/glob/README.md
@@ -5,16 +5,7 @@ Match files using the patterns the shell uses, like stars and stuff.
This is a glob implementation in JavaScript. It uses the `minimatch`
library to do its matching.
-## Attention: node-glob users!
-
-The API has changed dramatically between 2.x and 3.x. This library is
-now 100% JavaScript, and the integer flags have been replaced with an
-options object.
-
-Also, there's an event emitter class, proper tests, and all the other
-things you've come to expect from node modules.
-
-And best of all, no compilation!
+![](oh-my-glob.gif)
## Usage
diff --git a/deps/npm/node_modules/glob/glob.js b/deps/npm/node_modules/glob/glob.js
index 6941fc7..564f3b1 100644
--- a/deps/npm/node_modules/glob/glob.js
+++ b/deps/npm/node_modules/glob/glob.js
@@ -36,10 +36,8 @@
module.exports = glob
-var fs
-try { fs = require("graceful-fs") } catch (e) { fs = require("fs") }
-
-var minimatch = require("minimatch")
+var fs = require("graceful-fs")
+, minimatch = require("minimatch")
, Minimatch = minimatch.Minimatch
, inherits = require("inherits")
, EE = require("events").EventEmitter
diff --git a/deps/npm/node_modules/glob/oh-my-glob.gif b/deps/npm/node_modules/glob/oh-my-glob.gif
new file mode 100644
index 0000000000000000000000000000000000000000..a1568c13ca695563f97e3910e34f1a47d5657f4e
GIT binary patch
literal 510360
zcmbrE^;Z-A_s5si28?bbM%U=p(W66BYBWel3kb3eHX7*`M|X%QpnwC35zz;e>x%Y9eiK(%Mrq>ye6ZoS6fJA5$EL&@HHCZifS!``%
zqGJM$(t!YAcSm=kZ5zR|5doJ-3$0ZZwQ^RAMOa#rTslZM?q+3V*X0<(BvlA@4R?v=
z`VuY)c2(86${InT2wO`NBMe5;H_jqG{%W9)7DBTUx?xEoG%qCGifgU%xI+FxB9(3o*$zRrZOuO^dUOnR`ATZB{9A)yYmN
zm{s-4Ehksv)kili;;IW&(*3-=4U*D=OyRb+QFcW!c9jX11q8dQTLC%K6SF+FwuvtF
z{4Op$7S^|Hi}GW2Qe5hBu7S&QE0fP=>}6wOENcU;GjbwKB^a)Z4Nt__)_G_p+;X{#
z_i$!4FqoTOHWKs=Hz5i>P)oHA0veLN0W?*J1exo{9wxYZ;$+9Qe(~954{>kGftfrX6tM`*!
z+F+)bO#6=70tHVGY>Z14ipg|*Y?%A9p$e0IB~iI9S0>6em%+$5#EFOvD;huP(p16Xv?H
zyj`8EAXw#YKm{aZ>8xjF
zW@3#B<1JeSUA&SkYm;mn2@WmsMs-NfYY9ee@s_pRTs-cU*W+y)x!j$TEIT0<76jYY
zB-@&J+u9_DCXz#Ib*^rbLk+>UE6KDG@6efK+DdZhinr{HcOb|A_rSL6%a7rk(Mo
zjU?Nac+;ADndsyu$
z$yO~%R!zxPP5*rd@c%o)KOqph|0IO}!K{qzuNvst7%9o4z`*~mWdEo9zc2yNT>#$5
z@?g5jBPn!j(r(o5nrCSUzTM`Bsk>{AsnQ*RjxuiD@4PTw`}>)d)0_x1hOOkbDhAm4Pps0sNP3)(NRdFRkD
z`T)`^U;YGHe!4$hrV#vSRx|4Gd9^``;NOAXz~y>tS8@M2{tu8bJE+grV^u}hhfyE4
zpFipQ@|qGXqX+#M7N}Q&`^l
zXwHfSZeM!0mFAiFZ75(r@jPdNSQ!21$6k@WRs2rz(z@iT7jvx_OzY`!En}E;Nzg%g
z;A3M8mMh`5V1>?gf4=gdm+O35r8`Qg$nLy+!yH}E^d1?%p&D2WWNLNG|G0P)S!lX_
z*nHdlSVF9}%>OZ0NtJlq77ZVw1R`57=#?ec$L^B_Dp@;v-*ypOn=+T7+K<%}6zq-l
z&glN0$t3rV|En>$J49bVbAPM(s0VbKUKXENU+R%~E;c|dG}o%QSLp6G{jskiGP5BE
z5<(fJv7oSyA~+<;IcW#vHce4k9jt6W
z=TtOSyKI3SrxkAwin`lUPq0!vS|9+Cb+UjHELF<+bR`jgUA0*TQ7%}x7W;g=@XURt
zqtCu{X!S*4Q-|6Hsix|)q(QxRhT2T8*4dU?9h=1kN_+)vN<$S=)u6-Tx=30z#WLNw~lBTSJ9tFbmVt!%Xi8=C~e$T5XGPnf~h
zR|vd@8==h%&xqcfU_Bjm36mXpCiv?(?c(xSIl>P*Cdd?#UfONQT1quw-PU*P!?GYa
z$zUa&Pr#{2$2b~p^k`z5O*$*~0^s{FGDIl&U499#?!?6J7#Qx?-aURG5+dZ@#7~ui
z!!Qm+Z<`u@zF%ZoS}6>igmR>`T1s05W<{6P(Qr~pFy$TnFbJNe#D)_3F4|B>>ZH(I
zCr#2sb6Vsyuc%q&t(0wiZnWDjC$gw?aUnljQCTc~&B|Mw2QZ`rsZ0tBFFIg{D
zwkS`%wY^aK&~!dw<7@Smi$5>uqM}Blx-*DtaWya_Ad|ex8+(TH0{uJGF;Zhn@nM;S
zp^?;L29simIQJMltR?M=VW`cUb(XkXdV$Y@0p85iYY9CqNRyoBl@Y)ujetxG?SvC}
z)4~YoB^u6VBMf^QFKH;_EN*Ub){L=iwJS}q7c=u$FYPvB#0mk-h7ml#=Qs|A(p-mc
z3!EhY8E4}3N>4>`aVI;YT&EX^$RlAqhqQ^qm@N;qW6h`D81&Y^Sn3*zNLK1-!+wgR
zIl_8FU^aSCi=E}Eb5eVYMWOAy+4{5{XT;-yRQlV;Ik-pNL~5KDKfKj6v|hBm`IE43
zdFyoJBhFgup^LFuUu_=gwNZ#&4S3di4Ea7)Y)2
zHG64vllj(r&{c(HmeEUCMX*y@9XI#R_(&p~_0;ay!FQH7Snf^p-SraXtN9xesB8n0
zNW|UrHVVD{V#f2#Oq}DNUzcWFKEv^m5dC;Dw>xbm*Y(!kYo7-0MeR|sBb*4fIbjZD
zx*kNDJtcKtwL#~%`7SG0gwmIGMn$2Y9;T0ui3;pE4MQ}Tja%=jhT8pHYl~NcGoh4&
zexe*>1kLLu6+g^2dfIK0ApWYjVzJ=$ggE~e!*UUdC}*uHQnM_LPGJyud3Zz8;6Uk1
zf101wgNusQ*#osFKc9y;!kNFqUW%hfK($oTDK^9bNC%+NmISrUZ63sPZWM)H4h^mK
zqG>Yy6k}?9N-eSoG8KJq%uMm|%#?xf>IOp---=s&3Vd5GXiWE37;uTz9Kyup2n+RFZ<`dIX%0cWv&8bcNmwx=k@V01TjY!6CB7aFcUJ>T<{W|8r!?BbNJdJ3G%NjKmzhuRWr;X#C7jufavBPm^Pkr
z(U#N1V6lkM^VXYY5SuKr`nse!t>WS9QTn7}QAZ{Yz~(H`%s=$RS4D&wmb!q(_yQ+?
z>poa2ojVJXxWD>Hl0XMYW4w}8+loZf&_lXocxZ*;t2wlUC>P!T9sv;ZI|nD!4`C#VBuYd;^w|{jo
z&w<-+{9UiPv1<;g+kjsgk(+r&`}jfCxg0H)m6TjM{_6FQgiGtYzm){$@>7_>;SB5)
zC3}?e{!JWRb8J70<8!iptxb$PdqN%UwZ_R9Bmk^x13}cw?3LnAr)^6?MC9G;7s5782e
z7tdqp-N9R(Cl=xP9+4SWDBf$w-mFyp%RBm)yJMP48QoBjo)|{{^VB0TU86zy>l-PZn{F*Y4fb;aUh4+<9>-biL?)$+8l+3o
zJIZTO)7~DW^_OKmrpvOAv|{XqP8`Fs`r(I&$hx@fL$Lt57hoS0uuKC#y9cI{Ggu`7
zV#hiXSf)pL4EgEV-&BYtHtI2K8LN44MKmxU1pvIe8M7F=%b9hh;HE#j^sP0mC+TVB
z69l#tdS3ucx*PfwfPEtwy6v2|%;_jj23$gz9z%0BByuX8LAM=2&kJeqHIw=rGHF__
z&2+<~m*F#jf|)#s?o}ouKxQi_Af4LAf#)nU$+<3D6b}Mvq58
z2J*`SvdzcRKYWYM76a`9JgMjiwz7=NHXxRtMPfGe-^Fg%p5tLZZd9zoONDaXr($0?
z!ShhyZZvKB2yLZ7;V*Sdl>#BfmXbmex6?C_MP8~zo{cU$d>*SpSt|XtUyA!#O5iC=
zl`5mTi8)v(%>(ir+@xpuW^-V|XgCne=#-=a03*?+wdnk+f%2tyjCi(+C2oy)8*qMH
z>~lxH=5gsGiu6zvJrM1Ge-$pgFYJPb8lg4Gk^FUgxzF{}7KBsOF)3nTRiZ|6cuVqO
zq&z-?A(7&4hNTZzk|{lgr?gm0(a5x3jQHOaEgN7_M%Egpl-RUIy7t*ZZhmLPeRcUL
z#UMMzNCn(GozmwKGVl!m=@#ERAGr6EzB-_k=ZPNXsyjatD^C;8Tcwr26@YgDhTc>`vNG%M%X0}+72|oS->m(Sflm?HojAf`c<30
z&euyRd+EYw!r@?M2=)OmRZQul-&gBzRFfNYin_s;+J%LMix@7cHAPn3Ro>u@
z;mr$W(6PU6&<`|yeT+Lct-nZ}uBKvXU+*Ze7a5+8hCI^40$t#gLfuHMmhNa+Z@7L1
zukY((1ADE8?~&3i6grM>8rTAqp$9}2iAupI%jA{BHKoax-MOrhis8KB113qc~U3=p}88NMIU
z65k_U*<-=0U_X7)V^FUFYV;OVdeE`hthgtf?FZ3ykO9AV@Y<|?`JAyC3w1<5L?}@0
zW1ttd^JoKNywKSt9xMN=lk2RV0@fdlAYXGO-!BsBCDUj5wnii9Z@%q@*)hEYN^?yl
zr+QgT3QIHSa~}uXS351?X}f=g4h=yA83FWG8~`0d!{3fY1C7DL;@(3e(S;cX48`|0
zedvD~ix@9JjL={eY^N>-S}+!H#k{^|Rj1-z^*R>FiS9LlLHDP7jTRu;F?{c^_D2iN
zvkX|#BHhLC+~nFw7A?`QbS56rX`DWSv88=XOa^8SLZk{uuk?+|x`{bQ)9~S(9dLXd<)$gH0qtz-HdV9AKL#<8ykh3!
z;^9ol0(fB-&=Me`iXC&yqm35=`7Dgpn~#Hbvgi7XKnr>1ElEs2aif2pIt65$s@5B3
zGUAmd2nLU>b|4~owBOr$b#1`!uS1j#BqUiMjJz?J)Pf7`1eRfMM&EQ2_Y+u*ane&l
zT3|UcXX(GdX|0!2?!c$=b;Qin0DR~hi$OS}v#Ewu55Sh$TcUXVCSTLiRU=$y*B_uZ
zZcGo|`v}goLoRZNS)^1gj(yB?iX-xE4SZ}VCv#Nb4aT=|6LcXL(D)s3BQ#&`uV;-&
zv&v0O+HZp+1fx_qcEVTClE!ik|40%pDfJCtY6Ht`2Od|gWaQa4cI2{sTmwx4`VWS0r|{6<=FwpQl7d>=IHa*Pr#QV8J9#pRo7%B
z6^$`&y$@j90ll<{tpM^1mRfJL^EDPR^`mGf6z8PAw#F^`!s-PM^;W`hD<*&Es`A#W
zx?M#={A}(H+I4VAL7%muNx-T0<|L2`R>m$H?)z6iI47f$%2ck)YO~9*I1l<~%o^zn{^7`|XzYaZ5_)ZL=eZHz)7t^<*f$M8tf}cay%R9CzI)MIO
z-N!%HYyOHJEYZM@X`=j_nk{vDjKDTn8BQAz4`TC*bj4-#tL^aD2|2HjL$5Bj2Cgt%
z^O+5p4%t-20ewXjHbd5CLJf&``Q$3$0sz=NEBA^nS6-+Ivkk0b>y6;>mIgrd>`&OP
z?l#0*;Osl3bARbW62?4^esJN%m!TQG>FUdQufJ+G{~Ov%WmvtDGaGApFVb{kQlC^=k|0y@1ZwdpK@sM*w9mVKsIRb
z(92Cgt1#?>54+S@wB5*M2=C*f&yl0Lim0ZJ(7Io|*>dOjRBGh+c|9PkFS_O+IJc0p
z;nlI&HDrsi8s1N}{}9nB-V!-b#Cbt+dGKVOTgIQ3rBvHyp^-=ln+Th1{i5jlk=1P
zqeKI@-vjjlp`T%O?}Y(ieo(7$U+%;Inz^2(V8KYRZg_x3*vAC92vR1Tta%d0RPns?
zITd!Fn7xPz48+V+{T{e!;`fdZg+;{3{l=fQTtrpn(Jnq>5-smqN-qsNo3u
ze?Mp=VJoL|ZB5lu--n}Q;-jR4f@F07mi{*nQ)R()^br4!D{9Kdb$t3o5ooDt-qRk{
zN@#1S%;qtp#~`uX`Fn(WGpP7`4CA}fxEQ9X0S5>A+8suveV})fOyq)=YFsX|xVf
zx4xBTx31M6Y0PJ%9l-RScj5D6^+9xG&8>VaJttS8f~eJBIa!TlgXg*D!vqzPI5Z(q
zn)29J1KV$_&ygLmofz*je}lL7+e2GMi3M;`bG1i1@wUfz;&ja57ouC!BIV!W0w#jh
zG=jaKxEx5kjfE~mRT^D@W%nf4BFIH1;BOAk`Y2u<2lL5GdZ?r3^
zCXpI7_nwCC+YQdxnH*a&kp(tdepv=|vt*)Ukz_^G2U^
zz<)WF`=mxM;~?zp+)J-W(w9#+lD+uN9tJ38Sqw5P
zm5g>Ec882Znl33|XD=ucwdv&7>~yE4W9iYSTcrh;!6o}@
z`C**bE(H?#oIbm8UO$}pWR{D5`6Owzwd1!_ICj+gg?|!SXsX~LWaAf+-{o|FSe9SA
zu__**Df~9I`$7X8JSWZOVpslPe1_978o{hOwM!guoGMtyB8jZRF*FyzS9_Fv&7s
zQF~%D&Thc`K%r99+M}RxDo1S~ep4bPWNJHl1@cLbxh1Is`#)9uAYyfA*)fZInZH>{y>sc|Y8M
zS>Y=)<>#sNp`69s`7Dd`HcD7kI>be;cAGzeQTH@#EQ0(h>?)newdUg;FqiDHFj7=q
zi)rAk4WU!Blx%LQ^;QWnMeDmu-AfT^RZL^}633!2xmKlhM=Cn-=UdLGOaKJ|np?O&
z_I!WuBJ<9b3shD{9|OBBdiZ>-t*vh%Ay~hU4ogt%9|QH;n%v(Arc4>L+si<%)KTCf
z6n+NdsK7Uh0=COMbZUy$M%PVVC7eAkuwHF{lNKUQnPAHAW)T9jR%Jz+N;O^0b&_zY
zZE*%RiVEkkiiZO;c{4H4*|d69+82tI1eT$%vID*kJ=+HWC2V`M!MNwt_#NQovu8ji
zMipFLyV0d@Gu8=5{ED4p)B5(dfERWjI&{B?mCe(>SNg%uiM7R-y`b>FW3`F5m^KdX
zcpE_@dLX?+^*$_!Uj1cKRVvt}r<>QBbh1o_y&gJe_B`%UWLKCc^&8mkg9+4Nr
zWx`4i#WvKT3#LXuFtSE;*z9>j;T^H<7dSSnods)|NBXiF@}`#>dfNc>s6Nj~GueEZ
zUZ7Q5=u?K!%Fuzm##>=eKEzgHBN2iCHh~15{R-|%v%`YrbhU@}wJDb!_OdlUbBp9j
z9G1A|=^9Ng^IgYzXVZ&I(mR!!C}beLtZ)2`f?54xjm^mW1;L1
zzq?w{>7~)I$=;mj5KK>ffAbAyH15$kQswoN;YQhy55$(+J{oo$4&VCnls4Ih@L~f8
zjaSF{ktDp^zt`BuDnvzWMn&uFQAHmklmGshRNH^iDW%Vd_5v>C;~@2-0y7te_uI;I
za>bBXPOj_d6!Bh+keu`#^c=9~=L^iulLup()wbE*NHTnPgFzNKqe%B&%)c@@jL|L~t6jxg1o&j<`*3XV=(h(_x)
zO)%i|9ZuF~hq@mI=KtEt3b!#BKa|DiM*krow6HV&C_P;C8wq!@-FYcb%|%dtpn_Y3
zm=Pbx3~dOx?$Q=oa}H&e6u(k0K+KlAL`g+bM&V{;;x4b|)hv28smH+ezsSD%01Uih
zDZ6E1&I`u8LWyES(5gpq%y|gsX&uTizA$Q`LJS-!^tgLjP3
zPEh^IgXZ$b_|3l+N0su9FUvd3(l2Og0p^h7Y)(m2lhF*TCMEjT#yVD$jSOHE;+gR2
zSq?{xvdhNxVl}N#&UDZXUMS8Bm`G+0*w8niaHU%j|TmnrV*|QRG4T1Q`F`tD}&I4
zWOO&4G3h{GNGU8+bh#Mgwc;6-(V3~NJaa)f@d77e?kNUFGM29K
zW|%#C_^CY9w&Bfn_ci{fC|a%X8X5)!?h02cEaD$4H_yzP_1Io;4eaGE=1p-8U*I#)
z0-9)Fw$o0_64}`1eC1ip;5k1x4xj9mSW?Q
zaBf8l8;G#qp17Lc*3rZt7GTjjEk5v&Ei5HXdyZfp3Id;6aYFhd=UYfy0C
zw*GN#`N8QKMrw$0C=M*zgNC?P(F9>Csm)`TV|$)n^X?-67l;XnNn%2gw$F
zd;2QsqtkpeXB7d&m~M=^t(U43a6a-)rb?tM-3uP|n`?FQLZR9E@5h_Tzq#g~-xBz|
zb({95T1lTy!e6UT*nI_V25LHB7=J!45j0B`!ZRC=Dw!qjaF#BpmoKxtIv)n9pbuXS
zrsXx6FQj@l1Gs;d?|4Z@<0TV$F2B_7yp%B1nXb#_s@3(ga085(5gM5hLXfU;)1pYS
zLZrkePpGDi+(n!`*&_mPh@O%({3|2;`y&D?dQn(4)x|*~c{rV{=jW~Fz1IKonm&y-
zqnHXUoPska1GywG@OfyOyC{h;s{Ze+0yS1BK)Fc?MsH6|5h0hzzvsU6aRd@=@QOl|
zat4Uo2>(HI)xh$8qPWaO1dop@SRsZ8ma&AIBEz5Peu^+l6GvWZ&}z^qocthORddOfv$f4bvjI_=}L!EobTxZWKV
zc@Q_y83m9G$qC8kKiz3(ekFSj_yzAG1e-xRyX6$R7@kdHfvLNF%fgoPQ^s7
zVGt_jJXsKiyi_?1BVk%uD`jS&Xod@d5s;dGayB`zT-!^?H+hWW#Q{Bki!Ul!j3QBq
zhOCLb1VOsFT$VZc9+B;$4)b=L%X!Du{^p)+tqkA1(?7Er?2A1EsAN_n)
z#~g&YBt}*C*+nrf=l`jvvuojG3a0zp&bXs8y$&dsj#Oql$Aw^RBD}4lMokaTlyWI1
z63zJcy>n&D(luw+uXYyxw2!$0QrQ>qSJ4Oy9K6w7cqTB9Msq&ST-eNOp2vOO_!&dz
z8sOZ}@T6#dAid$A5CC~C#Wk-90I;cW)gYyGZA$W&6g~QosE{diVe_RTN1CAq4eAj=
z0DX^DMOkJKvNPzQ8M#7N^ZF<0$0sjf=t=g4!8*I%*8gk?2nYnUpt&L9~0ApgC1#
zC(*j}ie8tkc@%tWa`%|#2Dxs@mi~_910}iTTW9#hv0ROFoGNr$jkv6?n?8L8_UQ*O
zXh8Y+0NGX5x<-clIl3z=W~;8xb)f8~^z(*aE6`((>`y4LGZ;s4Ry%nyd`ov%m=Chv
zwig98UwibocWjDvE~T=4q4hZZ9
zvkDo6A#n7^54~?Wct4xeSOba**~#+G$tKvXP^)qu4hkqzEIHO+3DI0x06A0eJG<3G
zfs3afsq8~&-eTK`hV{JKLiQfV0qV=ULzGLFj+I-sjcnIiVD_~f*M_LoKxh0Afyj?>
z;`enjSJ6&Qae~yZwk64>0hM?G#Dybq#kSl^glpx_)HOLE41s4}1OAH?t%l3BX0Cw@
zXhPQT;$@eU>oq;1&7t+zTHo4BiLOKbgV$>i@#E^#5Es4%E{-8;od8Q6akHk_t=8xz
zpM&kjEwOudVK<<9fkRoHl&if$w3nR$7eYd$XpFePfKGdoT-ytqC%*3La9z9*iC2i+
z^}@*+>RfFokt+%G4F}R+Cjd^X6vgDy-81$i3yOvCkBfD($2YA0y8hV6cSRA{Q4sdx
zm$O7ihsRuvu8vjXo1KfBH#*z`;WNG}#=A$^^3FJQ6v*6$&4$r|n75jS(iU9w{Bo_>
zJeu29if{>$7B;%o|Cdh5LX`Lrp!+N1;dKIv4g?E))kvU!%keS(HovuLoIog^~L;LF#og_*!80OJR{Qh^8$=AYM*m>t{^yiy`yhFf(&}}E8akmH(+Qq2*k?`<_1{2r%d53w++z`
zAPYN=BdG1MLBatY$CqM{3!E0gXinK43E1tJztz{9^H2n
zPES2^AvOs~I^DMiLA|xJwx(4m=KWARVUnF2lVatITz~}787uh?2;!zgAM-VXZzrXE;}TbgZn8d=n;cd767Q
zH0B_nME$bPie;b|h~8H(*XxC^wV#JS*Er>2T)IxM2
z;st}+)qFIK^aY;&;yQ>sL!vT@&Vvk;NAWaBOGqz1T{2A-!YI3zG(}PUqSxNi$UF`B
z`ZiVa5G&{+IFQ=#Mw8Xxz;~F7{lC?u%Y1qAv;}HM1;$5(-*x|Usw;w?d`c6aP3ODm
z8*XseWAOg*55#)bv*h0qrH{KWeP|U%n%p%Dh}qVORikCYq)EH6Dn@0v*LZUsXDk~r
z28+TB#Wei&_D!pezXkgEt=uA?)LYG5dvk8dGCn{Wu
zU6oXpdGql;vw-wYII#NTs>lgm2B`+4BfJC-f@dGu8PkSDiO5{S#`HNKKJv6gKs;4OjpJdQiqZl@wwuhKMzwexes~xH9qp
z=tNQ^EmNaKqr|HS7PjVeN(x^mr??-BXL|j6>~E&@cioxxaKY}Odr!xUD%4ep3wQ23
zvPd|$2jC2ZY_*%E$$htqGm5?xP7pj-6iEs;z47^=GuqoM4Ky1q_^(@htI7SsDgC2i
znm2}c83oq11hJE1PIW6k#7AB_-A-=ea#5gNa!-MDf6EX(4kVo4YgL={N>}tGd8Wy3
zIipo?bPY51_Y_3O6O=V1D4<@arz`1I%`fiKg@s^BbbjFk`@P*fJn9K3DD9PdI&Rl@nE?L+jT~WX{`}=EA)lzhc7)lx!BdqrD{#J)6A2
zXl@SB|M75z;fEOxk9xN@mlk~c*X6YQ)ectelSF=y1_zAWy`kKsM+UIb9^})QQ~5M;C})3MlXi`YJwGC7~O(
zhTdT(a*i!DnEB0BHPoBVD~7)BZLw>xzH8j^IHY_DP*NtJbW!n{RVy0HQ{lrM`>~-X
zs7;y!rntM(7&Nt{d;LeJ81(4u^dURII{(r-#`jp*44nZNgIIL;h+43T9;B~}_)Bp+
zNA-?-#
zE$b)dWs1vpwM)4>?EB@zB%PG^Q)pkfbT1tJ)s8Dt_L?3HyUUONEasGY
z%#Nb1{#^)sb{bMljov^a&!2O=u6S
z)O!DbSL;!#Dqm_J{@c2oRl=i6u_1gcSERf6Dx3gYQWBRdEpic04*I_88=bU|##^f{
zo}o3Phi^($i!PqA#EY}!Ns!~hCN7i`h*zZkx3Sl?ii7AkZgajb@vLVmuVfF2UoR-t%xc{2
zbZ$-XgUMCEm1$*9+||*se`DDtDLbEj+Fe+H|G6;1K8m?9-P&IK8GiS0acVJMDC5l5
zO!+P{HQ{A3+v`ag3Mkd%3+aWVT?vY}*pW_cEN`H+rvcz-=EYswRMh|#nb&So-L;=O
zc=^>@&1wsZE-wkieZ_BVF
z1WSL=X}h!O`16yC)RUx0`?f~5gVipOu7Xyt)!xOL(p^q
z=sV+x3BnbxTK+O2G?W&>x)ot_bL&1^Z2O+x=k7FJ{qr&t8gl-f=5C_g7(ZODX@L6_
zdHIAzfX?((o8vOhQ+8kYX&G5x_;xCkc`Y?odbLpO_CAoE9{?mvYFl7IaiZ^_jE~24
z_md7BOdh0u&FoV;5)-?P-4|?!H|wYf61n=q>-e58s?G;av99(zboKzj^37fJ3_A>3
z>9*NFTke~jwY_$4-oZ1oUj!xpc?INdsh?2R%ES=|kpY>&99dLKcuFlBa4uYXogRO)
z0q&LvAz1S?Uci)pV#%O(`VpO)$Rif5sd=Bgy
zhR^)tBc%kVPpmFt!OL@GPR;>m|4E4lgZz}Ag>>P`
z?%D_L^UKXspmZx$?=Si>al*P;+U4S&!#sw|0foY
zI4=-0<_z-}CKC`=Q|=8}GA(M6^;fvH4it2(IlD?mcDjs9E7jD?3<}Y-yn9mo@~lBX
z(VyAro%tQ1hfSAbYC@A;x~nh8#7ZiPNwuxp=eFa@FJ&1b)fSd4LkMtEoP0E64cH(W
z50|$D#TIrO2DPH-EifSQg!BwDcM40zJ3hMw*rTrZjlrLbMH63}ug_Jfss~xV{H}4!
zIgU5{*2Ua=J(kpl(r7qTz}@^BR=aIzR~JST@=8xycA4kcHcpZwtbhn>Up$l6sOBsn
zabi#0m5y0sWs{^bul`y3Nch1%7Bdy9%6d=Ffo)=7=zdrV@9g$Or`Xm{MXSiu`QMP#-_1RQ=vg`lQ+o{`2mW8V@Z*EHLnlfm7N@4HFz
zS>=M8(;#htXTX6m4@f<6)V-YMgY
zMjR7%i{|~~=yA#Iu_H9SPpLiIpSk%;>;Fr`j)p#uP)SE3!jQSJ|8ws05rG<8R
zF*-Dl@=^YhB9;M+Xuv4He>mQ@o;-!A4(lRP)9mahaAP4Fj)`^;`PlpISibyb&B9*w
zzK5m`(_LKmAcq>FFXex<2lR#20H*E9)f{&iw