embeditor-rails 1.1.1 → 2.0.0.beta

data/lib/node_modules/npm/man/man1/npm-tag.1

@@ -0,0 +1,74 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-TAG" "1" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-tag\fR \-\- Tag a published version
+.
+.SH "SYNOPSIS"
+.
+.nf
+npm tag <name>@<version> [<tag>]
+.
+.fi
+.
+.SH "DESCRIPTION"
+Tags the specified version of the package with the specified tag, or the \fB\-\-tag\fR config if not specified\.
+.
+.P
+A tag can be used when installing packages as a reference to a version instead
+of using a specific version number:
+.
+.IP "" 4
+.
+.nf
+npm install <name>@<tag>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+When installing dependencies, a preferred tagged version may be specified:
+.
+.IP "" 4
+.
+.nf
+npm install \-\-tag <tag>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+This also applies to \fBnpm dedupe\fR\|\.
+.
+.P
+Publishing a package always sets the "latest" tag to the published version\.
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help publish
+.
+.IP "\(bu" 4
+npm help install
+.
+.IP "\(bu" 4
+npm help dedupe
+.
+.IP "\(bu" 4
+npm help  registry
+.
+.IP "\(bu" 4
+npm help config
+.
+.IP "\(bu" 4
+npm help  config
+.
+.IP "\(bu" 4
+npm help  npmrc
+.
+.IP "" 0
+

data/lib/node_modules/npm/man/man1/npm-test.1

@@ -0,0 +1,42 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-TEST" "1" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-test\fR \-\- Test a package
+.
+.SH "SYNOPSIS"
+.
+.nf
+  npm test <name>
+  npm tst <name>
+.
+.fi
+.
+.SH "DESCRIPTION"
+This runs a package\'s "test" script, if one was provided\.
+.
+.P
+To run tests as a condition of installation, set the \fBnpat\fR config to
+true\.
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help run\-script
+.
+.IP "\(bu" 4
+npm help  scripts
+.
+.IP "\(bu" 4
+npm help start
+.
+.IP "\(bu" 4
+npm help restart
+.
+.IP "\(bu" 4
+npm help stop
+.
+.IP "" 0
+

data/lib/node_modules/npm/man/man1/npm-uninstall.1

@@ -0,0 +1,42 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-RM" "1" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-rm\fR \-\- Remove a package
+.
+.SH "SYNOPSIS"
+.
+.nf
+npm rm <name>
+npm uninstall <name>
+.
+.fi
+.
+.SH "DESCRIPTION"
+This uninstalls a package, completely removing everything npm installed
+on its behalf\.
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help prune
+.
+.IP "\(bu" 4
+npm help install
+.
+.IP "\(bu" 4
+npm help  folders
+.
+.IP "\(bu" 4
+npm help config
+.
+.IP "\(bu" 4
+npm help  config
+.
+.IP "\(bu" 4
+npm help  npmrc
+.
+.IP "" 0
+

data/lib/node_modules/npm/man/man1/npm-unpublish.1

@@ -0,0 +1,53 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-UNPUBLISH" "1" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-unpublish\fR \-\- Remove a package from the registry
+.
+.SH "SYNOPSIS"
+.
+.nf
+npm unpublish <name>[@<version>]
+.
+.fi
+.
+.SH "WARNING"
+\fBIt is generally considered bad behavior to remove versions of a library
+that others are depending on!\fR
+.
+.P
+Consider using the \fBdeprecate\fR command
+instead, if your intent is to encourage users to upgrade\.
+.
+.P
+There is plenty of room on the registry\.
+.
+.SH "DESCRIPTION"
+This removes a package version from the registry, deleting its
+entry and removing the tarball\.
+.
+.P
+If no version is specified, or if all versions are removed then
+the root package entry is removed from the registry entirely\.
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help deprecate
+.
+.IP "\(bu" 4
+npm help publish
+.
+.IP "\(bu" 4
+npm help  registry
+.
+.IP "\(bu" 4
+npm help adduser
+.
+.IP "\(bu" 4
+npm help owner
+.
+.IP "" 0
+

data/lib/node_modules/npm/man/man1/npm-update.1

@@ -0,0 +1,45 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-UPDATE" "1" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-update\fR \-\- Update a package
+.
+.SH "SYNOPSIS"
+.
+.nf
+npm update [\-g] [<name> [<name> \.\.\.]]
+.
+.fi
+.
+.SH "DESCRIPTION"
+This command will update all the packages listed to the latest version
+(specified by the \fBtag\fR config)\.
+.
+.P
+It will also install missing packages\.
+.
+.P
+If the \fB\-g\fR flag is specified, this command will update globally installed packages\.
+If no package name is specified, all packages in the specified location (global or local) will be updated\.
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help install
+.
+.IP "\(bu" 4
+npm help outdated
+.
+.IP "\(bu" 4
+npm help  registry
+.
+.IP "\(bu" 4
+npm help  folders
+.
+.IP "\(bu" 4
+npm help ls
+.
+.IP "" 0
+

