<p>If that's not fancy enough for you, then you can fetch the code with
<p>If that's not fancy enough for you, then you can fetch the code with
git, and mess with it directly.</p>
git, and mess with it directly.</p>
<h2id="installing-on-cygwin">Installing on Cygwin</h2>
<h2id="installing-on-cygwin">Installing on Cygwin</h2>
<p>No.</p>
<p>No.</p>
<h2id="permissions-when-using-npm-to-install-other-stuff">Permissions when Using npm to Install Other Stuff</h2>
<p><strong>tl;dr</strong></p>
<ul>
<li>Use <code>sudo</code> for greater safety. Or don't, if you prefer not to.</li>
<li>npm will downgrade permissions if it's root before running any build
scripts that package authors specified.</li>
</ul>
<h3id="more-details-">More details...</h3>
<p>As of version 0.3, it is recommended to run npm as root.
This allows npm to change the user identifier to the <code>nobody</code> user prior
to running any package build or test commands.</p>
<p>If you are not the root user, or if you are on a platform that does not
support uid switching, then npm will not attempt to change the userid.</p>
<p>If you would like to ensure that npm <strong>always</strong> runs scripts as the
"nobody" user, and have it fail if it cannot downgrade permissions, then
set the following configuration param:</p>
<pre><code>npm config set unsafe-perm false
</code></pre><p>This will prevent running in unsafe mode, even as non-root users.</p>
<h2id="uninstalling">Uninstalling</h2>
<h2id="uninstalling">Uninstalling</h2>
<p>So sad to see you go.</p>
<p>So sad to see you go.</p>
<pre><code>sudo npm uninstall npm -g
<pre><code>sudo npm uninstall npm -g
@ -122,11 +107,11 @@ change the value for <em>all</em> npm commands in that process.</p>
command line arguments using nopt. You may also want to check out <code>npm
command line arguments using nopt. You may also want to check out <code>npm
help config</code> to learn about all the options you can set there.</p>
help config</code> to learn about all the options you can set there.</p>
<h2id="more-docs">More Docs</h2>
<h2id="more-docs">More Docs</h2>
<p>Check out the <ahref="https://www.npmjs.org/doc/">docs</a>,
<p>Check out the <ahref="https://docs.npmjs.com/">docs</a>,
especially the <ahref="https://www.npmjs.org/doc/faq.html">faq</a>.</p>
especially the <ahref="https://docs.npmjs.com/misc/faq">faq</a>.</p>
<p>You can use the <code>npm help</code> command to read any of them.</p>
<p>You can use the <code>npm help</code> command to read any of them.</p>
<p>If you're a developer, and you want to use npm to publish your program,
<p>If you're a developer, and you want to use npm to publish your program,
you should <ahref="https://www.npmjs.org/doc/developers.html">read this</a></p>
you should <ahref="https://docs.npmjs.com/misc/developers">read this</a></p>
<h2id="legal-stuff">Legal Stuff</h2>
<h2id="legal-stuff">Legal Stuff</h2>
<p>"npm" and "The npm Registry" are owned by npm, Inc.
<p>"npm" and "The npm Registry" are owned by npm, Inc.
All rights reserved. See the included LICENSE file for more details.</p>
All rights reserved. See the included LICENSE file for more details.</p>
@ -139,9 +124,9 @@ ensure accountability, there is absolutely no guarantee, warrantee, or
assertion expressed or implied as to the quality, fitness for a
assertion expressed or implied as to the quality, fitness for a
specific purpose, or lack of malice in any given npm package.</p>
specific purpose, or lack of malice in any given npm package.</p>
<p>If you have a complaint about a package in the public npm registry,
<p>If you have a complaint about a package in the public npm registry,
and cannot <ahref="https://www.npmjs.org/doc/misc/npm-disputes.html">resolve it with the package
and cannot <ahref="https://docs.npmjs.com/misc/disputes">resolve it with the package
owner</a>, please email
owner</a>, please email
<ahref="mailto:support@npmjs.com">support@npmjs.com</a> and explain the situation.</p>
<ahref="mailto:support@npmjs.com">support@npmjs.com</a> and explain the situation.</p>
<p>Any data published to The npm Registry (including user account
<p>Any data published to The npm Registry (including user account
information) may be removed or modified at the sole discretion of the
information) may be removed or modified at the sole discretion of the
npm server administrators.</p>
npm server administrators.</p>
@ -160,8 +145,6 @@ ban your account in extreme cases. So don't do that.</p>
</code></pre><p>This will ensure that all requests to that registry (including for tarballs)
</code></pre><p>This will ensure that all requests to that registry (including for tarballs)
include an authorization header. See <code>always-auth</code> in <code><ahref="../misc/npm-config.html"><ahref="../misc/npm-config.html">npm-config(7)</a></a></code> for more
include an authorization header. See <code>always-auth</code> in <code><ahref="../misc/npm-config.html"><ahref="../misc/npm-config.html">npm-config(7)</a></a></code> for more
details on always-auth. Registry-specific configuaration of <code>always-auth</code> takes
details on always-auth. Registry-specific configuration of <code>always-auth</code> takes
precedence over any global configuration.</p>
precedence over any global configuration.</p>
<h2id="see-also">SEE ALSO</h2>
<h2id="see-also">SEE ALSO</h2>
<ul>
<ul>
@ -67,5 +68,5 @@ precedence over any global configuration.</p>
@ -24,7 +24,7 @@ symlink from the local <code>node_modules</code> folder to the global symlink.</
<p>Note that <code>package-name</code> is taken from <code>package.json</code>,
<p>Note that <code>package-name</code> is taken from <code>package.json</code>,
not from directory name.</p>
not from directory name.</p>
<p>The package name can be optionally prefixed with a scope. See <code><ahref="../misc/npm-scope.html"><ahref="../misc/npm-scope.html">npm-scope(7)</a></a></code>.
<p>The package name can be optionally prefixed with a scope. See <code><ahref="../misc/npm-scope.html"><ahref="../misc/npm-scope.html">npm-scope(7)</a></a></code>.
The scope must by preceded by an @-symbol and followed by a slash.</p>
The scope must be preceded by an @-symbol and followed by a slash.</p>
<p>When creating tarballs for <code>npm publish</code>, the linked packages are
<p>When creating tarballs for <code>npm publish</code>, the linked packages are
"snapshotted" to their current state by resolving the symbolic links.</p>
"snapshotted" to their current state by resolving the symbolic links.</p>
<p>This is handy for installing your own stuff, so that you can work on it and
<p>This is handy for installing your own stuff, so that you can work on it and
Forrest L Norvell
10 years ago
Ben Noordhuis