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

embeditor-rails 2.0.0.beta → 2.0.0

Files changed (1024) hide show

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

@@ -1,71 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-search</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-search.html">npm-search</a></h1> <p>Search for packages</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm search [--long] [search terms ...]
-npm s [search terms ...]
-npm se [search terms ...]</code></pre>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>Search the registry for packages matching the search terms.</p>
-<p>If a term starts with <code>/</code>, then it&#39;s interpreted as a regular expression.
-A trailing <code>/</code> will be ignored in this case.  (Note that many regular
-expression characters must be escaped or quoted in most shells.)</p>
-<h2 id="CONFIGURATION">CONFIGURATION</h2>
-<h3 id="long">long</h3>
-<ul><li>Default: false</li><li>Type: Boolean</li></ul>
-<p>Display full package descriptions and other long text across multiple
-lines. When disabled (default) search results are truncated to fit
-neatly on a single line. Modules with extremely long names will
-fall on multiple lines.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><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-view.html">npm-view(1)</a></li></ul>
-</div>
-<p id="footer">npm-search &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-shrinkwrap.html DELETED

@@ -1,217 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-shrinkwrap</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-shrinkwrap.html">npm-shrinkwrap</a></h1> <p>Lock down dependency versions</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm shrinkwrap</code></pre>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>This command locks down the versions of a package&#39;s dependencies so
-that you can control exactly which versions of each dependency will be
-used when your package is installed. The &quot;package.json&quot; file is still
-required if you want to use &quot;npm install&quot;.</p>
-<p>By default, &quot;npm install&quot; recursively installs the target&#39;s
-dependencies (as specified in package.json), choosing the latest
-available version that satisfies the dependency&#39;s semver pattern. In
-some situations, particularly when shipping software where each change
-is tightly managed, it&#39;s desirable to fully specify each version of
-each dependency recursively so that subsequent builds and deploys do
-not inadvertently pick up newer versions of a dependency that satisfy
-the semver pattern. Specifying specific semver patterns in each
-dependency&#39;s package.json would facilitate this, but that&#39;s not always
-possible or desirable, as when another author owns the npm package.
-It&#39;s also possible to check dependencies directly into source control,
-but that may be undesirable for other reasons.</p>
-<p>As an example, consider package A:</p>
-<pre><code>{
-  &quot;name&quot;: &quot;A&quot;,
-  &quot;version&quot;: &quot;0.1.0&quot;,
-  &quot;dependencies&quot;: {
-    &quot;B&quot;: &quot;&lt;0.1.0&quot;
-  }
-}</code></pre>
-<p>package B:</p>
-<pre><code>{
-  &quot;name&quot;: &quot;B&quot;,
-  &quot;version&quot;: &quot;0.0.1&quot;,
-  &quot;dependencies&quot;: {
-    &quot;C&quot;: &quot;&lt;0.1.0&quot;
-  }
-}</code></pre>
-<p>and package C:</p>
-<pre><code>{
-  &quot;name&quot;: &quot;C,
-  &quot;version&quot;: &quot;0.0.1&quot;
-}</code></pre>
-<p>If these are the only versions of A, B, and C available in the
-registry, then a normal &quot;npm install A&quot; will install:</p>
-<pre><code>A@0.1.0
-`-- B@0.0.1
-    `-- C@0.0.1</code></pre>
-<p>However, if B@0.0.2 is published, then a fresh &quot;npm install A&quot; will
-install:</p>
-<pre><code>A@0.1.0
-`-- B@0.0.2
-    `-- C@0.0.1</code></pre>
-<p>assuming the new version did not modify B&#39;s dependencies. Of course,
-the new version of B could include a new version of C and any number
-of new dependencies. If such changes are undesirable, the author of A
-could specify a dependency on B@0.0.1. However, if A&#39;s author and B&#39;s
-author are not the same person, there&#39;s no way for A&#39;s author to say
-that he or she does not want to pull in newly published versions of C
-when B hasn&#39;t changed at all.</p>
-<p>In this case, A&#39;s author can run</p>
-<pre><code>npm shrinkwrap</code></pre>
-<p>This generates npm-shrinkwrap.json, which will look something like this:</p>
-<pre><code>{
-  &quot;name&quot;: &quot;A&quot;,
-  &quot;version&quot;: &quot;0.1.0&quot;,
-  &quot;dependencies&quot;: {
-    &quot;B&quot;: {
-      &quot;version&quot;: &quot;0.0.1&quot;,
-      &quot;dependencies&quot;: {
-        &quot;C&quot;: {
-          &quot;version&quot;: &quot;0.1.0&quot;
-        }
-      }
-    }
-  }
-}</code></pre>
-<p>The shrinkwrap command has locked down the dependencies based on
-what&#39;s currently installed in node_modules.  When &quot;npm install&quot;
-installs a package with a npm-shrinkwrap.json file in the package
-root, the shrinkwrap file (rather than package.json files) completely
-drives the installation of that package and all of its dependencies
-(recursively).  So now the author publishes A@0.1.0, and subsequent
-installs of this package will use B@0.0.1 and C@0.1.0, regardless the
-dependencies and versions listed in A&#39;s, B&#39;s, and C&#39;s package.json
-files.</p>
-<h3 id="Using-shrinkwrapped-packages">Using shrinkwrapped packages</h3>
-<p>Using a shrinkwrapped package is no different than using any other
-package: you can &quot;npm install&quot; it by hand, or add a dependency to your
-package.json file and &quot;npm install&quot; it.</p>
-<h3 id="Building-shrinkwrapped-packages">Building shrinkwrapped packages</h3>
-<p>To shrinkwrap an existing package:</p>
-<ol><li>Run &quot;npm install&quot; in the package root to install the current
-versions of all dependencies.</li><li>Validate that the package works as expected with these versions.</li><li>Run &quot;npm shrinkwrap&quot;, add npm-shrinkwrap.json to git, and publish
-your package.</li></ol>
-<p>To add or update a dependency in a shrinkwrapped package:</p>
-<ol><li>Run &quot;npm install&quot; in the package root to install the current
-versions of all dependencies.</li><li>Add or update dependencies. &quot;npm install&quot; each new or updated
-package individually and then update package.json.  Note that they
-must be explicitly named in order to be installed: running <code>npm
-install</code> with no arguments will merely reproduce the existing
-shrinkwrap.</li><li>Validate that the package works as expected with the new
-dependencies.</li><li>Run &quot;npm shrinkwrap&quot;, commit the new npm-shrinkwrap.json, and
-publish your package.</li></ol>
-<p>You can use <a href="../cli/npm-outdated.html">npm-outdated(1)</a> to view dependencies with newer versions
-available.</p>
-<h3 id="Other-Notes">Other Notes</h3>
-<p>A shrinkwrap file must be consistent with the package&#39;s package.json
-file. &quot;npm shrinkwrap&quot; will fail if required dependencies are not
-already installed, since that would result in a shrinkwrap that
-wouldn&#39;t actually work. Similarly, the command will fail if there are
-extraneous packages (not referenced by package.json), since that would
-indicate that package.json is not correct.</p>
-<p>Since &quot;npm shrinkwrap&quot; is intended to lock down your dependencies for
-production use, <code>devDependencies</code> will not be included unless you
-explicitly set the <code>--dev</code> flag when you run <code>npm shrinkwrap</code>.  If
-installed <code>devDependencies</code> are excluded, then npm will print a
-warning.  If you want them to be installed with your module by
-default, please consider adding them to <code>dependencies</code> instead.</p>
-<p>If shrinkwrapped package A depends on shrinkwrapped package B, B&#39;s
-shrinkwrap will not be used as part of the installation of A. However,
-because A&#39;s shrinkwrap is constructed from a valid installation of B
-and recursively specifies all dependencies, the contents of B&#39;s
-shrinkwrap will implicitly be included in A&#39;s shrinkwrap.</p>
-<h3 id="Caveats">Caveats</h3>
-<p>Shrinkwrap files only lock down package versions, not actual package
-contents.  While discouraged, a package author can republish an
-existing version of a package, causing shrinkwrapped packages using
-that version to pick up different code than they were before. If you
-want to avoid any risk that a byzantine author replaces a package
-you&#39;re using with code that breaks your application, you could modify
-the shrinkwrap file to use git URL references rather than version
-numbers so that npm always fetches all packages from git.</p>
-<p>If you wish to lock down the specific bytes included in a package, for
-example to have 100% confidence in being able to reproduce a
-deployment or build, then you ought to check your dependencies into
-source control, or pursue some other mechanism that can verify
-contents rather than versions.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm-install.html">npm-install(1)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../cli/npm-ls.html">npm-ls(1)</a></li></ul>
-</div>
-<p id="footer">npm-shrinkwrap &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-star.html DELETED

