embeditor-rails 1.1.1 → 2.0.0.beta

data/lib/node_modules/npm/man/man7/npm-index.7

@@ -0,0 +1,307 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-INDEX" "7" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-index\fR \-\- Index of all npm documentation
+.
+npm help .SH "README"
+node package manager
+.
+npm help .SH "npm"
+node package manager
+.
+npm help .SH "npm\-adduser"
+Add a registry user account
+.
+npm help .SH "npm\-bin"
+Display npm bin folder
+.
+npm help .SH "npm\-bugs"
+Bugs for a package in a web browser maybe
+.
+npm help .SH "npm\-build"
+Build a package
+.
+npm help .SH "npm\-bundle"
+REMOVED
+.
+npm help .SH "npm\-cache"
+Manipulates packages cache
+.
+npm help .SH "npm\-completion"
+Tab Completion for npm
+.
+npm help .SH "npm\-config"
+Manage the npm configuration files
+.
+npm help .SH "npm\-dedupe"
+Reduce duplication
+.
+npm help .SH "npm\-deprecate"
+Deprecate a version of a package
+.
+npm help .SH "npm\-docs"
+Docs for a package in a web browser maybe
+.
+npm help .SH "npm\-edit"
+Edit an installed package
+.
+npm help .SH "npm\-explore"
+Browse an installed package
+.
+npm help .SH "npm\-help\-search"
+Search npm help documentation
+.
+npm help .SH "npm\-help"
+Get help on npm
+.
+npm help .SH "npm\-init"
+Interactively create a package\.json file
+.
+npm help .SH "npm\-install"
+Install a package
+.
+npm help .SH "npm\-link"
+Symlink a package folder
+.
+npm help .SH "npm\-ls"
+List installed packages
+.
+npm help .SH "npm\-outdated"
+Check for outdated packages
+.
+npm help .SH "npm\-owner"
+Manage package owners
+.
+npm help .SH "npm\-pack"
+Create a tarball from a package
+.
+npm help .SH "npm\-prefix"
+Display prefix
+.
+npm help .SH "npm\-prune"
+Remove extraneous packages
+.
+npm help .SH "npm\-publish"
+Publish a package
+.
+npm help .SH "npm\-rebuild"
+Rebuild a package
+.
+npm help .SH "npm\-repo"
+Open package repository page in the browser
+.
+npm help .SH "npm\-restart"
+Start a package
+.
+npm help .SH "npm\-rm"
+Remove a package
+.
+npm help .SH "npm\-root"
+Display npm root
+.
+npm help .SH "npm\-run\-script"
+Run arbitrary package scripts
+.
+npm help .SH "npm\-search"
+Search for packages
+.
+npm help .SH "npm\-shrinkwrap"
+Lock down dependency versions
+.
+npm help .SH "npm\-star"
+Mark your favorite packages
+.
+npm help .SH "npm\-stars"
+View packages marked as favorites
+.
+npm help .SH "npm\-start"
+Start a package
+.
+npm help .SH "npm\-stop"
+Stop a package
+.
+npm help .SH "npm\-submodule"
+Add a package as a git submodule
+.
+npm help .SH "npm\-tag"
+Tag a published version
+.
+npm help .SH "npm\-test"
+Test a package
+.
+npm help .SH "npm\-uninstall"
+Remove a package
+.
+npm help .SH "npm\-unpublish"
+Remove a package from the registry
+.
+npm help .SH "npm\-update"
+Update a package
+.
+npm help .SH "npm\-version"
+Bump a package version
+.
+npm help .SH "npm\-view"
+View registry info
+.
+npm help .SH "npm\-whoami"
+Display npm username
+.
+npm apihelp .SH "npm"
+node package manager
+.
+npm apihelp .SH "npm\-bin"
+Display npm bin folder
+.
+npm apihelp .SH "npm\-bugs"
+Bugs for a package in a web browser maybe
+.
+npm apihelp .SH "npm\-commands"
+npm commands
+.
+npm apihelp .SH "npm\-config"
+Manage the npm configuration files
+.
+npm apihelp .SH "npm\-deprecate"
+Deprecate a version of a package
+.
+npm apihelp .SH "npm\-docs"
+Docs for a package in a web browser maybe
+.
+npm apihelp .SH "npm\-edit"
+Edit an installed package
+.
+npm apihelp .SH "npm\-explore"
+Browse an installed package
+.
+npm apihelp .SH "npm\-help\-search"
+Search the help pages
+.
+npm apihelp .SH "npm\-init"
+Interactively create a package\.json file
+.
+npm apihelp .SH "npm\-install"
+install a package programmatically
+.
+npm apihelp .SH "npm\-link"
+Symlink a package folder
+.
+npm apihelp .SH "npm\-load"
+Load config settings
+.
+npm apihelp .SH "npm\-ls"
+List installed packages
+.
+npm apihelp .SH "npm\-outdated"
+Check for outdated packages
+.
+npm apihelp .SH "npm\-owner"
+Manage package owners
+.
+npm apihelp .SH "npm\-pack"
+Create a tarball from a package
+.
+npm apihelp .SH "npm\-prefix"
+Display prefix
+.
+npm apihelp .SH "npm\-prune"
+Remove extraneous packages
+.
+npm apihelp .SH "npm\-publish"
+Publish a package
+.
+npm apihelp .SH "npm\-rebuild"
+Rebuild a package
+.
+npm apihelp .SH "npm\-repo"
+Open package repository page in the browser
+.
+npm apihelp .SH "npm\-restart"
+Start a package
+.
+npm apihelp .SH "npm\-root"
+Display npm root
+.
+npm apihelp .SH "npm\-run\-script"
+Run arbitrary package scripts
+.
+npm apihelp .SH "npm\-search"
+Search for packages
+.
+npm apihelp .SH "npm\-shrinkwrap"
+programmatically generate package shrinkwrap file
+.
+npm apihelp .SH "npm\-start"
+Start a package
+.
+npm apihelp .SH "npm\-stop"
+Stop a package
+.
+npm apihelp .SH "npm\-submodule"
+Add a package as a git submodule
+.
+npm apihelp .SH "npm\-tag"
+Tag a published version
+.
+npm apihelp .SH "npm\-test"
+Test a package
+.
+npm apihelp .SH "npm\-uninstall"
+uninstall a package programmatically
+.
+npm apihelp .SH "npm\-unpublish"
+Remove a package from the registry
+.
+npm apihelp .SH "npm\-update"
+Update a package
+.
+npm apihelp .SH "npm\-version"
+Bump a package version
+.
+npm apihelp .SH "npm\-view"
+View registry info
+.
+npm apihelp .SH "npm\-whoami"
+Display npm username
+.
+npm help  .SH "npm\-folders"
+Folder Structures Used by npm
+.
+npm help  .SH "npmrc"
+The npm config files
+.
+npm help  .SH "package\.json"
+Specifics of npm\'s package\.json handling
+.
+npm help  .SH "npm\-coding\-style"
+npm\'s "funny" coding style
+.
+npm help  .SH "npm\-config"
+More than you probably want to know about npm configuration
+.
+npm help  .SH "npm\-developers"
+Developer Guide
+.
+npm help  .SH "npm\-disputes"
+Handling Module Name Disputes
+.
+npm help  .SH "npm\-faq"
+Frequently Asked Questions
+.
+npm help  .SH "npm\-index"
+Index of all npm documentation
+.
+npm help  .SH "npm\-registry"
+The JavaScript Package Registry
+.
+npm help  .SH "npm\-scripts"
+How npm handles the "scripts" field
+.
+npm help  .SH "removing\-npm"
+Cleaning the Slate
+.
+npm help  .SH "semver"
+The semantic versioner for npm

