Talk:Npm

Leftpad was nominated for deletion. The discussion was closed on 29 December 2016 with a consensus to merge. Its contents were merged into Npm on 29 December 2016. The original page is now a redirect to this page. For the contribution history and old versions of the redirected article, please see its history; for its talk page, see here.

JavaScript Low‑importance

	This article is within the scope of WikiProject JavaScript, a collaborative effort to improve the coverage of articles related to JavaScript, and to the development of user scripts for use on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.JavaScriptWikipedia:WikiProject JavaScriptTemplate:WikiProject JavaScriptJavaScript articles
Low	This article has been rated as Low-importance on the importance scale.

Computing: Software / Free and open-source software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).
	This article is supported by Free and open-source software (assessed as Low-importance).

Early comments

It is pretty notable among Node.js users and developers. Search nodejs and npm on any serach engines for your references. — HenryLi (Talk) 21:30, 18 June 2011 (UTC)[reply]

This page says that I created npm as a result of frustrations working with the CommonJS. That isn't the case. Yes, I got frustrated with CommonJS, but my decision to create npm had much more to do with the frustrations of installing Node modules by hand. The cited article isn't even about npm, it's about Node's relationship to the attempt to standardize things like file system access and http client API. The mention of the Packages spec as an example only happened long after the original creation of npm, while I was an employee at Joyent. Since this is original authorship or whatever Wikipedia no-no, maybe someone else can investigate this further and either remove that comment, or at least try to find some better evidence that isn't blatantly misinterpreted? — IsaacSchlueter (Talk) Mon, 08 Dec 2014 22:40:23 UTC — Preceding undated comment added 22:41, 8 December 2014 (UTC)[reply]

@IsaacSchlueter: Done – FenixFeather ^(talk)^(Contribs) 00:40, 22 July 2016 (UTC)[reply]

@FenixFeather: Thanks! Isaac (talk) 17:48, 26 October 2017 (UTC)[reply]

According to the Manual of Style, shouldn't "npm" be spelled "Npm"? — Preceding unsigned comment added by Ralfstx (talk • contribs) 21:41, 27 January 2015 (UTC)[reply]

Platform?

There is no mention of platform in this article. And yet all examples I have found use Linux-style commands and pathnames. I think the article should state what complexities, if any, are needed to host npm and its friends (node.js, etc.) under Windows. David Spector (talk) 16:12, 25 May 2015 (UTC)[reply]

I don't know if that's actually necessary. Node.js has native installers for Windows and Mac that, by default, bundle npm with the installation. Once they're there, they behave like any other command line application and all the examples should apply. PassingStranger (talk) 22:03, 26 October 2015 (UTC)[reply]

Vetting Process

I made a change that indicates that npm is not special about reviews of packages. It was undone as needing a source log entry. I am not sure how this can be sourced. From looking at any other package manager the only one that would verify are the ones from Linux distributions. Neither Python, Perl, Ruby, PHP or npm have verification for packages. --Expatriaticus (talk) 18:02, 4 August 2016 (UTC)[reply]

Stuff on Wikipedia needs to be verifiable. If you can't find a source for it then it probably shouldn't be in the article. The sentence I wrote on npm is not overly harsh because it just summarizes what the source says. If you want to qualify it with "like most package managers..." then you should try to look for a source that also qualifies the lack of a vetting process on npm by pointing out that other package managers have equal lack of vetting process. If you just cite a bunch of sources on how several package managers don't have vetting processes, then that's WP:Synthesis. Hope that makes sense. – FenixFeather ^(talk)^(Contribs) 21:49, 4 August 2016 (UTC)[reply]

Would it not make sense to remove that claim then? Or at least to include it as well on the articles of all other programming language package managers on Wikipedia. --Expatriaticus (talk) 07:02, 5 August 2016 (UTC)[reply]

Yeah if you find articles on issues with certain package managers you should add them. What do you want to remove? – FenixFeather ^(talk)^(Contribs) 08:23, 5 August 2016 (UTC)[reply]

The sentence "The npm registry has no vetting process for submission, which means that packages found there can often be low quality, insecure, or malicious" in this form only exists on the npm article but the underlying issue exists on all platforms (no curation). Maybe it makes sense removing it? --Expatriaticus (talk) 14:52, 5 August 2016 (UTC)[reply]

I put that sentence there because there was significant coverage of this fact following the left-pad controversy. I honestly don't know why it shouldn't be included; the paper I cited seems to be a pretty reliable source. What's your rationale for removing it? – FenixFeather ^(talk)^(Contribs) 19:05, 5 August 2016 (UTC)[reply]

Registry Source

As far as I can tell, while npm is open source, the registry is either proprietary or a closed-box implementation based on CouchDb. Does anyone know of reliable sources that document the software freedom status of npm registry please? ClareTheSharer (talk) 17:49, 13 January 2017 (UTC)[reply]

Maintenance and rating of JavaScript articles

Concerning editing and maintaining JavaScript-related articles...

Collaboration...

If you are interested in collaborating on JavaScript articles or would like to see where you could help, stop by Wikipedia:WikiProject JavaScript and feel free to add your name to the participants list. Both editors and programmers are welcome.

Where to list JavaScript articles

We've found over 300 JavaScript-related articles so far. If you come across any others, please add them to that list.

