RubyGems - embeditor-rails - Versions diffs - 2.0.0.beta → 2.0.0 - Mend

embeditor-rails 2.0.0.beta → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1024) hide show

data/lib/node_modules/npm/html/doc/cli/npm-view.html DELETED

@@ -1,125 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-view</title>
-  <meta http-equiv="content-type" value="text/html;utf-8">
-  <link rel="stylesheet" type="text/css" href="../../static/style.css">
-  <body>
-    <div id="wrapper">
-<h1><a href="../cli/npm-view.html">npm-view</a></h1> <p>View registry info</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm view &lt;name&gt;[@&lt;version&gt;] [&lt;field&gt;[.&lt;subfield&gt;]...]
-npm v &lt;name&gt;[@&lt;version&gt;] [&lt;field&gt;[.&lt;subfield&gt;]...]</code></pre>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>This command shows data about a package and prints it to the stream
-referenced by the <code>outfd</code> config, which defaults to stdout.</p>
-<p>To show the package registry entry for the <code>connect</code> package, you can do
-this:</p>
-<pre><code>npm view connect</code></pre>
-<p>The default version is &quot;latest&quot; if unspecified.</p>
-<p>Field names can be specified after the package descriptor.
-For example, to show the dependencies of the <code>ronn</code> package at version
-0.3.5, you could do the following:</p>
-<pre><code>npm view ronn@0.3.5 dependencies</code></pre>
-<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:</p>
-<pre><code>npm view npm repository.url</code></pre>
-<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:</p>
-<pre><code>npm view opts@$(npm view ronn dependencies.opts)</code></pre>
-<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 &quot;express&quot; project, you can do this:</p>
-<pre><code>npm view express contributors.email</code></pre>
-<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:</p>
-<pre><code>npm view express contributors[0].email</code></pre>
-<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:</p>
-<pre><code>npm view express contributors.name contributors.email</code></pre>
-<p>&quot;Person&quot; 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 <code><a href="../files/package.json.html">package.json(5)</a></code> for more on this.)</p>
-<pre><code>npm view npm contributors</code></pre>
-<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:</p>
-<pre><code>npm view yui3@&#39;&gt;0.5.4&#39; dependencies.jsdom</code></pre>
-<h2 id="OUTPUT">OUTPUT</h2>
-<p>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>
-<p>If the --json flag is given, the outputted fields will be JSON.</p>
-<p>If the version range matches multiple versions, than each printed value
-will be prefixed with the version it applies to.</p>
-<p>If multiple fields are requested, than each of them are prefixed with
-the field name.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm-search.html">npm-search(1)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../cli/npm-docs.html">npm-docs(1)</a></li></ul>
-</div>
-<p id="footer">npm-view &mdash; npm@1.4.3</p>
-<script>
-;(function () {
-var wrapper = document.getElementById("wrapper")
-var els = Array.prototype.slice.call(wrapper.getElementsByTagName("*"), 0)
-  .filter(function (el) {
-    return el.parentNode === wrapper
-        && el.tagName.match(/H[1-6]/)
-        && el.id
-  })
-var l = 2
-  , toc = document.createElement("ul")
-toc.innerHTML = els.map(function (el) {
-  var i = el.tagName.charAt(1)
-    , out = ""
-  while (i > l) {
-    out += "<ul>"
-    l ++
-  }
-  while (i < l) {
-    out += "</ul>"
-    l --
-  }
-  out += "<li><a href='#" + el.id + "'>" +
-    ( el.innerText || el.text || el.innerHTML)
-    + "</a>"
-  return out
-}).join("\n")
-toc.id = "toc"
-document.body.appendChild(toc)
-})()
-</script>

data/lib/node_modules/npm/html/doc/cli/npm-whoami.html DELETED

@@ -1,54 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-whoami</title>
-  <meta http-equiv="content-type" value="text/html;utf-8">
-  <link rel="stylesheet" type="text/css" href="../../static/style.css">
-  <body>
-    <div id="wrapper">
-<h1><a href="../cli/npm-whoami.html">npm-whoami</a></h1> <p>Display npm username</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm whoami</code></pre>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>Print the <code>username</code> config to standard output.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li></ul>
-</div>
-<p id="footer">npm-whoami &mdash; npm@1.4.3</p>
-<script>
-;(function () {
-var wrapper = document.getElementById("wrapper")
-var els = Array.prototype.slice.call(wrapper.getElementsByTagName("*"), 0)
-  .filter(function (el) {
-    return el.parentNode === wrapper
-        && el.tagName.match(/H[1-6]/)
-        && el.id
-  })
-var l = 2
-  , toc = document.createElement("ul")
-toc.innerHTML = els.map(function (el) {
-  var i = el.tagName.charAt(1)
-    , out = ""
-  while (i > l) {
-    out += "<ul>"
-    l ++
-  }
-  while (i < l) {
-    out += "</ul>"
-    l --
-  }
-  out += "<li><a href='#" + el.id + "'>" +
-    ( el.innerText || el.text || el.innerHTML)
-    + "</a>"
-  return out
-}).join("\n")
-toc.id = "toc"
-document.body.appendChild(toc)
-})()
-</script>

