embeditor-rails 2.0.0.beta → 2.0.0

data/lib/node_modules/npm/man/man3/npm-docs.3

@@ -1,28 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-DOCS" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-docs\fR \-\- Docs for a package in a web browser maybe
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.docs(package, callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-This command tries to guess at the likely location of a package\'s
-documentation URL, and then tries to open it using the \fB\-\-browser\fR
-config param\.
-.
-.P
-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\.
-.
-.P
-This command will launch a browser, so this command may not be the most
-friendly for programmatic use\.

data/lib/node_modules/npm/man/man3/npm-edit.3

@@ -1,35 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-EDIT" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-edit\fR \-\- Edit an installed package
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.edit(package, callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-Opens the package folder in the default editor (or whatever you\'ve
-configured as the npm \fBeditor\fR config \-\- see \fBnpm help config\fR\|\.)
-.
-.P
-After it has been edited, the package is rebuilt so as to pick up any
-changes in compiled packages\.
-.
-.P
-For instance, you can do \fBnpm install connect\fR to install connect
-into your package, and then \fBnpm\.commands\.edit(["connect"], callback)\fR
-to make a few changes to your locally installed copy\.
-.
-.P
-The first parameter is a string array with a single element, the package
-to open\. The package can optionally have a version number attached\.
-.
-.P
-Since this command opens an editor in a new process, be careful about where
-and how this is used\.

data/lib/node_modules/npm/man/man3/npm-explore.3

@@ -1,28 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-EXPLORE" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-explore\fR \-\- Browse an installed package
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.explore(args, callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-Spawn a subshell in the directory of the installed package specified\.
-.
-.P
-If a command is specified, then it is run in the subshell, which then
-immediately terminates\.
-.
-.P
-Note that the package is \fInot\fR automatically rebuilt afterwards, so be
-sure to use \fBnpm rebuild <pkg>\fR if you make any changes\.
-.
-.P
-The first element in the \'args\' parameter must be a package name\.  After that is the optional command, which can be any number of strings\. All of the strings will be combined into one, space\-delimited command\.

data/lib/node_modules/npm/man/man3/npm-help-search.3

@@ -1,51 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-HELP\-SEARCH" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-help-search\fR \-\- Search the help pages
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.helpSearch(args, [silent,] callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-This command is rarely useful, but it exists in the rare case that it is\.
-.
-.P
-This command takes an array of search terms and returns the help pages that
-match in order of best match\.
-.
-.P
-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:
-.
-.IP "\(bu" 4
-hits:
-A map of args to number of hits on that arg\. For example, {"npm": 3}
-.
-.IP "\(bu" 4
-found:
-Total number of unique args that matched\.
-.
-.IP "\(bu" 4
-totalHits:
-Total number of hits\.
-.
-.IP "\(bu" 4
-lines:
-An array of all matching lines (and some adjacent lines)\.
-.
-.IP "\(bu" 4
-file:
-Name of the file that matched
-.
-.IP "" 0
-.
-.P
-The silent parameter is not neccessary not used, but it may in the future\.

data/lib/node_modules/npm/man/man3/npm-init.3

@@ -1,39 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "INIT" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBinit\fR \-\- Interactively create a package\.json file
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.init(args, callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-This will ask you a bunch of questions, and then write a package\.json for you\.
-.
-.P
-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\.
-.
-.P
-If you already have a package\.json file, it\'ll read that first, and default to
-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
-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\.
-.
-.SH "SEE ALSO"
-npm help  package\.json

data/lib/node_modules/npm/man/man3/npm-install.3

@@ -1,29 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-INSTALL" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-install\fR \-\- install a package programmatically
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.install([where,] packages, callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-This acts much the same ways as installing on the command\-line\.
-.
-.P
-The \'where\' parameter is optional and only used internally, and it specifies
-where the packages should be installed to\.
-.
-.P
-The \'packages\' parameter is an array of strings\. Each element in the array is
-the name of a package to be installed\.
-.
-.P
-Finally, \'callback\' is a function that will be called when all packages have been
-installed or when an error has been encountered\.

data/lib/node_modules/npm/man/man3/npm-link.3

@@ -1,53 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-LINK" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-link\fR \-\- Symlink a package folder
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.command\.link(callback)
-npm\.command\.link(packages, callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-Package linking is a two\-step process\.
-.
-.P
-Without parameters, link will create a globally\-installed
-symbolic link from \fBprefix/package\-name\fR to the current folder\.
-.
-.P
-With a parameters, link will create a symlink from the local \fBnode_modules\fR
-folder to the global symlink\.
-.
-.P
-When creating tarballs for \fBnpm publish\fR, the linked packages are
-"snapshotted" to their current state by resolving the symbolic links\.
-.
-.P
-This is
-handy for installing your own stuff, so that you can work on it and test it
-iteratively without having to continually rebuild\.
-.
-.P
-For example:
-.
-.IP "" 4
-.
-.nf
-npm\.commands\.link(cb)           # creates global link from the cwd
-                                # (say redis package)
-npm\.commands\.link(\'redis\', cb)  # link\-install the package
-.
-.fi
-.
-.IP "" 0
-.
-.P
-Now, any changes to the redis package will be reflected in
-the package in the current working directory

data/lib/node_modules/npm/man/man3/npm-load.3

@@ -1,44 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-LOAD" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-load\fR \-\- Load config settings
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.load(conf, cb)
-.
-.fi
-.
-.SH "DESCRIPTION"
-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\.
-.
-.P
-The first parameter should follow a similar structure as the package\.json
-config object\.
-.
-.P
-For example, to emulate the \-\-dev flag, pass an object that looks like this:
-.
-.IP "" 4
-.
-.nf
-{
-  "dev": true
-}
-.
-.fi
-.
-.IP "" 0
-.
-.P
-For a list of all the available command\-line configs, see \fBnpm help config\fR

data/lib/node_modules/npm/man/man3/npm-ls.3

@@ -1,86 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-LS" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-ls\fR \-\- List installed packages
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.ls(args, [silent,] callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-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\.
-.
-.P
-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 \fBglobal\fR to list global packages\.
-.
-.P
-It will print out extraneous, missing, and invalid packages\.
-.
-.P
-If the silent parameter is set to true, nothing will be output to the screen,
-but the data will still be returned\.
-.
-.P
-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\.
-.
-.SH "CONFIGURATION"
-.
-.SS "long"
-.
-.IP "\(bu" 4
-Default: false
-.
-.IP "\(bu" 4
-Type: Boolean
-.
-.IP "" 0
-.
-.P
-Show extended information\.
-.
-.SS "parseable"
-.
-.IP "\(bu" 4
-Default: false
-.
-.IP "\(bu" 4
-Type: Boolean
-.
-.IP "" 0
-.
-.P
-Show parseable output instead of tree view\.
-.
-.SS "global"
-.
-.IP "\(bu" 4
-Default: false
-.
-.IP "\(bu" 4
-Type: Boolean
-.
-.IP "" 0
-.
-.P
-List packages in the global install prefix instead of in the current
-project\.
-.
-.P
-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\.

data/lib/node_modules/npm/man/man3/npm-outdated.3

@@ -1,21 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-OUTDATED" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-outdated\fR \-\- Check for outdated packages
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.outdated([packages,] callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-This command will check the registry to see if the specified packages are
-currently outdated\.
-.
-.P
-If the \'packages\' parameter is left out, npm will check all packages\.

data/lib/node_modules/npm/man/man3/npm-owner.3

@@ -1,52 +0,0 @@
-.\" Generated with Ronnjs 0.3.8
-.\" http://github.com/kapouer/ronnjs/
-.
-.TH "NPM\-OWNER" "3" "February 2014" "" ""
-.
-.SH "NAME"
-\fBnpm-owner\fR \-\- Manage package owners
-.
-.SH "SYNOPSIS"
-.
-.nf
-npm\.commands\.owner(args, callback)
-.
-.fi
-.
-.SH "DESCRIPTION"
-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):
-.
-.IP "\(bu" 4
-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\.
-.
-.IP "\(bu" 4
-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\.
-.
-.IP "\(bu" 4
-rm (user, package):
-Remove a user from the package owner list\.  This immediately revokes their
-privileges\.
-.
-.IP "" 0
-.
-.P
-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\.
-.
-.SH "SEE ALSO"
-.
-.IP "\(bu" 4
-npm apihelp publish
-.
-.IP "\(bu" 4
-npm help  registry
-.
-.IP "" 0
-