embeditor-rails 2.0.0.beta → 2.0.0

data/lib/node_modules/npm/doc/api/npm-whoami.md

@@ -1,15 +0,0 @@
-npm-whoami(3) -- Display npm username
-=====================================
-
-## SYNOPSIS
-
-    npm.commands.whoami(args, callback)
-
-## DESCRIPTION
-
-Print the `username` config to standard output.
-
-'args' is never used and callback is never called with data.
-'args' must be present or things will break.
-
-This function is not useful programmatically

data/lib/node_modules/npm/doc/api/npm.md

@@ -1,116 +0,0 @@
-npm(3) -- node package manager
-==============================
-
-## SYNOPSIS
-
-    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
-
-@VERSION@
-
-## 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 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.
-
-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` hash, 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.
-
-For example, this would work in a node repl:
-
-    > npm = require("npm")
-    > npm.load()  // wait a sec...
-    > npm.install("dnode", "express")
-
-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"

data/lib/node_modules/npm/doc/cli/npm-adduser.md

@@ -1,38 +0,0 @@
-npm-adduser(1) -- Add a registry user account
-=============================================
-
-## SYNOPSIS
-
-    npm adduser
-
-## DESCRIPTION
-
-Create or verify a user named `<username>` in the npm registry, and
-save the credentials to the `.npmrc` file.
-
-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.
-
-To reset your password, go to <https://npmjs.org/forgot>
-
-You may use this command multiple times with the same user account to
-authorize on a new machine.
-
-## CONFIGURATION
-
-### registry
-
-Default: http://registry.npmjs.org/
-
-The base URL of the npm package registry.
-
-## SEE ALSO
-
-* npm-registry(7)
-* npm-config(1)
-* npm-config(7)
-* npmrc(5)
-* npm-owner(1)
-* npm-whoami(1)

data/lib/node_modules/npm/doc/cli/npm-bin.md

@@ -1,19 +0,0 @@
-npm-bin(1) -- Display npm bin folder
-====================================
-
-## SYNOPSIS
-
-    npm bin
-
-## DESCRIPTION
-
-Print the folder where npm will install executables.
-
-## SEE ALSO
-
-* npm-prefix(1)
-* npm-root(1)
-* npm-folders(5)
-* npm-config(1)
-* npm-config(7)
-* npmrc(5)

data/lib/node_modules/npm/doc/cli/npm-bugs.md

@@ -1,42 +0,0 @@
-npm-bugs(1) -- Bugs for a package in a web browser maybe
-========================================================
-
-## SYNOPSIS
-
-    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.
-
-### registry
-
-* Default: https://registry.npmjs.org/
-* Type: url
-
-The base URL of the npm package registry.
-
-
-## SEE ALSO
-
-* npm-docs(1)
-* npm-view(1)
-* npm-publish(1)
-* npm-registry(7)
-* npm-config(1)
-* npm-config(7)
-* npmrc(5)
-* package.json(5)

data/lib/node_modules/npm/doc/cli/npm-build.md

@@ -1,22 +0,0 @@
-npm-build(1) -- Build a package
-===============================
-
-## SYNOPSIS
-
-    npm build <package-folder>
-
-* `<package-folder>`:
-  A folder containing a `package.json` file in its root.
-
-## DESCRIPTION
-
-This is the plumbing command called by `npm link` and `npm install`.
-
-It should generally not be called directly.
-
-## SEE ALSO
-
-* npm-install(1)
-* npm-link(1)
-* npm-scripts(7)
-* package.json(5)

data/lib/node_modules/npm/doc/cli/npm-bundle.md

@@ -1,14 +0,0 @@
-npm-bundle(1) -- REMOVED
-========================
-
-## DESCRIPTION
-
-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.
-
-## SEE ALSO
-
-* npm-install(1)

data/lib/node_modules/npm/doc/cli/npm-cache.md

@@ -1,72 +0,0 @@
-npm-cache(1) -- Manipulates packages cache
-==========================================
-
-## SYNOPSIS
-
-    npm cache add <tarball file>
-    npm cache add <folder>
-    npm cache add <tarball url>
-    npm cache add <name>@<version>
-
-    npm cache ls [<path>]
-
-    npm cache clean [<path>]
-
-## DESCRIPTION
-
-Used to add, list, or clear the npm cache folder.
-
-* 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/:
-  A folder containing the package contents as they appear in the tarball.
-* .../package.json:
-  The package.json file, as npm sees it, with overlays applied and a _id attribute.
-* .../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.
-
-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 root cache folder.
-
-## SEE ALSO
-
-* npm-folders(5)
-* npm-config(1)
-* npm-config(7)
-* npmrc(5)
-* npm-install(1)
-* npm-publish(1)
-* npm-pack(1)

data/lib/node_modules/npm/doc/cli/npm-completion.md

@@ -1,29 +0,0 @@
-npm-completion(1) -- Tab Completion for npm
-===========================================
-
-## SYNOPSIS
-
-    . <(npm completion)
-
-## DESCRIPTION
-
-Enables tab-completion in all npm commands.
-
-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.
-
-## SEE ALSO
-
-* npm-developers(7)
-* npm-faq(7)
-* npm(1)

data/lib/node_modules/npm/doc/cli/npm-config.md

@@ -1,71 +0,0 @@
-npm-config(1) -- Manage the npm configuration files
-===================================================
-
-## SYNOPSIS
-
-    npm config set <key> <value> [--global]
-    npm config get <key>
-    npm config delete <key>
-    npm config list
-    npm config edit
-    npm c [set|get|delete|list]
-    npm get <key>
-    npm set <key> <value> [--global]
-
-## DESCRIPTION
-
-npm gets its config settings from the command line, environment
-variables, `npmrc` files, and in some cases, the `package.json` file.
-
-See npmrc(5) for more information about the npmrc files.
-
-See `npm-config(7)` for a more thorough discussion of the mechanisms
-involved.
-
-The `npm config` command can be used to update and edit the contents
-of the user and global npmrc files.
-
-## Sub-commands
-
-Config supports the following sub-commands:
-
-### set
-
-    npm config set key value
-
-Sets the config key to the value.
-
-If value is omitted, then it sets it to "true".
-
-### get
-
-    npm config get key
-
-Echo the config value to stdout.
-
-### list
-
-    npm config list
-
-Show all the config settings.
-
-### delete
-
-    npm config delete key
-
-Deletes the key from all configuration files.
-
-### edit
-
-    npm config edit
-
-Opens the config file in an editor.  Use the `--global` flag to edit the
-global config.
-
-## SEE ALSO
-
-* npm-folders(5)
-* npm-config(7)
-* package.json(5)
-* npmrc(5)
-* npm(1)