npm

Developers can use npm to install and publish their Node.js applications.

npm can be used from the Node.js CLI, or it can be used programmatically inside Node.js JavaScript code.

npm is just like many other package managers,being  very similar to apt-get, Composer, RubyGems, PEAR, etc..

Just like the aforementioned tools, npm can manage dependencies, help with installations, bundle packages, search for new packages, update existing packages, remove unwanted packages, star packages for later usage and many other more.

Documentation included in the npm package, to help developers get started and improve the way their work with Node.js.

What is new in this release:

• The multi-stage installer.
• Install: it looks different.
• Install: it works different.
• Flat, flat, flat.
• Shrinkwraps: they are a-changin'.
• The Age of Progress (Bars).

What is new in version 3.8.3:

• The multi-stage installer.
• Install: it looks different.
• Install: it works different.
• Flat, flat, flat.
• Shrinkwraps: they are a-changin'.
• The Age of Progress (Bars).

What is new in version 3.7.0:

• The multi-stage installer.
• Install: it looks different.
• Install: it works different.
• Flat, flat, flat.
• Shrinkwraps: they are a-changin'.
• The Age of Progress (Bars).

What is new in version 3.5.1:

• The multi-stage installer.
• Install: it looks different.
• Install: it works different.
• Flat, flat, flat.
• Shrinkwraps: they are a-changin'.
• The Age of Progress (Bars).

What is new in version 2.6.1:

• npm outdated --long now includes a column showing the type of dependency.

What is new in version 2.4.1:

• The dist-tag endpoints for npm dist-tag {add,rm,ls} are now live on the public npm registry.

What is new in version 2.3.0:

• The new whoami endpoint might not return a value.
• Registries based on token-based auth can now offer starring.
• Fixed HTTP[S] connection keep-alive on Node 0.11 / io.js 1.0.
• Added caching based on Last-Modified / If-Modified-Since headers.
• Use %COMSPEC% when set on Windows.
• Ensure Git cache prefix exists before repo clone on Windows.

What is new in version 2.2.0:

• Added a new default script that will print out environment values.

What is new in version 2.1.10:

• Fixed:
• Log "already built" messages at info, not error.
• GitHub won't redirect you through an HTML page to a compressed tarball if you don't tell it you accept JSON responses.
• 1: Use graceful-fs so the whole dependency tree gets read, even in case of EMFILE.
• Grammar in docs.

What is new in version 2.1.5:

• Defactor npmconf back into npm.
• Install peerDependencies from top.
• Better error messages on malformed .npmrc properties.
• Replace instances of 'hash' with 'object' in documentation.
• Clarify how local paths should be used.
• Work around bug in marked.

What is new in version 2.0.0:

• npm now assumes that node is newer than 0.6.
• Defer rollbacks until just before the CLI exits.
• Ensure permissions are set correctly in cache when running as root.
• Make default error display less scary.
• Correctly interpret relative paths for local dependencies.

What is new in version 1.4.0:

• Remove npm publish --force.
• Other changes to the registry client related to saved configs and couch logins.
• Show an error to the user when doing npm update and the package.json specifies a version that does not exist.

What is new in version 1.3.24:

• Added --long doc for search output in doc/misc.
• Tidy search output via columnify.
• Cleaned up ignore-install-link test.
• Fixed outdated-json test on Windows.
• Fixed npm install overwrites npm link.
• Supports multiple packagenames in npm docs.
• Fixed updating Git URLs with credentials in them.

Requirements:

• Node.js 0.6 or higher