Install a package
\nSYNOPSIS<\/p>\n
npm install (with no args in a package dir)
\nnpm install <tarball file>
\nnpm install <tarball url>
\nnpm install <folder>
\nnpm install <name> [–save|–save-dev|–save-optional]
\nnpm install <name>@<tag>
\nnpm install <name>@<version>
\nnpm install <name>@<version range>
\nnpm i (with any of the previous argument usage)<\/p>\n
This command installs a package, and any packages that it depends on. If the package has a shrinkwrap file, the installation of dependencies will be driven by that. See npm-shrinkwrap(1).<\/p>\n
A package is:<\/p>\n
a) a folder containing a program described by a package.json file
\nb) a gzipped tarball containing (a)
\nc) a url that resolves to (b)
\nd) a <name>@<version> that is published on the registry with (c)
\ne) a <name>@<tag> that points to (d)
\nf) a <name> that has a “latest” tag satisfying (e)
\ng) a <git remote url> that resolves to (b)<\/p>\n
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>\n
<\/p>\n