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/misc/npm-developers.html DELETED

@@ -1,208 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-developers</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="../misc/npm-developers.html">npm-developers</a></h1> <p>Developer Guide</p>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>So, you&#39;ve decided to use npm to develop (and maybe publish/deploy)
-your project.</p>
-<p>Fantastic!</p>
-<p>There are a few things that you need to do above the simple steps
-that your users will do to install your program.</p>
-<h2 id="About-These-Documents">About These Documents</h2>
-<p>These are man pages.  If you install npm, you should be able to
-then do <code>man npm-thing</code> to get the documentation on a particular
-topic, or <code>npm help thing</code> to see the same information.</p>
-<h2 id="What-is-a-package">What is a <code>package</code></h2>
-<p>A package is:</p>
-<ul><li>a) a folder containing a program described by a package.json file</li><li>b) a gzipped tarball containing (a)</li><li>c) a url that resolves to (b)</li><li>d) a <code>&lt;name&gt;@&lt;version&gt;</code> that is published on the registry with (c)</li><li>e) a <code>&lt;name&gt;@&lt;tag&gt;</code> that points to (d)</li><li>f) a <code>&lt;name&gt;</code> that has a &quot;latest&quot; tag satisfying (e)</li><li>g) a <code>git</code> url that, when cloned, results in (a).</li></ul>
-<p>Even if you never publish your package, you can still get a lot of
-benefits of using npm if you just want to write a node program (a), and
-perhaps if you also want to be able to easily install it elsewhere
-after packing it up into a tarball (b).</p>
-<p>Git urls can be of the form:</p>
-<pre><code>git://github.com/user/project.git#commit-ish
-git+ssh://user@hostname:project.git#commit-ish
-git+http://user@hostname/project/blah.git#commit-ish
-git+https://user@hostname/project/blah.git#commit-ish</code></pre>
-<p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as
-an argument to <code>git checkout</code>.  The default is <code>master</code>.</p>
-<h2 id="The-package-json-File">The package.json File</h2>
-<p>You need to have a <code>package.json</code> file in the root of your project to do
-much of anything with npm.  That is basically the whole interface.</p>
-<p>See <code><a href="../files/package.json.html">package.json(5)</a></code> for details about what goes in that file.  At the very
-least, you need:</p>
-<ul><li><p>name:
-This should be a string that identifies your project.  Please do not
-use the name to specify that it runs on node, or is in JavaScript.
-You can use the &quot;engines&quot; field to explicitly state the versions of
-node (or whatever else) that your program requires, and it&#39;s pretty
-well assumed that it&#39;s javascript.</p><p>It does not necessarily need to match your github repository name.</p><p>So, <code>node-foo</code> and <code>bar-js</code> are bad names.  <code>foo</code> or <code>bar</code> are better.</p></li><li><p>version:
-A semver-compatible version.</p></li><li><p>engines:
-Specify the versions of node (or whatever else) that your program
-runs on.  The node API changes a lot, and there may be bugs or new
-functionality that you depend on.  Be explicit.</p></li><li><p>author:
-Take some credit.</p></li><li><p>scripts:
-If you have a special compilation or installation script, then you
-should put it in the <code>scripts</code> hash.  You should definitely have at
-least a basic smoke-test command as the &quot;scripts.test&quot; field.
-See <a href="../misc/npm-scripts.html">npm-scripts(7)</a>.</p></li><li><p>main:
-If you have a single module that serves as the entry point to your
-program (like what the &quot;foo&quot; package gives you at require(&quot;foo&quot;)),
-then you need to specify that in the &quot;main&quot; field.</p></li><li><p>directories:
-This is a hash of folders.  The best ones to include are &quot;lib&quot; and
-&quot;doc&quot;, but if you specify a folder full of man pages in &quot;man&quot;, then
-they&#39;ll get installed just like these ones.</p></li></ul>
-<p>You can use <code>npm init</code> in the root of your package in order to get you
-started with a pretty basic package.json file.  See <code><a href="../cli/npm-init.html">npm-init(1)</a></code> for
-more info.</p>
-<h2 id="Keeping-files-out-of-your-package">Keeping files <em>out</em> of your package</h2>
-<p>Use a <code>.npmignore</code> file to keep stuff out of your package.  If there&#39;s
-no <code>.npmignore</code> file, but there <em>is</em> a <code>.gitignore</code> file, then npm will
-ignore the stuff matched by the <code>.gitignore</code> file.  If you <em>want</em> to
-include something that is excluded by your <code>.gitignore</code> file, you can
-create an empty <code>.npmignore</code> file to override it.</p>
-<p>By default, the following paths and files are ignored, so there&#39;s no
-need to add them to <code>.npmignore</code> explicitly:</p>
-<ul><li><code>.*.swp</code></li><li><code>._*</code></li><li><code>.DS_Store</code></li><li><code>.git</code></li><li><code>.hg</code></li><li><code>.lock-wscript</code></li><li><code>.svn</code></li><li><code>.wafpickle-*</code></li><li><code>CVS</code></li><li><code>npm-debug.log</code></li></ul>
-<p>Additionally, everything in <code>node_modules</code> is ignored, except for
-bundled dependencies. npm automatically handles this for you, so don&#39;t
-bother adding <code>node_modules</code> to <code>.npmignore</code>.</p>
-<p>The following paths and files are never ignored, so adding them to
-<code>.npmignore</code> is pointless:</p>
-<ul><li><code>package.json</code></li><li><code><a href="../../doc/README.html">README</a>.*</code></li></ul>
-<h2 id="Link-Packages">Link Packages</h2>
-<p><code>npm link</code> is designed to install a development package and see the
-changes in real time without having to keep re-installing it.  (You do
-need to either re-link or <code>npm rebuild -g</code> to update compiled packages,
-of course.)</p>
-<p>More info at <code><a href="../cli/npm-link.html">npm-link(1)</a></code>.</p>
-<h2 id="Before-Publishing-Make-Sure-Your-Package-Installs-and-Works">Before Publishing: Make Sure Your Package Installs and Works</h2>
-<p><strong>This is important.</strong></p>
-<p>If you can not install it locally, you&#39;ll have
-problems trying to publish it.  Or, worse yet, you&#39;ll be able to
-publish it, but you&#39;ll be publishing a broken or pointless package.
-So don&#39;t do that.</p>
-<p>In the root of your package, do this:</p>
-<pre><code>npm install . -g</code></pre>
-<p>That&#39;ll show you that it&#39;s working.  If you&#39;d rather just create a symlink
-package that points to your working directory, then do this:</p>
-<pre><code>npm link</code></pre>
-<p>Use <code>npm ls -g</code> to see if it&#39;s there.</p>
-<p>To test a local install, go into some other folder, and then do:</p>
-<pre><code>cd ../some-other-folder
-npm install ../my-package</code></pre>
-<p>to install it locally into the node_modules folder in that other place.</p>
-<p>Then go into the node-repl, and try using require(&quot;my-thing&quot;) to
-bring in your module&#39;s main module.</p>
-<h2 id="Create-a-User-Account">Create a User Account</h2>
-<p>Create a user with the adduser command.  It works like this:</p>
-<pre><code>npm adduser</code></pre>
-<p>and then follow the prompts.</p>
-<p>This is documented better in <a href="../cli/npm-adduser.html">npm-adduser(1)</a>.</p>
-<h2 id="Publish-your-package">Publish your package</h2>
-<p>This part&#39;s easy.  IN the root of your folder, do this:</p>
-<pre><code>npm publish</code></pre>
-<p>You can give publish a url to a tarball, or a filename of a tarball,
-or a path to a folder.</p>
-<p>Note that pretty much <strong>everything in that folder will be exposed</strong>
-by default.  So, if you have secret stuff in there, use a
-<code>.npmignore</code> file to list out the globs to ignore, or publish
-from a fresh checkout.</p>
-<h2 id="Brag-about-it">Brag about it</h2>
-<p>Send emails, write blogs, blab in IRC.</p>
-<p>Tell the world how easy it is to install your program!</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../misc/npm-faq.html">npm-faq(7)</a></li><li><a href="../cli/npm.html">npm(1)</a></li><li><a href="../cli/npm-init.html">npm-init(1)</a></li><li><a href="../files/package.json.html">package.json(5)</a></li><li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li><li><a href="../cli/npm-publish.html">npm-publish(1)</a></li><li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li><li><a href="../misc/npm-registry.html">npm-registry(7)</a></li></ul>
-</div>
-<p id="footer">npm-developers &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/misc/npm-disputes.html DELETED

