node/deps/npm/html/api/config.html

<!doctype html>
<html>
  <title>config</title>
  <meta http-equiv="content-type" value="text/html;utf-8">
  <link rel="stylesheet" type="text/css" href="./style.css">

  <body>
    <div id="wrapper">
<h1><a href="../api/config.html">config</a></h1> <p>Manage the npm configuration files</p>

<h2 id="SYNOPSIS">SYNOPSIS</h2>

<pre><code>npm.commands.config(args, callback)
var val = npm.config.get(key)
npm.config.set(key, val)</code></pre>

<h2 id="DESCRIPTION">DESCRIPTION</h2>

<p>This function acts much the same way as the command-line version.  The first
element in the array tells config what to do. Possible values are:</p>

<ul><li><p><code>set</code></p><p>Sets a config parameter.  The second element in <code>args</code> is interpreted as the
key, and the third element is interpreted as the value.</p></li><li><p><code>get</code></p><p>Gets the value of a config parameter. The second element in <code>args</code> is the
key to get the value of.</p></li><li><p><code>delete</code> (<code>rm</code> or <code>del</code>)</p><p>Deletes a parameter from the config. The second element in <code>args</code> is the
key to delete.</p></li><li><p><code>list</code> (<code>ls</code>)</p><p>Show all configs that aren't secret. No parameters necessary.</p></li><li><p><code>edit</code>:</p><p>Opens the config file in the default editor. This command isn't very useful
programmatically, but it is made available.</p></li></ul>

<p>To programmatically access npm configuration settings, or set them for
the duration of a program, use the <code>npm.config.set</code> and <code>npm.config.get</code>
functions instead.</p>

<h2 id="SEE-ALSO">SEE ALSO</h2>

<ul><li><a href="../api/npm.html">npm(3)</a></li></ul>
</div>
<p id="footer">config &mdash; npm@1.1.23</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>
</body></html>
Remove npm's .gitignore, add generated docs 13 years ago			`<!doctype html>`
			`<html>`
			`<title>config</title>`
			`<meta http-equiv="content-type" value="text/html;utf-8">`
			`<link rel="stylesheet" type="text/css" href="./style.css">`

			`<body>`
			`<div id="wrapper">`
			`<h1><a href="../api/config.html">config</a></h1> <p>Manage the npm configuration files</p>`

			`<h2 id="SYNOPSIS">SYNOPSIS</h2>`

			`<pre><code>npm.commands.config(args, callback)`
			`var val = npm.config.get(key)`
			`npm.config.set(key, val)</code></pre>`

			`<h2 id="DESCRIPTION">DESCRIPTION</h2>`

			`<p>This function acts much the same way as the command-line version. The first`
			`element in the array tells config what to do. Possible values are:</p>`

			`<ul><li><p><code>set</code></p><p>Sets a config parameter. The second element in <code>args</code> is interpreted as the`
			`key, and the third element is interpreted as the value.</p></li><li><p><code>get</code></p><p>Gets the value of a config parameter. The second element in <code>args</code> is the`
			`key to get the value of.</p></li><li><p><code>delete</code> (<code>rm</code> or <code>del</code>)</p><p>Deletes a parameter from the config. The second element in <code>args</code> is the`
			`key to delete.</p></li><li><p><code>list</code> (<code>ls</code>)</p><p>Show all configs that aren't secret. No parameters necessary.</p></li><li><p><code>edit</code>:</p><p>Opens the config file in the default editor. This command isn't very useful`
			`programmatically, but it is made available.</p></li></ul>`

			`<p>To programmatically access npm configuration settings, or set them for`
			`the duration of a program, use the <code>npm.config.set</code> and <code>npm.config.get</code>`
			`functions instead.</p>`

			`<h2 id="SEE-ALSO">SEE ALSO</h2>`

			`<ul><li><a href="../api/npm.html">npm(3)</a></li></ul>`
			`</div>`
upgrade npm to 1.1.23 This also upgrades node-gyp to 0.4.3 13 years ago			`<p id="footer">config — npm@1.1.23</p>`
Remove npm's .gitignore, add generated docs 13 years ago			`<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>`
			`</body></html>`