https://github.com/isaacs/npm/tree/master/doc
That's not really a question.
I don't know yet.
Read the error output, and if you can't figure out what it means, do what it says and post a bug with all the information it asks for.
If there doesn't seem to be enough output for your liking, run the
command with --loglevel verbose
or if you're really brave, --loglevel silly
.
npm config set loglevel error
You can also set it to win
or silent
for even more quietness.
npm ls installed
If you just want to see the names, and not all the registry data, you
can do: npm ls installed --no-registry
to turn off the registry.
npm ls
Arguments are greps. npm ls jsdom
shows jsdom packages.
npm update npm
You can also update all outdated packages by doing npm update
without
any arguments.
A package is:
- a) a folder containing a program described by a package.json file
- b) a gzipped tarball containing (a)
- c) a url that resolves to (b)
- d) a
<name>@<version>
that is published on the registry with (c) - e) a
<name>@<tag>
that points to (d) - f) a
<name>
that has a "latest" tag satisfying (e)
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).
You don't. Try one of these:
See npm help developers
and npm help json
.
You'll most likely want to npm link
your development folder. That's
awesomely handy.
No.
If you need to depend on something that isn't published, or a package that is published, but which you've modified slightly, you can do this.
The correct way is to do the following:
- add a
"name":"version"
entry to your package.json file. npm bundle install <pkg>
where<pkg>
is a url or path to your custom unpublished package.
When installing your package, npm will skip over any dependencies that are bundled.
No.
Source repositories change quickly. That is their purpose. Whatever you bundle into your package is your business, but having the registry refer to a git URL as a "dependency" defeats the whole purpose.
It's possible that something a bit more snazzy will be developed at some point in the future, but not likely. The current system allows for a lot of use cases, and is very easy to maintain.
npm link
See npm help registry
for more info.
As of this writing, node has problems uploading files over HTTPS. That means that publishes go over HTTP.
Until the problem is solved, npm will complain about being insecure. The warnings will disappear when node supports uploading tarballs over https reliably.
Email i@izs.me from the email address that you signed up with. Then wait a day or two maybe.
Either the registry is down, or node's DNS isn't able to reach out. This happens a lot if you don't follow all the steps in the Cygwin setup doc.
To check if the registry is down, open up http://registry.npmjs.org/ in a web browser. This will also tell you if you are just unable to access the internet for some reason.
If the registry IS down, let me know by emailing i@izs.me. I'll have someone kick it or something.
npm view npm author
npm view npm contributors
Discuss it on the mailing list, or post an issue.
npm is not capable of hatred. It loves everyone, especially you.