data/lib/node_modules/npm/man/man1/npm-version.1

@@ -0,0 +1,75 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-VERSION" "1" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-version\fR \-\- Bump a package version
+.
+.SH "SYNOPSIS"
+.
+.nf
+npm version [<newversion> | major | minor | patch]
+.
+.fi
+.
+.SH "DESCRIPTION"
+Run this in a package directory to bump the version and write the new
+data back to the package\.json file\.
+.
+.P
+The \fBnewversion\fR argument should be a valid semver string, \fIor\fR a valid
+second argument to semver\.inc (one of "patch", "minor", or
+"major")\. In the second case, the existing version will be incremented
+by 1 in the specified field\.
+.
+.P
+If run in a git repo, it will also create a version commit and tag, and
+fail if the repo is not clean\.
+.
+.P
+If supplied with \fB\-\-message\fR (shorthand: \fB\-m\fR) config option, npm will
+use it as a commit message when creating a version commit\.  If the \fBmessage\fR config contains \fB%s\fR then that will be replaced with the
+resulting version number\.  For example:
+.
+.IP "" 4
+.
+.nf
+npm version patch \-m "Upgrade to %s for reasons"
+.
+.fi
+.
+.IP "" 0
+.
+.P
+If the \fBsign\-git\-tag\fR config is set, then the tag will be signed using
+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:
+.
+.IP "" 4
+.
+.nf
+$ 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:
+.
+.fi
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help init
+.
+.IP "\(bu" 4
+npm help  package\.json
+.
+.IP "\(bu" 4
+npm help  semver
+.
+.IP "" 0
+

data/lib/node_modules/npm/man/man1/npm-view.1

@@ -0,0 +1,186 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-VIEW" "1" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-view\fR \-\- View registry info
+.
+.SH "SYNOPSIS"
+.
+.nf
+npm view <name>[@<version>] [<field>[\.<subfield>]\.\.\.]
+npm v <name>[@<version>] [<field>[\.<subfield>]\.\.\.]
+.
+.fi
+.
+.SH "DESCRIPTION"
+This command shows data about a package and prints it to the stream
+referenced by the \fBoutfd\fR config, which defaults to stdout\.
+.
+.P
+To show the package registry entry for the \fBconnect\fR package, you can do
+this:
+.
+.IP "" 4
+.
+.nf
+npm view connect
+.
+.fi
+.
+.IP "" 0
+.
+.P
+The default version is "latest" if unspecified\.
+.
+.P
+Field names can be specified after the package descriptor\.
+For example, to show the dependencies of the \fBronn\fR package at version
+0\.3\.5, you could do the following:
+.
+.IP "" 4
+.
+.nf
+npm view ronn@0\.3\.5 dependencies
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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:
+.
+.IP "" 4
+.
+.nf
+npm view npm repository\.url
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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:
+.
+.IP "" 4
+.
+.nf
+npm view opts@$(npm view ronn dependencies\.opts)
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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:
+.
+.IP "" 4
+.
+.nf
+npm view express contributors\.email
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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:
+.
+.IP "" 4
+.
+.nf
+npm view express contributors[0]\.email
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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:
+.
+.IP "" 4
+.
+.nf
+npm view express contributors\.name contributors\.email
+.
+.fi
+.
+.IP "" 0
+.
+.P
+"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\.  (npm help  See \fBpackage\.json\fR for more on this\.)
+.
+.IP "" 4
+.
+.nf
+npm view npm contributors
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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:
+.
+.IP "" 4
+.
+.nf
+npm view yui3@\'>0\.5\.4\' dependencies\.jsdom
+.
+.fi
+.
+.IP "" 0
+.
+.SH "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\.
+.
+.P
+If the \-\-json flag is given, the outputted fields will be JSON\.
+.
+.P
+If the version range matches multiple versions, than each printed value
+will be prefixed with the version it applies to\.
+.
+.P
+If multiple fields are requested, than each of them are prefixed with
+the field name\.
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help search
+.
+.IP "\(bu" 4
+npm help  registry
+.
+.IP "\(bu" 4
+npm help config
+.
+.IP "\(bu" 4
+npm help  config
+.
+.IP "\(bu" 4
+npm help  npmrc
+.
+.IP "\(bu" 4
+npm help docs
+.
+.IP "" 0
+