data/lib/node_modules/npm/man/man7/npm-registry.7

@@ -0,0 +1,82 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-REGISTRY" "7" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-registry\fR \-\- The JavaScript Package Registry
+.
+.SH "DESCRIPTION"
+To resolve packages by name and version, npm talks to a registry website
+that implements the CommonJS Package Registry specification for reading
+package info\.
+.
+.P
+Additionally, npm\'s package registry implementation supports several
+write APIs as well, to allow for publishing packages and managing user
+account information\.
+.
+.P
+The official public npm registry is at \fIhttp://registry\.npmjs\.org/\fR\|\.  It
+is powered by a CouchDB database at \fIhttp://isaacs\.iriscouch\.com/registry\fR\|\.  The code for the couchapp is
+available at \fIhttp://github\.com/npm/npmjs\.org\fR\|\.  npm user accounts
+are CouchDB users, stored in the \fIhttp://isaacs\.iriscouch\.com/_users\fR
+database\.
+.
+.P
+npm help  npm help The registry URL is supplied by the \fBregistry\fR config parameter\.  See \fBnpm\-config\fR, \fBnpmrcnpm help  \fR, and \fBnpm\-config\fR for more on managing
+npm\'s configuration\.
+.
+.SH "Can I run my own private registry?"
+Yes!
+.
+.P
+The easiest way is to replicate the couch database, and use the same (or
+similar) design doc to implement the APIs\.
+.
+.P
+If you set up continuous replication from the official CouchDB, and then
+set your internal CouchDB as the registry config, then you\'ll be able
+to read any published packages, in addition to your private ones, and by
+default will only publish internally\.  If you then want to publish a
+package for the whole world to see, you can simply override the \fB\-\-registry\fR config for that command\.
+.
+.SH "I don't want my package published in the official registry\. It's private\."
+Set \fB"private": true\fR in your package\.json to prevent it from being
+published at all, or \fB"publishConfig":{"registry":"http://my\-internal\-registry\.local"}\fR
+to force it to be published only to your internal registry\.
+.
+.P
+npm help  See \fBpackage\.json\fR for more info on what goes in the package\.json file\.
+.
+.SH "Will you replicate from my registry into the public one?"
+No\.  If you want things to be public, then publish them into the public
+registry using npm\.  What little security there is would be for nought
+otherwise\.
+.
+.SH "Do I have to use couchdb to build a registry that npm can talk to?"
+No, but it\'s way easier\.  Basically, yes, you do, or you have to
+effectively implement the entire CouchDB API anyway\.
+.
+.SH "Is there a website or something to see package docs and such?"
+Yes, head over to \fIhttps://npmjs\.org/\fR
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help config
+.
+.IP "\(bu" 4
+npm help  config
+.
+.IP "\(bu" 4
+npm help  npmrc
+.
+.IP "\(bu" 4
+npm help  developers
+.
+.IP "\(bu" 4
+npm help  disputes
+.
+.IP "" 0
+