@@ -1,126 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-disputes</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="../misc/npm-disputes.html">npm-disputes</a></h1> <p>Handling Module Name Disputes</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<ol><li>Get the author email with <code>npm owner ls &lt;pkgname&gt;</code></li><li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li><li>After a few weeks, if there&#39;s no resolution, we&#39;ll sort it out.</li></ol>
-<p>Don&#39;t squat on package names.  Publish code or move out of the way.</p>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p>There sometimes arise cases where a user publishes a module, and then
-later, some other user wants to use that name.  Here are some common
-ways that happens (each of these is based on actual events.)</p>
-<ol><li>Joe writes a JavaScript module <code>foo</code>, which is not node-specific.
-Joe doesn&#39;t use node at all.  Bob   wants to use <code>foo</code> in node, so he
-wraps it in an npm module.  Some time later, Joe starts using node,
-and wants to take over management of his program.</li><li>Bob writes an npm module <code>foo</code>, and publishes it.  Perhaps much
-later, Joe finds a bug in <code>foo</code>, and fixes it.  He sends a pull
-request to Bob, but Bob doesn&#39;t have the time to deal with it,
-because he has a new job and a new baby and is focused on his new
-erlang project, and kind of not involved with node any more.  Joe
-would like to publish a new <code>foo</code>, but can&#39;t, because the name is
-taken.</li><li>Bob writes a 10-line flow-control library, and calls it <code>foo</code>, and
-publishes it to the npm registry.  Being a simple little thing, it
-never really has to be updated.  Joe works for Foo Inc, the makers
-of the critically acclaimed and widely-marketed <code>foo</code> JavaScript
-toolkit framework.  They publish it to npm as <code>foojs</code>, but people are
-routinely confused when <code>npm install foo</code> is some different thing.</li><li>Bob writes a parser for the widely-known <code>foo</code> file format, because
-he needs it for work.  Then, he gets a new job, and never updates the
-prototype.  Later on, Joe writes a much more complete <code>foo</code> parser,
-but can&#39;t publish, because Bob&#39;s <code>foo</code> is in the way.</li></ol>
-<p>The validity of Joe&#39;s claim in each situation can be debated.  However,
-Joe&#39;s appropriate course of action in each case is the same.</p>
-<ol><li><code>npm owner ls foo</code>.  This will tell Joe the email address of the
-owner (Bob).</li><li>Joe emails Bob, explaining the situation <strong>as respectfully as
-possible</strong>, and what he would like to do with the module name.  He
-adds the npm support staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of
-the email.  Mention in the email that Bob can run <code>npm owner add
-joe foo</code> to add Joe as an owner of the <code>foo</code> package.</li><li>After a reasonable amount of time, if Bob has not responded, or if
-Bob and Joe can&#39;t come to any sort of resolution, email support
-<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we&#39;ll sort it out.  (&quot;Reasonable&quot; is
-usually at least 4 weeks, but extra time is allowed around common
-holidays.)</li></ol>
-<h2 id="REASONING">REASONING</h2>
-<p>In almost every case so far, the parties involved have been able to reach
-an amicable resolution without any major intervention.  Most people
-really do want to be reasonable, and are probably not even aware that
-they&#39;re in your way.</p>
-<p>Module ecosystems are most vibrant and powerful when they are as
-self-directed as possible.  If an admin one day deletes something you
-had worked on, then that is going to make most people quite upset,
-regardless of the justification.  When humans solve their problems by
-talking to other humans with respect, everyone has the chance to end up
-feeling good about the interaction.</p>
-<h2 id="EXCEPTIONS">EXCEPTIONS</h2>
-<p>Some things are not allowed, and will be removed without discussion if
-they are brought to the attention of the npm registry admins, including
-but not limited to:</p>
-<ol><li>Malware (that is, a package designed to exploit or harm the machine on
-which it is installed).</li><li>Violations of copyright or licenses (for example, cloning an
-MIT-licensed program, and then removing or changing the copyright and
-license statement).</li><li>Illegal content.</li><li>&quot;Squatting&quot; on a package name that you <em>plan</em> to use, but aren&#39;t
-actually using.  Sorry, I don&#39;t care how great the name is, or how
-perfect a fit it is for the thing that someday might happen.  If
-someone wants to use it today, and you&#39;re just taking up space with
-an empty tarball, you&#39;re going to be evicted.</li><li>Putting empty packages in the registry.  Packages must have SOME
-functionality.  It can be silly, but it can&#39;t be <em>nothing</em>.  (See
-also: squatting.)</li><li>Doing weird things with the registry, like using it as your own
-personal application database or otherwise putting non-packagey
-things into it.</li></ol>
-<p>If you see bad behavior like this, please report it right away.</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-owner.html">npm-owner(1)</a></li></ul>
-</div>
-<p id="footer">npm-disputes &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/misc/npm-faq.html DELETED