data/lib/node_modules/npm/html/doc/cli/npm.html DELETED

@@ -1,165 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm</title>
-  <meta http-equiv="content-type" value="text/html;utf-8">
-  <link rel="stylesheet" type="text/css" href="../../static/style.css">
-  <body>
-    <div id="wrapper">
-<h1><a href="../cli/npm.html">npm</a></h1> <p>node package manager</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm &lt;command&gt; [args]</code></pre>
-<h2 id="VERSION">VERSION</h2>
-<p>1.4.3</p>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>npm is the package manager for the Node JavaScript platform.  It puts
-modules in place so that node can find them, and manages dependency
-conflicts intelligently.</p>
-<p>It is extremely configurable to support a wide variety of use cases.
-Most commonly, it is used to publish, discover, install, and develop node
-programs.</p>
-<p>Run <code>npm help</code> to get a list of available commands.</p>
-<h2 id="INTRODUCTION">INTRODUCTION</h2>
-<p>You probably got npm because you want to install stuff.</p>
-<p>Use <code>npm install blerg</code> to install the latest version of &quot;blerg&quot;.  Check out
-<code><a href="../cli/npm-install.html">npm-install(1)</a></code> for more info.  It can do a lot of stuff.</p>
-<p>Use the <code>npm search</code> command to show everything that&#39;s available.
-Use <code>npm ls</code> to show everything you&#39;ve installed.</p>
-<h2 id="DIRECTORIES">DIRECTORIES</h2>
-<p>See <code><a href="../files/npm-folders.html">npm-folders(5)</a></code> to learn about where npm puts stuff.</p>
-<p>In particular, npm has two modes of operation:</p>
-<ul><li>global mode:<br />npm installs packages into the install prefix at
-<code>prefix/lib/node_modules</code> and bins are installed in <code>prefix/bin</code>.</li><li>local mode:<br />npm installs packages into the current project directory, which
-defaults to the current working directory.  Packages are installed to
-<code>./node_modules</code>, and bins are installed to <code>./node_modules/.bin</code>.</li></ul>
-<p>Local mode is the default.  Use <code>--global</code> or <code>-g</code> on any command to
-operate in global mode instead.</p>
-<h2 id="DEVELOPER-USAGE">DEVELOPER USAGE</h2>
-<p>If you&#39;re using npm to develop and publish your code, check out the
-following help topics:</p>
-<ul><li>json:
-Make a package.json file.  See <code><a href="../files/package.json.html">package.json(5)</a></code>.</li><li>link:
-For linking your current working code into Node&#39;s path, so that you
-don&#39;t have to reinstall every time you make a change.  Use
-<code>npm link</code> to do this.</li><li>install:
-It&#39;s a good idea to install things if you don&#39;t need the symbolic link.
-Especially, installing other peoples code from the registry is done via
-<code>npm install</code></li><li>adduser:
-Create an account or log in.  Credentials are stored in the
-user config file.</li><li>publish:
-Use the <code>npm publish</code> command to upload your code to the registry.</li></ul>
-<h2 id="CONFIGURATION">CONFIGURATION</h2>
-<p>npm is extremely configurable.  It reads its configuration options from
-5 places.</p>
-<ul><li>Command line switches:<br />Set a config with <code>--key val</code>.  All keys take a value, even if they
-are booleans (the config parser doesn&#39;t know what the options are at
-the time of parsing.)  If no value is provided, then the option is set
-to boolean <code>true</code>.</li><li>Environment Variables:<br />Set any config by prefixing the name in an environment variable with
-<code>npm_config_</code>.  For example, <code>export npm_config_key=val</code>.</li><li>User Configs:<br />The file at $HOME/.npmrc is an ini-formatted list of configs.  If
-present, it is parsed.  If the <code>userconfig</code> option is set in the cli
-or env, then that will be used instead.</li><li>Global Configs:<br />The file found at ../etc/npmrc (from the node executable, by default
-this resolves to /usr/local/etc/npmrc) will be parsed if it is found.
-If the <code>globalconfig</code> option is set in the cli, env, or user config,
-then that file is parsed instead.</li><li>Defaults:<br />npm&#39;s default configuration options are defined in
-lib/utils/config-defs.js.  These must not be changed.</li></ul>
-<p>See <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for much much more information.</p>
-<h2 id="CONTRIBUTIONS">CONTRIBUTIONS</h2>
-<p>Patches welcome!</p>
-<ul><li>code:
-Read through <code><a href="../misc/npm-coding-style.html">npm-coding-style(7)</a></code> if you plan to submit code.
-You don&#39;t have to agree with it, but you do have to follow it.</li><li>docs:
-If you find an error in the documentation, edit the appropriate markdown
-file in the &quot;doc&quot; folder.  (Don&#39;t worry about generating the man page.)</li></ul>
-<p>Contributors are listed in npm&#39;s <code>package.json</code> file.  You can view them
-easily by doing <code>npm view npm contributors</code>.</p>
-<p>If you would like to contribute, but don&#39;t know what to work on, check
-the issues list or ask on the mailing list.</p>
-<ul><li><a href="http://github.com/npm/npm/issues">http://github.com/npm/npm/issues</a></li><li><a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li></ul>
-<h2 id="BUGS">BUGS</h2>
-<p>When you find issues, please report them:</p>
-<ul><li>web:
-<a href="http://github.com/npm/npm/issues">http://github.com/npm/npm/issues</a></li><li>email:
-<a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li></ul>
-<p>Be sure to include <em>all</em> of the output from the npm command that didn&#39;t work
-as expected.  The <code>npm-debug.log</code> file is also helpful to provide.</p>
-<p>You can also look for isaacs in #node.js on irc://irc.freenode.net.  He
-will no doubt tell you to put the output in a gist or email.</p>
-<h2 id="AUTHOR">AUTHOR</h2>
-<p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> ::
-<a href="https://github.com/isaacs/">isaacs</a> ::
-<a href="http://twitter.com/izs">@izs</a> ::
-<a href="mailto:i@izs.me">i@izs.me</a></p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm-help.html">npm-help(1)</a></li><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../../doc/README.html">README</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../misc/npm-index.html">npm-index(7)</a></li><li><a href="../api/npm.html">npm(3)</a></li></ul>
-</div>
-<p id="footer">npm &mdash; npm@1.4.3</p>
-<script>
-;(function () {
-var wrapper = document.getElementById("wrapper")
-var els = Array.prototype.slice.call(wrapper.getElementsByTagName("*"), 0)
-  .filter(function (el) {
-    return el.parentNode === wrapper
-        && el.tagName.match(/H[1-6]/)
-        && el.id
-  })
-var l = 2
-  , toc = document.createElement("ul")
-toc.innerHTML = els.map(function (el) {
-  var i = el.tagName.charAt(1)
-    , out = ""
-  while (i > l) {
-    out += "<ul>"
-    l ++
-  }
-  while (i < l) {
-    out += "</ul>"
-    l --
-  }
-  out += "<li><a href='#" + el.id + "'>" +
-    ( el.innerText || el.text || el.innerHTML)
-    + "</a>"
-  return out
-}).join("\n")
-toc.id = "toc"
-document.body.appendChild(toc)
-})()
-</script>

data/lib/node_modules/npm/html/doc/files/npm-folders.html DELETED

@@ -1,239 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-folders</title>
-  <meta http-equiv="content-type" value="text/html;utf-8">
-  <link rel="stylesheet" type="text/css" href="../../static/style.css">
-  <body>
-    <div id="wrapper">
-<h1><a href="../files/npm-folders.html">npm-folders</a></h1> <p>Folder Structures Used by npm</p>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>npm puts various things on your computer.  That&#39;s its job.</p>
-<p>This document will tell you what it puts where.</p>
-<h3 id="tl-dr">tl;dr</h3>
-<ul><li>Local install (default): puts stuff in <code>./node_modules</code> of the current
-package root.</li><li>Global install (with <code>-g</code>): puts stuff in /usr/local or wherever node
-is installed.</li><li>Install it <strong>locally</strong> if you&#39;re going to <code>require()</code> it.</li><li>Install it <strong>globally</strong> if you&#39;re going to run it on the command line.</li><li>If you need both, then install it in both places, or use <code>npm link</code>.</li></ul>
-<h3 id="prefix-Configuration">prefix Configuration</h3>
-<p>The <code>prefix</code> config defaults to the location where node is installed.
-On most systems, this is <code>/usr/local</code>, and most of the time is the same
-as node&#39;s <code>process.installPrefix</code>.</p>
-<p>On windows, this is the exact location of the node.exe binary.  On Unix
-systems, it&#39;s one level up, since node is typically installed at
-<code>{prefix}/bin/node</code> rather than <code>{prefix}/node.exe</code>.</p>
-<p>When the <code>global</code> flag is set, npm installs things into this prefix.
-When it is not set, it uses the root of the current package, or the
-current working directory if not in a package already.</p>
-<h3 id="Node-Modules">Node Modules</h3>
-<p>Packages are dropped into the <code>node_modules</code> folder under the <code>prefix</code>.
-When installing locally, this means that you can
-<code>require(&quot;packagename&quot;)</code> to load its main module, or
-<code>require(&quot;packagename/lib/path/to/sub/module&quot;)</code> to load other modules.</p>
-<p>Global installs on Unix systems go to <code>{prefix}/lib/node_modules</code>.
-Global installs on Windows go to <code>{prefix}/node_modules</code> (that is, no
-<code>lib</code> folder.)</p>
-<p>If you wish to <code>require()</code> a package, then install it locally.</p>
-<h3 id="Executables">Executables</h3>
-<p>When in global mode, executables are linked into <code>{prefix}/bin</code> on Unix,
-or directly into <code>{prefix}</code> on Windows.</p>
-<p>When in local mode, executables are linked into
-<code>./node_modules/.bin</code> so that they can be made available to scripts run
-through npm.  (For example, so that a test runner will be in the path
-when you run <code>npm test</code>.)</p>
-<h3 id="Man-Pages">Man Pages</h3>
-<p>When in global mode, man pages are linked into <code>{prefix}/share/man</code>.</p>
-<p>When in local mode, man pages are not installed.</p>
-<p>Man pages are not installed on Windows systems.</p>
-<h3 id="Cache">Cache</h3>
-<p>See <code><a href="../cli/npm-cache.html">npm-cache(1)</a></code>.  Cache files are stored in <code>~/.npm</code> on Posix, or
-<code>~/npm-cache</code> on Windows.</p>
-<p>This is controlled by the <code>cache</code> configuration param.</p>
-<h3 id="Temp-Files">Temp Files</h3>
-<p>Temporary files are stored by default in the folder specified by the
-<code>tmp</code> config, which defaults to the TMPDIR, TMP, or TEMP environment
-variables, or <code>/tmp</code> on Unix and <code>c:\windows\temp</code> on Windows.</p>
-<p>Temp files are given a unique folder under this root for each run of the
-program, and are deleted upon successful exit.</p>
-<h2 id="More-Information">More Information</h2>
-<p>When installing locally, npm first tries to find an appropriate
-<code>prefix</code> folder.  This is so that <code>npm install foo@1.2.3</code> will install
-to the sensible root of your package, even if you happen to have <code>cd</code>ed
-into some other folder.</p>
-<p>Starting at the $PWD, npm will walk up the folder tree checking for a
-folder that contains either a <code>package.json</code> file, or a <code>node_modules</code>
-folder.  If such a thing is found, then that is treated as the effective
-&quot;current directory&quot; for the purpose of running npm commands.  (This
-behavior is inspired by and similar to git&#39;s .git-folder seeking
-logic when running git commands in a working dir.)</p>
-<p>If no package root is found, then the current folder is used.</p>
-<p>When you run <code>npm install foo@1.2.3</code>, then the package is loaded into
-the cache, and then unpacked into <code>./node_modules/foo</code>.  Then, any of
-foo&#39;s dependencies are similarly unpacked into
-<code>./node_modules/foo/node_modules/...</code>.</p>
-<p>Any bin files are symlinked to <code>./node_modules/.bin/</code>, so that they may
-be found by npm scripts when necessary.</p>
-<h3 id="Global-Installation">Global Installation</h3>
-<p>If the <code>global</code> configuration is set to true, then npm will
-install packages &quot;globally&quot;.</p>
-<p>For global installation, packages are installed roughly the same way,
-but using the folders described above.</p>
-<h3 id="Cycles-Conflicts-and-Folder-Parsimony">Cycles, Conflicts, and Folder Parsimony</h3>
-<p>Cycles are handled using the property of node&#39;s module system that it
-walks up the directories looking for <code>node_modules</code> folders.  So, at every
-stage, if a package is already installed in an ancestor <code>node_modules</code>
-folder, then it is not installed at the current location.</p>
-<p>Consider the case above, where <code>foo -&gt; bar -&gt; baz</code>.  Imagine if, in
-addition to that, baz depended on bar, so you&#39;d have:
-<code>foo -&gt; bar -&gt; baz -&gt; bar -&gt; baz ...</code>.  However, since the folder
-structure is: <code>foo/node_modules/bar/node_modules/baz</code>, there&#39;s no need to
-put another copy of bar into <code>.../baz/node_modules</code>, since when it calls
-require(&quot;bar&quot;), it will get the copy that is installed in
-<code>foo/node_modules/bar</code>.</p>
-<p>This shortcut is only used if the exact same
-version would be installed in multiple nested <code>node_modules</code> folders.  It
-is still possible to have <code>a/node_modules/b/node_modules/a</code> if the two
-&quot;a&quot; packages are different versions.  However, without repeating the
-exact same package multiple times, an infinite regress will always be
-prevented.</p>
-<p>Another optimization can be made by installing dependencies at the
-highest level possible, below the localized &quot;target&quot; folder.</p>
-<h4 id="Example">Example</h4>
-<p>Consider this dependency graph:</p>
-<pre><code>foo
-+-- blerg@1.2.5
-+-- bar@1.2.3
-|   +-- blerg@1.x (latest=1.3.7)
-|   +-- baz@2.x
-|   |   `-- quux@3.x
-|   |       `-- bar@1.2.3 (cycle)
-|   `-- asdf@*
-`-- baz@1.2.3
-    `-- quux@3.x
-        `-- bar</code></pre>
-<p>In this case, we might expect a folder structure like this:</p>
-<pre><code>foo
-+-- node_modules
-    +-- blerg (1.2.5) &lt;---[A]
-    +-- bar (1.2.3) &lt;---[B]
-    |   `-- node_modules
-    |       +-- baz (2.0.2) &lt;---[C]
-    |       |   `-- node_modules
-    |       |       `-- quux (3.2.0)
-    |       `-- asdf (2.3.4)
-    `-- baz (1.2.3) &lt;---[D]
-        `-- node_modules
-            `-- quux (3.2.0) &lt;---[E]</code></pre>
-<p>Since foo depends directly on <code>bar@1.2.3</code> and <code>baz@1.2.3</code>, those are
-installed in foo&#39;s <code>node_modules</code> folder.</p>
-<p>Even though the latest copy of blerg is 1.3.7, foo has a specific
-dependency on version 1.2.5.  So, that gets installed at [A].  Since the
-parent installation of blerg satisfies bar&#39;s dependency on <code>blerg@1.x</code>,
-it does not install another copy under [B].</p>
-<p>Bar [B] also has dependencies on baz and asdf, so those are installed in
-bar&#39;s <code>node_modules</code> folder.  Because it depends on <code>baz@2.x</code>, it cannot
-re-use the <code>baz@1.2.3</code> installed in the parent <code>node_modules</code> folder [D],
-and must install its own copy [C].</p>
-<p>Underneath bar, the <code>baz -&gt; quux -&gt; bar</code> dependency creates a cycle.
-However, because bar is already in quux&#39;s ancestry [B], it does not
-unpack another copy of bar into that folder.</p>
-<p>Underneath <code>foo -&gt; baz</code> [D], quux&#39;s [E] folder tree is empty, because its
-dependency on bar is satisfied by the parent folder copy installed at [B].</p>
-<p>For a graphical breakdown of what is installed where, use <code>npm ls</code>.</p>
-<h3 id="Publishing">Publishing</h3>
-<p>Upon publishing, npm will look in the <code>node_modules</code> folder.  If any of
-the items there are not in the <code>bundledDependencies</code> array, then they will
-not be included in the package tarball.</p>
-<p>This allows a package maintainer to install all of their dependencies
-(and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere.  See <code><a href="../files/package.json.html">package.json(5)</a></code> for more information.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../cli/npm-pack.html">npm-pack(1)</a></li><li><a href="../cli/npm-cache.html">npm-cache(1)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li></ul>
-</div>
-<p id="footer">npm-folders &mdash; npm@1.4.3</p>
-<script>
-;(function () {
-var wrapper = document.getElementById("wrapper")
-var els = Array.prototype.slice.call(wrapper.getElementsByTagName("*"), 0)
-  .filter(function (el) {
-    return el.parentNode === wrapper
-        && el.tagName.match(/H[1-6]/)
-        && el.id
-  })
-var l = 2
-  , toc = document.createElement("ul")
-toc.innerHTML = els.map(function (el) {
-  var i = el.tagName.charAt(1)
-    , out = ""
-  while (i > l) {
-    out += "<ul>"
-    l ++
-  }
-  while (i < l) {
-    out += "</ul>"
-    l --
-  }
-  out += "<li><a href='#" + el.id + "'>" +
-    ( el.innerText || el.text || el.innerHTML)
-    + "</a>"
-  return out
-}).join("\n")
-toc.id = "toc"
-document.body.appendChild(toc)
-})()
-</script>