embeditor-rails 2.0.0.beta → 2.0.0

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

@@ -1,58 +0,0 @@
-npm-dedupe(1) -- Reduce duplication
-===================================
-
-## SYNOPSIS
-
-    npm dedupe [package names...]
-    npm ddp [package names...]
-
-## DESCRIPTION
-
-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.
-
-## SEE ALSO
-
-* npm-ls(1)
-* npm-update(1)
-* npm-install(1)

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

@@ -1,26 +0,0 @@
-npm-deprecate(1) -- Deprecate a version of a package
-====================================================
-
-## SYNOPSIS
-
-    npm deprecate <name>[@<version>] <message>
-
-## DESCRIPTION
-
-This command will update the npm registry entry for a package, providing
-a deprecation warning to all who attempt to install it.
-
-It works on version ranges as well as specific versions, so you can do
-something like this:
-
-    npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3"
-
-Note that you must be the package owner to deprecate something.  See the
-`owner` and `adduser` help topics.
-
-To un-deprecate a package, specify an empty string (`""`) for the `message` argument.
-
-## SEE ALSO
-
-* npm-publish(1)
-* npm-registry(7)

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

@@ -1,44 +0,0 @@
-npm-docs(1) -- Docs for a package in a web browser maybe
-========================================================
-
-## SYNOPSIS
-
-    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.
-
-### registry
-
-* Default: https://registry.npmjs.org/
-* Type: url
-
-The base URL of the npm package registry.
-
-
-## SEE ALSO
-
-* 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-edit.md

@@ -1,37 +0,0 @@
-npm-edit(1) -- Edit an installed package
-========================================
-
-## SYNOPSIS
-
-    npm edit <name>[@<version>]
-
-## DESCRIPTION
-
-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`.
-
-## SEE ALSO
-
-* npm-folders(5)
-* npm-explore(1)
-* npm-install(1)
-* npm-config(1)
-* npm-config(7)
-* npmrc(5)

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

@@ -1,40 +0,0 @@
-npm-explore(1) -- Browse an installed package
-=============================================
-
-## SYNOPSIS
-
-    npm explore <name>[@<version>] [ -- <cmd>]
-
-## DESCRIPTION
-
-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.
-
-This is particularly handy in the case of git submodules in the
-`node_modules` folder:
-
-    npm explore some-dependency -- git pull origin master
-
-Note that the package is *not* automatically rebuilt afterwards, so be
-sure to use `npm rebuild <pkg>` if you make any changes.
-
-## CONFIGURATION
-
-### shell
-
-* Default: SHELL environment variable, or "bash" on Posix, or "cmd" on
-  Windows
-* Type: path
-
-The shell to run for the `npm explore` command.
-
-## SEE ALSO
-
-* npm-submodule(1)
-* npm-folders(5)
-* npm-edit(1)
-* npm-rebuild(1)
-* npm-build(1)
-* npm-install(1)

data/lib/node_modules/npm/doc/cli/npm-help-search.md

@@ -1,35 +0,0 @@
-npm-help-search(1) -- Search npm help documentation
-===================================================
-
-## SYNOPSIS
-
-    npm help-search some search terms
-
-## DESCRIPTION
-
-This command will search the npm markdown documentation files for the
-terms provided, and then list the results, sorted by relevance.
-
-If only one result is found, then it will show that help topic.
-
-If the argument to `npm help` is not a known help topic, then it will
-call `help-search`.  It is rarely if ever necessary to call this
-command directly.
-
-## CONFIGURATION
-
-### long
-
-* Type: Boolean
-* Default false
-
-If true, the "long" flag will cause help-search to output context around
-where the terms were found in the documentation.
-
-If false, then help-search will just list out the help topics found.
-
-## SEE ALSO
-
-* npm(1)
-* npm-faq(7)
-* npm-help(1)

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

@@ -1,40 +0,0 @@
-npm-help(1) -- Get help on npm
-==============================
-
-## SYNOPSIS
-
-    npm help <topic>
-    npm help some search terms
-
-## DESCRIPTION
-
-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.
-
-## SEE ALSO
-
-* npm(1)
-* README
-* npm-faq(7)
-* npm-folders(5)
-* npm-config(1)
-* npm-config(7)
-* npmrc(5)
-* package.json(5)
-* npm-help-search(1)
-* npm-index(7)

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

@@ -1,25 +0,0 @@
-npm-init(1) -- Interactively create a package.json file
-=======================================================
-
-## SYNOPSIS
-
-    npm init
-
-## DESCRIPTION
-
-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.
-
-## SEE ALSO
-
-* <https://github.com/isaacs/init-package-json>
-* package.json(5)
-* npm-version(1)

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

@@ -1,252 +0,0 @@
-npm-install(1) -- Install a package
-===================================
-
-## SYNOPSIS
-
-    npm install (with no args in a package dir)
-    npm install <tarball file>
-    npm install <tarball url>
-    npm install <folder>
-    npm install <name> [--save|--save-dev|--save-optional]
-    npm install <name>@<tag>
-    npm install <name>@<version>
-    npm install <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 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://"
-
-    Example:
-
-          npm install https://github.com/indexzero/forever/tarball/v0.5.6
-
-* `npm install <name> [--save|--save-dev|--save-optional]`:
-
-    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`.
-
-    Examples:
-
-          npm install sax --save
-          npm install node-tap --save-dev
-          npm install dtrace-provider --save-optional
-
-
-    **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 <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.
-
-    Example:
-
-          npm install sax@latest
-
-* `npm install <name>@<version>`:
-
-    Install the specified version of the package.  This will fail if the version
-    has not been published to the registry.
-
-    Example:
-
-          npm install sax@0.1.1
-
-* `npm install <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)`.
-
-    Note that most version ranges must be put in quotes so that your shell will
-    treat it as a single argument.
-
-    Example:
-
-          npm install sax@">=0.1.0 <0.2.0"
-
-* `npm install <git remote url>`:
-
-    Install a package by cloning a git remote url.  The format of the git
-    url is:
-
-          <protocol>://[<user>@]<hostname><separator><path>[#<commit-ish>]
-
-    `<protocol>` is one of `git`, `git+ssh`, `git+http`, or
-    `git+https`.  If no `<commit-ish>` is specified, then `master` is
-    used.
-
-    Examples:
-
-          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
-
-You may combine multiple arguments, and even multiple types of arguments.
-For example:
-
-    npm install sax@">=0.1.0 <0.2.0" bench supervisor
-
-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.
-
-## SEE ALSO
-
-* npm-folders(5)
-* npm-update(1)
-* npm-link(1)
-* npm-rebuild(1)
-* npm-scripts(7)
-* npm-build(1)
-* npm-config(1)
-* npm-config(7)
-* npmrc(5)
-* npm-registry(7)
-* npm-folders(5)
-* npm-tag(1)
-* npm-rm(1)
-* npm-shrinkwrap(1)