data/lib/node_modules/npm/man/man7/npm-scripts.7

@@ -0,0 +1,354 @@
+.\" Generated with Ronnjs 0.3.8
+.\" http://github.com/kapouer/ronnjs/
+.
+.TH "NPM\-SCRIPTS" "7" "February 2014" "" ""
+.
+.SH "NAME"
+\fBnpm-scripts\fR \-\- How npm handles the "scripts" field
+.
+.SH "DESCRIPTION"
+npm supports the "scripts" member of the package\.json script, for the
+following scripts:
+.
+.IP "\(bu" 4
+prepublish:
+Run BEFORE the package is published\.  (Also run on local \fBnpm
+install\fR without any arguments\.)
+.
+.IP "\(bu" 4
+publish, postpublish:
+Run AFTER the package is published\.
+.
+.IP "\(bu" 4
+preinstall:
+Run BEFORE the package is installed
+.
+.IP "\(bu" 4
+install, postinstall:
+Run AFTER the package is installed\.
+.
+.IP "\(bu" 4
+preuninstall, uninstall:
+Run BEFORE the package is uninstalled\.
+.
+.IP "\(bu" 4
+postuninstall:
+Run AFTER the package is uninstalled\.
+.
+.IP "\(bu" 4
+preupdate:
+Run BEFORE the package is updated with the update command\.
+.
+.IP "\(bu" 4
+update, postupdate:
+Run AFTER the package is updated with the update command\.
+.
+.IP "\(bu" 4
+pretest, test, posttest:
+Run by the \fBnpm test\fR command\.
+.
+.IP "\(bu" 4
+prestop, stop, poststop:
+Run by the \fBnpm stop\fR command\.
+.
+.IP "\(bu" 4
+prestart, start, poststart:
+Run by the \fBnpm start\fR command\.
+.
+.IP "\(bu" 4
+prerestart, restart, postrestart:
+Run by the \fBnpm restart\fR command\. Note: \fBnpm restart\fR will run the
+stop and start scripts if no \fBrestart\fR script is provided\.
+.
+.IP "" 0
+.
+.P
+Additionally, arbitrary scripts can be run by doing \fBnpm run\-script <stage> <pkg>\fR\|\.
+.
+.SH "NOTE: INSTALL SCRIPTS ARE AN ANTIPATTERN"
+\fBtl;dr\fR Don\'t use \fBinstall\fR\|\.  Use a \fB\|\.gyp\fR file for compilation, and \fBprepublish\fR for anything else\.
+.
+.P
+You should almost never have to explicitly set a \fBpreinstall\fR or \fBinstall\fR script\.  If you are doing this, please consider if there is
+another option\.
+.
+.P
+The only valid use of \fBinstall\fR or \fBpreinstall\fR scripts is for
+compilation which must be done on the target architecture\.  In early
+versions of node, this was often done using the \fBnode\-waf\fR scripts, or
+a standalone \fBMakefile\fR, and early versions of npm required that it be
+explicitly set in package\.json\.  This was not portable, and harder to
+do properly\.
+.
+.P
+In the current version of node, the standard way to do this is using a \fB\|\.gyp\fR file\.  If you have a file with a \fB\|\.gyp\fR extension in the root
+of your package, then npm will run the appropriate \fBnode\-gyp\fR commands
+automatically at install time\.  This is the only officially supported
+method for compiling binary addons, and does not require that you add
+anything to your package\.json file\.
+.
+.P
+If you have to do other things before your package is used, in a way
+that is not dependent on the operating system or architecture of the
+target system, then use a \fBprepublish\fR script instead\.  This includes
+tasks such as:
+.
+.IP "\(bu" 4
+Compile CoffeeScript source code into JavaScript\.
+.
+.IP "\(bu" 4
+Create minified versions of JavaScript source code\.
+.
+.IP "\(bu" 4
+Fetching remote resources that your package will use\.
+.
+.IP "" 0
+.
+.P
+The advantage of doing these things at \fBprepublish\fR time instead of \fBpreinstall\fR or \fBinstall\fR time is that they can be done once, in a
+single place, and thus greatly reduce complexity and variability\.
+Additionally, this means that:
+.
+.IP "\(bu" 4
+You can depend on \fBcoffee\-script\fR as a \fBdevDependency\fR, and thus
+your users don\'t need to have it installed\.
+.
+.IP "\(bu" 4
+You don\'t need to include the minifiers in your package, reducing
+the size for your users\.
+.
+.IP "\(bu" 4
+You don\'t need to rely on your users having \fBcurl\fR or \fBwget\fR or
+other system tools on the target machines\.
+.
+.IP "" 0
+.
+.SH "DEFAULT VALUES"
+npm will default some script values based on package contents\.
+.
+.IP "\(bu" 4
+\fB"start": "node server\.js"\fR:
+.
+.IP
+If there is a \fBserver\.js\fR file in the root of your package, then npm
+will default the \fBstart\fR command to \fBnode server\.js\fR\|\.
+.
+.IP "\(bu" 4
+\fB"preinstall": "node\-waf clean || true; node\-waf configure build"\fR:
+.
+.IP
+If there is a \fBwscript\fR file in the root of your package, npm will
+default the \fBpreinstall\fR command to compile using node\-waf\.
+.
+.IP "" 0
+.
+.SH "USER"
+If npm was invoked with root privileges, then it will change the uid
+to the user account or uid specified by the \fBuser\fR config, which
+defaults to \fBnobody\fR\|\.  Set the \fBunsafe\-perm\fR flag to run scripts with
+root privileges\.
+.
+.SH "ENVIRONMENT"
+Package scripts run in an environment where many pieces of information
+are made available regarding the setup of npm and the current state of
+the process\.
+.
+.SS "path"
+If you depend on modules that define executable scripts, like test
+suites, then those executables will be added to the \fBPATH\fR for
+executing the scripts\.  So, if your package\.json has this:
+.
+.IP "" 4
+.
+.nf
+{ "name" : "foo"
+, "dependencies" : { "bar" : "0\.1\.x" }
+, "scripts": { "start" : "bar \./test" } }
+.
+.fi
+.
+.IP "" 0
+.
+.P
+then you could run \fBnpm start\fR to execute the \fBbar\fR script, which is
+exported into the \fBnode_modules/\.bin\fR directory on \fBnpm install\fR\|\.
+.
+.SS "package\.json vars"
+The package\.json fields are tacked onto the \fBnpm_package_\fR prefix\. So,
+for instance, if you had \fB{"name":"foo", "version":"1\.2\.5"}\fR in your
+package\.json file, then your package scripts would have the \fBnpm_package_name\fR environment variable set to "foo", and the \fBnpm_package_version\fR set to "1\.2\.5"
+.
+.SS "configuration"
+Configuration parameters are put in the environment with the \fBnpm_config_\fR prefix\. For instance, you can view the effective \fBroot\fR
+config by checking the \fBnpm_config_root\fR environment variable\.
+.
+.SS "Special: package\.json &quot;config&quot; hash"
+The package\.json "config" keys are overwritten in the environment if
+there is a config param of \fB<name>[@<version>]:<key>\fR\|\.  For example,
+if the package\.json has this:
+.
+.IP "" 4
+.
+.nf
+{ "name" : "foo"
+, "config" : { "port" : "8080" }
+, "scripts" : { "start" : "node server\.js" } }
+.
+.fi
+.
+.IP "" 0
+.
+.P
+and the server\.js is this:
+.
+.IP "" 4
+.
+.nf
+http\.createServer(\.\.\.)\.listen(process\.env\.npm_package_config_port)
+.
+.fi
+.
+.IP "" 0
+.
+.P
+then the user could change the behavior by doing:
+.
+.IP "" 4
+.
+.nf
+npm config set foo:port 80
+.
+.fi
+.
+.IP "" 0
+.
+.SS "current lifecycle event"
+Lastly, the \fBnpm_lifecycle_event\fR environment variable is set to
+whichever stage of the cycle is being executed\. So, you could have a
+single script used for different parts of the process which switches
+based on what\'s currently happening\.
+.
+.P
+Objects are flattened following this format, so if you had \fB{"scripts":{"install":"foo\.js"}}\fR in your package\.json, then you\'d
+see this in the script:
+.
+.IP "" 4
+.
+.nf
+process\.env\.npm_package_scripts_install === "foo\.js"
+.
+.fi
+.
+.IP "" 0
+.
+.SH "EXAMPLES"
+For example, if your package\.json contains this:
+.
+.IP "" 4
+.
+.nf
+{ "scripts" :
+  { "install" : "scripts/install\.js"
+  , "postinstall" : "scripts/install\.js"
+  , "uninstall" : "scripts/uninstall\.js"
+  }
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+then the \fBscripts/install\.js\fR will be called for the install,
+post\-install, stages of the lifecycle, and the \fBscripts/uninstall\.js\fR
+would be called when the package is uninstalled\.  Since \fBscripts/install\.js\fR is running for three different phases, it would
+be wise in this case to look at the \fBnpm_lifecycle_event\fR environment
+variable\.
+.
+.P
+If you want to run a make command, you can do so\.  This works just
+fine:
+.
+.IP "" 4
+.
+.nf
+{ "scripts" :
+  { "preinstall" : "\./configure"
+  , "install" : "make && make install"
+  , "test" : "make test"
+  }
+}
+.
+.fi
+.
+.IP "" 0
+.
+.SH "EXITING"
+Scripts are run by passing the line as a script argument to \fBsh\fR\|\.
+.
+.P
+If the script exits with a code other than 0, then this will abort the
+process\.
+.
+.P
+Note that these script files don\'t have to be nodejs or even
+javascript programs\. They just have to be some kind of executable
+file\.
+.
+.SH "HOOK SCRIPTS"
+If you want to run a specific script at a specific lifecycle event for
+ALL packages, then you can use a hook script\.
+.
+.P
+Place an executable file at \fBnode_modules/\.hooks/{eventname}\fR, and
+it\'ll get run for all packages when they are going through that point
+in the package lifecycle for any packages installed in that root\.
+.
+.P
+Hook scripts are run exactly the same way as package\.json scripts\.
+That is, they are in a separate child process, with the env described
+above\.
+.
+.SH "BEST PRACTICES"
+.
+.IP "\(bu" 4
+Don\'t exit with a non\-zero error code unless you \fIreally\fR mean it\.
+Except for uninstall scripts, this will cause the npm action to
+fail, and potentially be rolled back\.  If the failure is minor or
+only will prevent some optional features, then it\'s better to just
+print a warning and exit successfully\.
+.
+.IP "\(bu" 4
+npm help  Try not to use scripts to do what npm can do for you\.  Read through \fBpackage\.json\fR to see all the things that you can specify and enable
+by simply describing your package appropriately\.  In general, this
+will lead to a more robust and consistent state\.
+.
+.IP "\(bu" 4
+Inspect the env to determine where to put things\.  For instance, if
+the \fBnpm_config_binroot\fR environ is set to \fB/home/user/bin\fR, then
+don\'t try to install executables into \fB/usr/local/bin\fR\|\.  The user
+probably set it up that way for a reason\.
+.
+.IP "\(bu" 4
+Don\'t prefix your script commands with "sudo"\.  If root permissions
+are required for some reason, then it\'ll fail with that error, and
+the user will sudo the npm command in question\.
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+npm help run\-script
+.
+.IP "\(bu" 4
+npm help  package\.json
+.
+.IP "\(bu" 4
+npm help  developers
+.
+.IP "\(bu" 4
+npm help install
+.
+.IP "" 0
+