Jump to content

npm

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Theprogrammer (talk | contribs) at 01:12, 15 January 2018 (→updated about package-lock.json). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
npm
Original author(s)Isaac Z. Schlueter
Developer(s)Rebecca Turner, Kat Marchán, others
Initial releaseJanuary 12, 2010; 15 years ago (2010-01-12)[1]
Stable release
5.6.0 / 28 November 2017; 7 years ago (2017-11-28)[2]
Repository
Written inJavaScript
LicenseArtistic License 2.0
Websitewww.npmjs.com

npm is a package manager for the JavaScript programming language. It is the default package manager for the JavaScript runtime environment Node.js. It consists of a command line client, also called npm, and an online database of public and paid-for private packages, called the npm registry. The registry is accessed via the client, and the available packages can be browsed and searched via the npm website. The package manager and the registry are managed by npm, Inc.

History

npm is written entirely in JavaScript and was developed by Isaac Z. Schlueter as a result of having "seen module packaging done terribly" and with inspiration from the shortcomings of other similar projects such as PEAR (PHP) and CPAN (Perl).[3]

Notable breakage

In March 2016, npm attracted press attention[4] after a package called left-pad, which was depended upon by many popular JavaScript packages, was unpublished as the result of a dispute.[5] Although the package was re-published 3 hours later,[6] it caused widespread disruption, leading npm to change its policies regarding unpublishing to prevent a similar event in the future.[7]

Description

npm is included as a recommended feature in Node.js installer.[8] npm consists of a command line client that interacts with a remote registry. It allows users to consume and distribute JavaScript modules that are available on the registry.[9] Packages on the registry are in CommonJS format and include a metadata file in JSON format.[10] Over 477,000 packages are available on the main npm registry.[11] The registry has no vetting process for submission, which means that packages found there can be low quality, insecure, or malicious.[10] Instead, npm relies on user reports to take down packages if they violate policies by being low quality, insecure or malicious.[12] npm exposes statistics including number of downloads and number of depending packages to assist developers in judging the quality of packages.[13]

Usage

npm can manage packages that are local dependencies of a particular project, as well as globally-installed JavaScript tools.[14] When used as a dependency manager for a local project, npm can install, in one command, all the dependencies of a project through the package.json file.[15] In the package.json file, each dependency can specify a range of valid versions using the semantic versioning scheme, allowing developers to auto-update their packages while at the same time avoiding unwanted breaking changes.[16] npm also provides version-bumping tools for developers to tag their packages with a particular version.[17]. npm also provides something called as package-lock.json[18] file which has the entry of the exact version used by the project after evaluating semantic versioning in package.json.

Alternatives

There are a number of open-source alternatives to npm for installing modular JavaScript, including ied, pnpm, npm-install, npmd, and Yarn, the last of which was released by Facebook in October 2016.[19] They are all compatible with the public npm registry and use it by default, but provide different client-side experiences, usually focused on improving performance and determinism compared to the npm client.[20]

See also

References

  1. ^ "Earliest releases of npm". GitHub. Retrieved 27 July 2016.
  2. ^ "npm/CHANGELOG.md at latest". GitHub. 2017-11-28. Archived from the original on 2017-12-17. Retrieved 2017-12-17.
  3. ^ Schlueter, Isaac Z. (25 March 2013). "Forget CommonJS. It's dead. **We are server side JavaScript.**". GitHub.
  4. ^ Yegulalp, Serdar (23 March 2016). "How one yanked JavaScript package wreaked havoc". InfoWorld. Retrieved 22 July 2016.
  5. ^ Williams, Chris. "How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript". The Register. Retrieved 17 April 2016.
  6. ^ "kik, left-pad, and npm". Retrieved 9 May 2017.
  7. ^ "changes to unpublish policy". Retrieved 9 May 2017.
  8. ^ Dierx, Peter (30 March 2016). "A Beginner's Guide to npm — the Node Package Manager". sitepoint. Retrieved 22 July 2016.
  9. ^ Ampersand.js. "Ampersand.js - Learn". ampersandjs.com. Retrieved 22 July 2016.
  10. ^ a b Ojamaa, Andres; Duuna, Karl (2012). "Assessing the Security of Node.js Platform". IEEE Xplore. Retrieved 22 July 2016.
  11. ^ Kennedy, Hugh; DeVay, Paul. "Understanding npm". Nsight. Retrieved 22 July 2016.
  12. ^ "npm Code of Conduct: acceptable package content". Retrieved 9 May 2017.
  13. ^ Vorbach, Paul. "npm-stat: download statistics for NPM packages". npm-stat.com.
  14. ^ Ellingwood, Justin. "How To Use npm to Manage Node.js Packages on a Linux Server". DigitalOcean. Retrieved 22 October 2016.
  15. ^ "npm-install". docs.npmjs. Retrieved 22 October 2016.
  16. ^ "semver". docs.npmjs. Retrieved 22 October 2016.
  17. ^ "npm-version". docs.npm. Retrieved 29 October 2016.
  18. ^ Koirala, Shivprasad (21 Aug 2017). "What is the need of package-lock.json in Node?". codeproject. {{cite web}}: Cite has empty unknown parameter: |dead-url= (help)
  19. ^ "Hello, Yarn!". The npm Blog. 11 October 2016. Retrieved 17 December 2016.
  20. ^ Katz, Yehuda (11 October 2016). "Why I'm working on Yarn". Retrieved 17 December 2016.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Npm&oldid=820499489"