User scripts

The WikiProject is also taking on the organization of the Wikipedia community's user script support pages. If you are interested in helping to organize information on the user scripts (or are curious about what we are up to), let us know!

If you have need for a user script that does not yet exist, or you have a cool idea for a user script or gadget, you can post it at Wikipedia:User scripts/Requests. And if you are a JavaScript programmer, that's a great place to find tasks if you are bored.

How to report JavaScript articles in need of attention

If you come across a JavaScript article desperately in need of editor attention, and it's beyond your ability to handle, you can add it to our list of JavaScript-related articles that need attention.

Rating JavaScript articles

At the top of the talk page of most every JavaScript-related article is a WikiProject JavaScript template where you can record the quality class and importance of the article. Doing so will help the community track the stage of completion and watch the highest priority articles more closely.

Thank you. The Transhumanist 01:12, 12 April 2017 (UTC)[reply]

Overloaded name "npm" needs disambiguation

npm is the name of a command-line tool, part of the name of a server system, the colloquial name of the whole facility and the name of the corporation seeking to profit from all of the above (and from the ambiguity of the term). The article makes no attempt to disambiguate this naming mess. It should, especially if spin doctors are going to start "optimising" the text to satisfy a corporate strategy. ClareTheSharer (talk) 10:47, 9 May 2017 (UTC)[reply]

"an online database of public packages"?

The intro says:

It consists of a command line client, also called npm, and an online database of public packages, called the npm registry.

As far as I know, not all npm packages are public. This should be fixed --إلياس الجزائري (talk) 14:21, 9 May 2017 (UTC)[reply]

Updated. Chininazu12 (talk) 02:51, 18 August 2017 (UTC)[reply]

"JavaScript runtime environment" explanation or dedicated page

Do the ignorant and naive (like myself), this phrase isn't entirely clear on its own. I added a link to https://en.wikipedia.org/w/index.php?title=Java_Runtime_Environment (which redirects to Java Virtual Machine, but I think a single sentence outlining (in laymen's terms) what a JavaScript runtime environment is would greatly aid in the understandability of this topic for those not already familiar with it. Zhermes (talk) 16:57, 20 December 2017 (UTC)[reply]

Acronym does not Stand for Node.js Package Manager

There are sources available from the NPM FAQ website that state that NPM is not an acronym for Node Package Manager, according to a Quara post. https://www.quora.com/I-keep-hearing-NPM-doesnt-stand-for-Node-Package-Manager-what-does-it-stand-for

I think it is important to verify this claim and change the opening paragraph if the claim is found to be true. — Preceding unsigned comment added by Apiotuch (talk • contribs) 10:14, 17 February 2019 (UTC)[reply]

That would be a bogus claim, and is completely false. Ordusifer (talk) 01:41, 26 March 2020 (UTC)[reply]

Officially, npm claims is is a "recursive bacronymic abbreviation for 'npm is not an acronym'": https://github.com/npm/cli#is-npm-an-acronym-for-node-package-manager — Preceding unsigned comment added by David McCoy (the hot one) (talk • contribs) 23:31, 10 June 2021 (UTC)[reply]

The Company

I've added a section on NPM inc (it might well deserve a completely separate page) and something on the resignation of the CEO, Bryan Bogensberger. NoPolymath (talk) 18:35, 20 September 2019 (UTC)[reply]

Done. (See npm, Inc.) jareha ^(comments) 02:04, 1 July 2021 (UTC)[reply]

Error: first parameter cannot be parsed as a date or time

FYI: See error on page — Preceding unsigned comment added by Samuel Marks (talk • contribs) 00:39, 26 October 2022 (UTC)[reply]

Requested move 27 June 2023

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved per request. Renaming NPM would require a separate discussion. Favonian (talk) 16:09, 4 July 2023 (UTC)[reply]

Npm (software) → Npm – This article is the WP:PRIMARYTOPIC for 'npm' and per MOS:ACROTITLE: "Acronyms should be used in a page name if the subject is known primarily by its abbreviation and that abbreviation is primarily associated with the subject". That is the case here. PhotographyEdits (talk) 09:26, 27 June 2023 (UTC)[reply]

NPM In ictu oculi (talk) 13:22, 27 June 2023 (UTC)[reply]
@In ictu oculi Sorry, what do you mean? PhotographyEdits (talk) 13:41, 27 June 2023 (UTC)[reply]
Comment I think I would be in favor of moving Npm (software) to Npm and possibly NPM → NPM (disambiguation) making a NPM a redirect to Npm. (Aside: I think Npm (software) Npm, Inc. probably should be merged to the software article and at Npm since the company is only own for Npm. And since none of the other items in the disambiguation page seem to be notable enough and generally known as "NPM". (With a hatnote added at Npm to NPM (disambiguation), of course.)) Skynxnex (talk) 13:44, 27 June 2023 (UTC)[reply]
I also support merging the company into this article. Since it has become a subsidiary, I think it is unlikely to become much more notable than it currently is, meaning it is probably a WP:PERMASTUB. The current article about the package manager is not that long either. PhotographyEdits (talk) 13:47, 27 June 2023 (UTC)[reply]

Support per my comments above and nom. Also there is no other page with the title Npm plus a disambiguator. Skynxnex (talk) 15:36, 3 July 2023 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.