embeditor-rails 2.0.0.beta → 2.0.0

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

@@ -1,17 +0,0 @@
-npm-prune(3) -- Remove extraneous packages
-==========================================
-
-## SYNOPSIS
-
-    npm.commands.prune([packages,] callback)
-
-## DESCRIPTION
-
-This command removes "extraneous" packages.
-
-The first parameter is optional, and it specifies packages to be removed.
-
-No packages are specified, then all packages will be checked.
-
-Extraneous packages are packages that are not listed on the parent
-package's dependencies list.

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

@@ -1,30 +0,0 @@
-npm-publish(3) -- Publish a package
-===================================
-
-## SYNOPSIS
-
-    npm.commands.publish([packages,] callback)
-
-## DESCRIPTION
-
-Publishes a package to the registry so that it can be installed by name.
-Possible values in the 'packages' array are:
-
-* `<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.
-
-If the package array is empty, npm will try to publish something in the
-current working directory.
-
-This command could fails if one of the packages specified already exists in
-the registry.  Overwrites when the "force" environment variable is set.
-
-## SEE ALSO
-
-* npm-registry(7)
-* npm-adduser(1)
-* npm-owner(3)

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

@@ -1,16 +0,0 @@
-npm-rebuild(3) -- Rebuild a package
-===================================
-
-## SYNOPSIS
-
-    npm.commands.rebuild([packages,] callback)
-
-## DESCRIPTION
-
-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`

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

@@ -1,19 +0,0 @@
-npm-repo(3) -- Open package repository page in the browser
-========================================================
-
-## SYNOPSIS
-
-    npm.commands.repo(package, callback)
-
-## 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.
-
-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.

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

@@ -1,22 +0,0 @@
-npm-restart(3) -- Start a package
-=================================
-
-## SYNOPSIS
-
-    npm.commands.restart(packages, callback)
-
-## 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.
-
-npm can run tests on multiple packages. Just specify multiple packages
-in the `packages` parameter.
-
-## SEE ALSO
-
-* npm-start(3)
-* npm-stop(3)

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

@@ -1,15 +0,0 @@
-npm-root(3) -- Display npm root
-===============================
-
-## SYNOPSIS
-
-    npm.commands.root(args, callback)
-
-## DESCRIPTION
-
-Print the effective `node_modules` folder to standard out.
-
-'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-run-script.md

@@ -1,27 +0,0 @@
-npm-run-script(3) -- Run arbitrary package scripts
-==================================================
-
-## SYNOPSIS
-
-    npm.commands.run-script(args, callback)
-
-## DESCRIPTION
-
-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.
-
-## SEE ALSO
-
-* npm-scripts(7)
-* npm-test(3)
-* npm-start(3)
-* npm-restart(3)
-* npm-stop(3)

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

@@ -1,35 +0,0 @@
-npm-search(3) -- Search for packages
-====================================
-
-## SYNOPSIS
-
-    npm.commands.search(searchTerms, [silent,] [staleness,] callback)
-
-## DESCRIPTION
-
-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).

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

@@ -1,20 +0,0 @@
-npm-shrinkwrap(3) -- programmatically generate package shrinkwrap file
-====================================================
-
-## SYNOPSIS
-
-    npm.commands.shrinkwrap(args, [silent,] callback)
-
-## DESCRIPTION
-
-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.

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

@@ -1,13 +0,0 @@
-npm-start(3) -- Start a package
-===============================
-
-## SYNOPSIS
-
-    npm.commands.start(packages, callback)
-
-## DESCRIPTION
-
-This runs a package's "start" script, if one was provided.
-
-npm can run tests on multiple packages. Just specify multiple packages
-in the `packages` parameter.

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

@@ -1,13 +0,0 @@
-npm-stop(3) -- Stop a package
-=============================
-
-## SYNOPSIS
-
-    npm.commands.stop(packages, callback)
-
-## DESCRIPTION
-
-This runs a package's "stop" script, if one was provided.
-
-npm can run stop on multiple packages. Just specify multiple packages
-in the `packages` parameter.

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

@@ -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/<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

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

@@ -1,23 +0,0 @@
-npm-tag(3) -- Tag a published version
-=====================================
-
-## SYNOPSIS
-
-    npm.commands.tag(package@version, tag, callback)
-
-## DESCRIPTION
-
-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.

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

@@ -1,16 +0,0 @@
-npm-test(3) -- Test a package
-=============================
-
-## SYNOPSIS
-
-      npm.commands.test(packages, callback)
-
-## DESCRIPTION
-
-This runs a package's "test" script, if one was provided.
-
-To run tests as a condition of installation, set the `npat` config to
-true.
-
-npm can run tests on multiple packages. Just specify multiple packages
-in the `packages` parameter.

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

@@ -1,16 +0,0 @@
-npm-uninstall(3) -- uninstall a package programmatically
-========================================================
-
-## SYNOPSIS
-
-    npm.commands.uninstall(packages, callback)
-
-## DESCRIPTION
-
-This acts much the same ways as uninstalling on the command-line.
-
-The 'packages' parameter is an array of strings. Each element in the array is
-the name of a package to be uninstalled.
-
-Finally, 'callback' is a function that will be called when all packages have been
-uninstalled or when an error has been encountered.

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

@@ -1,20 +0,0 @@
-npm-unpublish(3) -- Remove a package from the registry
-======================================================
-
-## SYNOPSIS
-
-    npm.commands.unpublish(package, callback)
-
-## DESCRIPTION
-
-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.

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

@@ -1,11 +0,0 @@
-npm-update(3) -- Update a package
-=================================
-
-## SYNOPSIS
-    npm.commands.update(packages, callback)
-
-# DESCRIPTION
-
-Updates a package, upgrading it to the latest version. It also installs any missing packages.
-
-The 'packages' argument is an array of packages to update. The 'callback' parameter will be called when done or when an error occurs.

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

@@ -1,18 +0,0 @@
-npm-version(3) -- Bump a package version
-========================================
-
-## SYNOPSIS
-
-    npm.commands.version(newversion, callback)
-
-## DESCRIPTION
-
-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.

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

@@ -1,93 +0,0 @@
-npm-view(3) -- View registry info
-=================================
-
-## SYNOPSIS
-
-    npm.commands.view(args, [silent,] callback)
-
-## DESCRIPTION
-
-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:
-
-    npm.commands.view(["ronn@0.3.5", "dependencies"], callback)
-
-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.commands.view(["npm", "repository.url"], callback)
-
-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.commands.view(["express", "contributors.email"], callback)
-
-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.commands.view(["express", "contributors[0].email"], callback)
-
-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:
-
-    npm.commands.view(["express", "contributors.name", "contributors.email"], callback)
-
-"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.)
-
-    npm.commands.view(["npm", "contributors"], callback)
-
-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.commands.view(["yui3@'>0.5.4'", "dependencies.jsdom"], callback)
-
-## 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 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:
-
-    { <version>:
-      { <field>: <value>
-      , ... }
-    , ... }
-
-corresponding to the list of fields selected.