@@ -1,60 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-star</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-star.html">npm-star</a></h1> <p>Mark your favorite packages</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm star &lt;pkgname&gt; [&lt;pkg&gt;, ...]
-npm unstar &lt;pkgname&gt; [&lt;pkg&gt;, ...]</code></pre>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>&quot;Starring&quot; a package means that you have some interest in it.  It&#39;s
-a vaguely positive way to show that you care.</p>
-<p>&quot;Unstarring&quot; is the same thing, but in reverse.</p>
-<p>It&#39;s a boolean thing.  Starring repeatedly has no additional effect.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm-view.html">npm-view(1)</a></li><li><a href="../cli/npm-whoami.html">npm-whoami(1)</a></li><li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li></ul>
-</div>
-<p id="footer">npm-star &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-stars.html DELETED

@@ -1,59 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-stars</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-stars.html">npm-stars</a></h1> <p>View packages marked as favorites</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm stars
-npm stars [username]</code></pre>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>If you have starred a lot of neat things and want to find them again
-quickly this command lets you do just that.</p>
-<p>You may also want to see your friend&#39;s favorite packages, in this case
-you will most certainly enjoy this command.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm-star.html">npm-star(1)</a></li><li><a href="../cli/npm-view.html">npm-view(1)</a></li><li><a href="../cli/npm-whoami.html">npm-whoami(1)</a></li><li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li></ul>
-</div>
-<p id="footer">npm-stars &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-start.html DELETED

@@ -1,54 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-start</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-start.html">npm-start</a></h1> <p>Start a package</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<pre><code>npm start &lt;name&gt;</code></pre>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>This runs a package&#39;s &quot;start&quot; script, if one was provided.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm-run-script.html">npm-run-script(1)</a></li><li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li><li><a href="../cli/npm-test.html">npm-test(1)</a></li><li><a href="../cli/npm-restart.html">npm-restart(1)</a></li><li><a href="../cli/npm-stop.html">npm-stop(1)</a></li></ul>
-</div>
-<p id="footer">npm-start &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>