@@ -1,382 +0,0 @@
-<!doctype html>
-<html>
-  <title>npm-faq</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="../misc/npm-faq.html">npm-faq</a></h1> <p>Frequently Asked Questions</p>
-<h2 id="Where-can-I-find-these-docs-in-HTML">Where can I find these docs in HTML?</h2>
-<p><a href="https://www.npmjs.org/doc/">https://www.npmjs.org/doc/</a>, or run:</p>
-<pre><code>npm config set viewer browser</code></pre>
-<p>to open these documents in your default web browser rather than <code>man</code>.</p>
-<h2 id="It-didn-t-work">It didn&#39;t work.</h2>
-<p>That&#39;s not really a question.</p>
-<h2 id="Why-didn-t-it-work">Why didn&#39;t it work?</h2>
-<p>I don&#39;t know yet.</p>
-<p>Read the error output, and if you can&#39;t figure out what it means,
-do what it says and post a bug with all the information it asks for.</p>
-<h2 id="Where-does-npm-put-stuff">Where does npm put stuff?</h2>
-<p>See <code><a href="../files/npm-folders.html">npm-folders(5)</a></code></p>
-<p>tl;dr:</p>
-<ul><li>Use the <code>npm root</code> command to see where modules go, and the <code>npm bin</code>
-command to see where executables go</li><li>Global installs are different from local installs.  If you install
-something with the <code>-g</code> flag, then its executables go in <code>npm bin -g</code>
-and its modules go in <code>npm root -g</code>.</li></ul>
-<h2 id="How-do-I-install-something-on-my-computer-in-a-central-location">How do I install something on my computer in a central location?</h2>
-<p>Install it globally by tacking <code>-g</code> or <code>--global</code> to the command.  (This
-is especially important for command line utilities that need to add
-their bins to the global system <code>PATH</code>.)</p>
-<h2 id="I-installed-something-globally-but-I-can-t-require-it">I installed something globally, but I can&#39;t <code>require()</code> it</h2>
-<p>Install it locally.</p>
-<p>The global install location is a place for command-line utilities
-to put their bins in the system <code>PATH</code>.  It&#39;s not for use with <code>require()</code>.</p>
-<p>If you <code>require()</code> a module in your code, then that means it&#39;s a
-dependency, and a part of your program.  You need to install it locally
-in your program.</p>
-<h2 id="Why-can-t-npm-just-put-everything-in-one-place-like-other-package-managers">Why can&#39;t npm just put everything in one place, like other package managers?</h2>
-<p>Not every change is an improvement, but every improvement is a change.
-This would be like asking git to do network IO for every commit.  It&#39;s
-not going to happen, because it&#39;s a terrible idea that causes more
-problems than it solves.</p>
-<p>It is much harder to avoid dependency conflicts without nesting
-dependencies.  This is fundamental to the way that npm works, and has
-proven to be an extremely successful approach.  See <code><a href="../files/npm-folders.html">npm-folders(5)</a></code> for
-more details.</p>
-<p>If you want a package to be installed in one place, and have all your
-programs reference the same copy of it, then use the <code>npm link</code> command.
-That&#39;s what it&#39;s for.  Install it globally, then link it into each
-program that uses it.</p>
-<h2 id="Whatever-I-really-want-the-old-style-everything-global-style">Whatever, I really want the old style &#39;everything global&#39; style.</h2>
-<p>Write your own package manager.  You could probably even wrap up <code>npm</code>
-in a shell script if you really wanted to.</p>
-<p>npm will not help you do something that is known to be a bad idea.</p>
-<h2 id="Should-I-check-my-node_modules-folder-into-git">Should I check my <code>node_modules</code> folder into git?</h2>
-<p>Mikeal Rogers answered this question very well:</p>
-<p><a href="http://www.mikealrogers.com/posts/nodemodules-in-git.html">http://www.mikealrogers.com/posts/nodemodules-in-git.html</a></p>
-<p>tl;dr</p>
-<ul><li>Check <code>node_modules</code> into git for things you <strong>deploy</strong>, such as
-websites and apps.</li><li>Do not check <code>node_modules</code> into git for libraries and modules
-intended to be reused.</li><li>Use npm to manage dependencies in your dev environment, but not in
-your deployment scripts.</li></ul>
-<h2 id="Is-it-npm-or-NPM-or-Npm">Is it &#39;npm&#39; or &#39;NPM&#39; or &#39;Npm&#39;?</h2>
-<p>npm should never be capitalized unless it is being displayed in a
-location that is customarily all-caps (such as the title of man pages.)</p>
-<h2 id="If-npm-is-an-acronym-why-is-it-never-capitalized">If &#39;npm&#39; is an acronym, why is it never capitalized?</h2>
-<p>Contrary to the belief of many, &quot;npm&quot; is not in fact an abbreviation for
-&quot;Node Package Manager&quot;.  It is a recursive bacronymic abbreviation for
-&quot;npm is not an acronym&quot;.  (If it was &quot;ninaa&quot;, then it would be an
-acronym, and thus incorrectly named.)</p>
-<p>&quot;NPM&quot;, however, <em>is</em> an acronym (more precisely, a capitonym) for the
-National Association of Pastoral Musicians.  You can learn more
-about them at <a href="http://npm.org/">http://npm.org/</a>.</p>
-<p>In software, &quot;NPM&quot; is a Non-Parametric Mapping utility written by
-Chris Rorden.  You can analyze pictures of brains with it.  Learn more
-about the (capitalized) NPM program at <a href="http://www.cabiatl.com/mricro/npm/">http://www.cabiatl.com/mricro/npm/</a>.</p>
-<p>The first seed that eventually grew into this flower was a bash utility
-named &quot;pm&quot;, which was a shortened descendent of &quot;pkgmakeinst&quot;, a
-bash function that was used to install various different things on different
-platforms, most often using Yahoo&#39;s <code>yinst</code>.  If <code>npm</code> was ever an
-acronym for anything, it was <code>node pm</code> or maybe <code>new pm</code>.</p>
-<p>So, in all seriousness, the &quot;npm&quot; project is named after its command-line
-utility, which was organically selected to be easily typed by a right-handed
-programmer using a US QWERTY keyboard layout, ending with the
-right-ring-finger in a postition to type the <code>-</code> key for flags and
-other command-line arguments.  That command-line utility is always
-lower-case, though it starts most sentences it is a part of.</p>
-<h2 id="How-do-I-list-installed-packages">How do I list installed packages?</h2>
-<p><code>npm ls</code></p>
-<h2 id="How-do-I-search-for-packages">How do I search for packages?</h2>
-<p><code>npm search</code></p>
-<p>Arguments are greps.  <code>npm search jsdom</code> shows jsdom packages.</p>
-<h2 id="How-do-I-update-npm">How do I update npm?</h2>
-<pre><code>npm update npm -g</code></pre>
-<p>You can also update all outdated local packages by doing <code>npm update</code> without
-any arguments, or global packages by doing <code>npm update -g</code>.</p>
-<p>Occasionally, the version of npm will progress such that the current
-version cannot be properly installed with the version that you have
-installed already.  (Consider, if there is ever a bug in the <code>update</code>
-command.)</p>
-<p>In those cases, you can do this:</p>
-<pre><code>curl https://npmjs.org/install.sh | sh</code></pre>
-<h2 id="What-is-a-package">What is a <code>package</code>?</h2>
-<p>A package is:</p>
-<ul><li>a) a folder containing a program described by a package.json file</li><li>b) a gzipped tarball containing (a)</li><li>c) a url that resolves to (b)</li><li>d) a <code>&lt;name&gt;@&lt;version&gt;</code> that is published on the registry with (c)</li><li>e) a <code>&lt;name&gt;@&lt;tag&gt;</code> that points to (d)</li><li>f) a <code>&lt;name&gt;</code> that has a &quot;latest&quot; tag satisfying (e)</li><li>g) a <code>git</code> url that, when cloned, results in (a).</li></ul>
-<p>Even if you never publish your package, you can still get a lot of
-benefits of using npm if you just want to write a node program (a), and
-perhaps if you also want to be able to easily install it elsewhere
-after packing it up into a tarball (b).</p>
-<p>Git urls can be of the form:</p>
-<pre><code>git://github.com/user/project.git#commit-ish
-git+ssh://user@hostname:project.git#commit-ish
-git+http://user@hostname/project/blah.git#commit-ish
-git+https://user@hostname/project/blah.git#commit-ish</code></pre>
-<p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as
-an argument to <code>git checkout</code>.  The default is <code>master</code>.</p>
-<h2 id="What-is-a-module">What is a <code>module</code>?</h2>
-<p>A module is anything that can be loaded with <code>require()</code> in a Node.js
-program.  The following things are all examples of things that can be
-loaded as modules:</p>
-<ul><li>A folder with a <code>package.json</code> file containing a <code>main</code> field.</li><li>A folder with an <code>index.js</code> file in it.</li><li>A JavaScript file.</li></ul>
-<p>Most npm packages are modules, because they are libraries that you
-load with <code>require</code>.  However, there&#39;s no requirement that an npm
-package be a module!  Some only contain an executable command-line
-interface, and don&#39;t provide a <code>main</code> field for use in Node programs.</p>
-<p>Almost all npm packages (at least, those that are Node programs)
-<em>contain</em> many modules within them (because every file they load with
-<code>require()</code> is a module).</p>
-<p>In the context of a Node program, the <code>module</code> is also the thing that
-was loaded <em>from</em> a file.  For example, in the following program:</p>
-<pre><code>var req = require(&#39;request&#39;)</code></pre>
-<p>we might say that &quot;The variable <code>req</code> refers to the <code>request</code> module&quot;.</p>
-<h2 id="So-why-is-it-the-node_modules-folder-but-package-json-file-Why-not-node_packages-or-module-json">So, why is it the &quot;<code>node_modules</code>&quot; folder, but &quot;<code>package.json</code>&quot; file?  Why not <code>node_packages</code> or <code>module.json</code>?</h2>
-<p>The <code>package.json</code> file defines the package.  (See &quot;What is a
-package?&quot; above.)</p>
-<p>The <code>node_modules</code> folder is the place Node.js looks for modules.
-(See &quot;What is a module?&quot; above.)</p>
-<p>For example, if you create a file at <code>node_modules/foo.js</code> and then
-had a program that did <code>var f = require(&#39;foo.js&#39;)</code> then it would load
-the module.  However, <code>foo.js</code> is not a &quot;package&quot; in this case,
-because it does not have a package.json.</p>
-<p>Alternatively, if you create a package which does not have an
-<code>index.js</code> or a <code>&quot;main&quot;</code> field in the <code>package.json</code> file, then it is
-not a module.  Even if it&#39;s installed in <code>node_modules</code>, it can&#39;t be
-an argument to <code>require()</code>.</p>
-<h2 id="node_modules-is-the-name-of-my-deity-s-arch-rival-and-a-Forbidden-Word-in-my-religion-Can-I-configure-npm-to-use-a-different-folder"><code>&quot;node_modules&quot;</code> is the name of my deity&#39;s arch-rival, and a Forbidden Word in my religion.  Can I configure npm to use a different folder?</h2>
-<p>No.  This will never happen.  This question comes up sometimes,
-because it seems silly from the outside that npm couldn&#39;t just be
-configured to put stuff somewhere else, and then npm could load them
-from there.  It&#39;s an arbitrary spelling choice, right?  What&#39;s the big
-deal?</p>
-<p>At the time of this writing, the string <code>&#39;node_modules&#39;</code> appears 151
-times in 53 separate files in npm and node core (excluding tests and
-documentation).</p>
-<p>Some of these references are in node&#39;s built-in module loader.  Since
-npm is not involved <strong>at all</strong> at run-time, node itself would have to
-be configured to know where you&#39;ve decided to stick stuff.  Complexity
-hurdle #1.  Since the Node module system is locked, this cannot be
-changed, and is enough to kill this request.  But I&#39;ll continue, in
-deference to your deity&#39;s delicate feelings regarding spelling.</p>
-<p>Many of the others are in dependencies that npm uses, which are not
-necessarily tightly coupled to npm (in the sense that they do not read
-npm&#39;s configuration files, etc.)  Each of these would have to be
-configured to take the name of the <code>node_modules</code> folder as a
-parameter.  Complexity hurdle #2.</p>
-<p>Furthermore, npm has the ability to &quot;bundle&quot; dependencies by adding
-the dep names to the <code>&quot;bundledDependencies&quot;</code> list in package.json,
-which causes the folder to be included in the package tarball.  What
-if the author of a module bundles its dependencies, and they use a
-different spelling for <code>node_modules</code>?  npm would have to rename the
-folder at publish time, and then be smart enough to unpack it using
-your locally configured name.  Complexity hurdle #3.</p>
-<p>Furthermore, what happens when you <em>change</em> this name?  Fine, it&#39;s
-easy enough the first time, just rename the <code>node_modules</code> folders to
-<code>./blergyblerp/</code> or whatever name you choose.  But what about when you
-change it again?  npm doesn&#39;t currently track any state about past
-configuration settings, so this would be rather difficult to do
-properly.  It would have to track every previous value for this
-config, and always accept any of them, or else yesterday&#39;s install may
-be broken tomorrow.  Complexity hurdle #5.</p>
-<p>Never going to happen.  The folder is named <code>node_modules</code>.  It is
-written indelibly in the Node Way, handed down from the ancient times
-of Node 0.3.</p>
-<h2 id="How-do-I-install-node-with-npm">How do I install node with npm?</h2>
-<p>You don&#39;t.  Try one of these node version managers:</p>
-<p>Unix:</p>
-<ul><li><a href="http://github.com/isaacs/nave">http://github.com/isaacs/nave</a></li><li><a href="http://github.com/visionmedia/n">http://github.com/visionmedia/n</a></li><li><a href="http://github.com/creationix/nvm">http://github.com/creationix/nvm</a></li></ul>
-<p>Windows:</p>
-<ul><li><a href="http://github.com/marcelklehr/nodist">http://github.com/marcelklehr/nodist</a></li><li><a href="https://github.com/hakobera/nvmw">https://github.com/hakobera/nvmw</a></li><li><a href="https://github.com/nanjingboy/nvmw">https://github.com/nanjingboy/nvmw</a></li></ul>
-<h2 id="How-can-I-use-npm-for-development">How can I use npm for development?</h2>
-<p>See <code><a href="../misc/npm-developers.html">npm-developers(7)</a></code> and <code><a href="../files/package.json.html">package.json(5)</a></code>.</p>
-<p>You&#39;ll most likely want to <code>npm link</code> your development folder.  That&#39;s
-awesomely handy.</p>
-<p>To set up your own private registry, check out <code><a href="../misc/npm-registry.html">npm-registry(7)</a></code>.</p>
-<h2 id="Can-I-list-a-url-as-a-dependency">Can I list a url as a dependency?</h2>
-<p>Yes.  It should be a url to a gzipped tarball containing a single folder
-that has a package.json in its root, or a git url.
-(See &quot;what is a package?&quot; above.)</p>
-<h2 id="How-do-I-symlink-to-a-dev-folder-so-I-don-t-have-to-keep-re-installing">How do I symlink to a dev folder so I don&#39;t have to keep re-installing?</h2>
-<p>See <code><a href="../cli/npm-link.html">npm-link(1)</a></code></p>
-<h2 id="The-package-registry-website-What-is-that-exactly">The package registry website.  What is that exactly?</h2>
-<p>See <code><a href="../misc/npm-registry.html">npm-registry(7)</a></code>.</p>
-<h2 id="I-forgot-my-password-and-can-t-publish-How-do-I-reset-it">I forgot my password, and can&#39;t publish.  How do I reset it?</h2>
-<p>Go to <a href="https://npmjs.org/forgot">https://npmjs.org/forgot</a>.</p>
-<h2 id="I-get-ECONNREFUSED-a-lot-What-s-up">I get ECONNREFUSED a lot.  What&#39;s up?</h2>
-<p>Either the registry is down, or node&#39;s DNS isn&#39;t able to reach out.</p>
-<p>To check if the registry is down, open up
-<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a> in a web browser.  This will also tell
-you if you are just unable to access the internet for some reason.</p>
-<p>If the registry IS down, let us know by emailing <a href="mailto:support@npmjs.com">support@npmjs.com</a>
-or posting an issue at <a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a>.  If it&#39;s
-down for the world (and not just on your local network) then we&#39;re
-probably already being pinged about it.</p>
-<p>You can also often get a faster response by visiting the #npm channel
-on Freenode IRC.</p>
-<h2 id="Why-no-namespaces">Why no namespaces?</h2>
-<p>Please see this discussion: <a href="https://github.com/npm/npm/issues/798">https://github.com/npm/npm/issues/798</a></p>
-<p>tl;dr - It doesn&#39;t actually make things better, and can make them worse.</p>
-<p>If you want to namespace your own packages, you may: simply use the
-<code>-</code> character to separate the names.  npm is a mostly anarchic system.
-There is not sufficient need to impose namespace rules on everyone.</p>
-<h2 id="Who-does-npm">Who does npm?</h2>
-<p>npm was originally written by Isaac Z. Schlueter, and many others have
-contributed to it, some of them quite substantially.</p>
-<p>The npm open source project, The npm Registry, and <a href="https://www.npmjs.org">the community
-website</a> are maintained and operated by the
-good folks at <a href="https://www.npmjs.com">npm, Inc.</a></p>
-<h2 id="I-have-a-question-or-request-not-addressed-here-Where-should-I-put-it">I have a question or request not addressed here. Where should I put it?</h2>
-<p>Post an issue on the github project:</p>
-<ul><li><a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li></ul>
-<h2 id="Why-does-npm-hate-me">Why does npm hate me?</h2>
-<p>npm is not capable of hatred.  It loves everyone, especially you.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<ul><li><a href="../cli/npm.html">npm(1)</a></li><li><a href="../misc/npm-developers.html">npm-developers(7)</a></li><li><a href="../files/package.json.html">package.json(5)</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-config.html">npm-config(7)</a></li><li><a href="../files/npm-folders.html">npm-folders(5)</a></li></ul>
-</div>
-<p id="footer">npm-faq &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>